Claude Code Has an Internal Skill Nobody Knew About: /skillify

Source: David Veselý, Claude Code Has an Internal Skill Nobody Knew About: /skillify (Medium, 2026-04-08)

Key takeaways

  • /skillify generates skill files from existing patterns in your codebase.
  • Auto-creates .claude/skills/*/SKILL.md entries from repeated workflows you already do.
  • Solves the “I keep doing this — should make it a skill” friction loop.
  • Directly relevant to OMC’s skill system and to any team starting to build a shared skill library.

The pitch

If you keep doing the same thing in Claude Code sessions — “run tests, fix failures, update changelog” for example — the “right” thing is to make it a reusable skill. Nobody does it because writing SKILL.md files from scratch is friction.

/skillify takes the workflow you just ran and generates a SKILL.md draft for you. You review, edit, and commit.

Why this matters

  • Lowers the activation energy for skill creation. The difference between “yeah I should make that a skill” and “I made it a skill” is usually 10 minutes of writing. /skillify cuts that to 2 minutes of review.
  • Useful for team skill libraries. Once one engineer skillifies a workflow, the rest of the team can run it. Multiplier effect.
  • Complements OMC’s own skillify skill. If you’re running OMC, you have a parallel implementation. Worth comparing the two approaches.

Where it fits in the broader skill ecosystem

  • skills.sh registry — the public registry of installable skills
  • Agent Skills Repos — Joe Njenga’s curated review of what’s in the ecosystem
  • OMC’s /oh-my-claudecode:skillify — if you’re running OMC, this is the parallel built-in
  • Rezvani’s github.com/alirezarezvani/claude-skills — 220+ skills as a reference library

Built by Force Information Systems · Harris Computer · Constellation Software. Licensed under MIT.