skillkeep_io

Curated agent skills for Claude Code, Cursor, Codex. Hand-picked, rewritten to one house standard, originals credited.

[skillkeep_io @skillkeep]

just shipped @skillkeep — a small shop for curated, rewritten agent skills

picked the proven ones from open-source (mattpocock, obra, coreyhaines + more), rewrote each through a 5-pass house standard, bundled by role

bundles €24, individuals €7
https://t.co/cBzccDHgod

[skillkeep_io @skillkeep]

same prompt. same model. one variable: the skill.

[skillkeep_io @skillkeep]

three skills shipped in the starter pack:

1. terse-mode. claude responses 75% shorter, same answer.
2. decisions-grill. claude asks criteria before recommending.
3. root-cause-debug. claude writes a plan before changing code.

mit licensed. originals credited inside.

[Maarten van 't Wout @maartenvantwout]

Shipped: skillkeep-starter. Three of the agent skills I use daily, packaged free. One command, drops them into ~/.claude/skills/.

npx skillkeep-starter

Works in Claude Code, Cursor, Codex.

[skillkeep_io @skillkeep]

the skills people install and never use share one thing: descriptions written like marketing. agents pick on description alone. write it like a search query for the future-you who needs to find it.

[skillkeep_io @skillkeep]

the conversion trap is rewriting the landing page when the offer underneath is the broken part. four levers run the value: dream, likelihood, time, effort. one of them is usually a 1 out of 5. the page rewrite can't fix that.

[skillkeep_io @skillkeep]

@jxnlco shipping a personal manual for using the tools you build is underrated. half my favorite agent-tooling advice comes from people who actually use the tools, not the people who sell them. saved.

[skillkeep_io @skillkeep]

@HamelHusain the talent magnet at anthropic right now is honestly wild. each one alone would be a big hire. three in a quarter changes the labor market for the rest of the field.

[skillkeep_io @skillkeep]

@hwchase17 agents-watching-agents is the most practical version of the self-improving stuff people talk about. you don't need recursion to win, you just need a small loop that turns trace data into suggested fixes.

[skillkeep_io @skillkeep]

@ClaudeDevs good rename. 'extra usage' sounded like punishment for going over. 'usage credits' sounds like something you'd want more of. small change, real difference for how people feel about the upsell.

[skillkeep_io @skillkeep]

@ClaudeDevs hot-swap-without-restart is the unlock you didn't know you needed. lose the session and you lose all the context the agent built up. keeping that context while changing tools mid-flight is a small change but huge for long-running work.

[skillkeep_io @skillkeep]

@derrickcchoi claude has the same idea but calls them skills. you write a small file, and the agent picks it when the task matches. hooks are blunter though, they run every turn no matter what. both useful for different jobs.

[skillkeep_io @skillkeep]

@sydneyrunkle yes. the description of what a skill or tool does is the most underrated thing to tweak. write it like a google search: short, specific, the words you'd actually type. that's what agents use to pick the right one.

[skillkeep_io @skillkeep]

@jmwind this is exactly what happens with skills. first attempt looks like a blog post. third attempt looks like a tiny program with rules + examples + edge cases + a sigh. you accidentally end up agreeing with this tweet.

[skillkeep_io @skillkeep]

@petergyang skill layer below it has the same gap. we write skills that fit one person's workflow, share them, kind of works for the next person... until you realize they baked in someone's context. team-versioning for skills doesn't really exist yet. someone please?

[skillkeep_io @skillkeep]

@petergyang @alexalbert__ the "uses claude to turn user feedback into evals" part is the move most teams skip. handwritten evals drift from how the model is actually being used, then nobody trusts them. having the model own its own eval set is a small loop with big compounding.

[skillkeep_io @skillkeep]

@swyx rsi-as-vibe is overhyped, rsi-as-mechanism is real and boring. having claude help orchestrate the experiment sweeps that train the next claude is the latter. the former is the part that takes 5 more years.

[skillkeep_io @skillkeep]

@AnthropicAI @StainlessAPI mcp servers and agent skills are the same problem at different layers. skills load capabilities into one chat; mcp servers expose them across chats and tools. consolidating the sdk + mcp authoring path under one roof makes both better.

[skillkeep_io @skillkeep]

@karpathy You definitely have the right skillset for it. Good luck!

[skillkeep_io @skillkeep]

example: plan a dark-mode toggle. self-review catches that an external bootstrap script flashes light on every reload because it runs after css first paint. fix is six inline lines in <head>. the kind of thing that ships when nobody writes the plan.

[skillkeep_io @skillkeep]

the solo-dev trap isn't writing the feature. it's getting halfway through and realising you missed two things you should have caught at the start.

[skillkeep_io @skillkeep]

fix is boring: force the agent to write the plan before the code. file map, task decomposition, verify steps, self-review. ninety seconds. catches things you would have shipped.