skillify
- Repo stars 34,677
- Author updated Live
- Author repo oh-my-claudecode
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @Yeachan-Heo · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skillify
description: Turn a repeatable workflow from the current session into a reusable OMC skill draft Use this ski…
category: other
runtime: no special runtime
---
# skillify output preview
## PART A: Task fit
- Use case: Turn a repeatable workflow from the current session into a reusable OMC skill draft Use this skill when the current session uncovered a repeatable workflow that should become a reusable OMC skill. Capture a successful multi-step workflow as a concrete skill draft instead of rediscovering it later. runs entirely locally. Works with Claude Code, Cursor, Cli….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Goal / Quality Gate / Workflow” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Turn a repeatable workflow from the current session into a reusable OMC skill draft Use this skill when the current session uncovered a repeatable workflow that should become a reusable OMC skill. Capture a successful multi-step workflow as a concrete skill draft instead of rediscovering it later. runs entirely locally. Works with Claude Code, Cursor, Cli…”.
- **02** When the source has headings, the agent prioritizes “Goal / Quality Gate / Workflow” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/oh-my-claudecode`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Goal / Quality Gate / Workflow”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skillify
description: Turn a repeatable workflow from the current session into a reusable OMC skill draft Use this ski…
category: other
source: Yeachan-Heo/oh-my-claudecode
---
# skillify
## When to use
- Turn a repeatable workflow from the current session into a reusable OMC skill draft Use this skill when the current se…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Goal / Quality Gate / Workflow” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skillify" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Goal / Quality Gate / Workflow
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Skillify
Use this skill when the current session uncovered a repeatable workflow that should become a reusable OMC skill.
Compatibility:
/oh-my-claudecode:learneris a deprecated alias for this skill. Prefer/oh-my-claudecode:skillifyin docs, prompts, and new workflows. Internal implementation modules may still use the learner name.
Goal
Capture a successful multi-step workflow as a concrete skill draft instead of rediscovering it later.
Quality Gate
Before extracting a skill, all three should be true:
- "Could someone Google this in 5 minutes?" → No.
- "Is this specific to this codebase, project, or workflow?" → Yes.
- "Did this take real debugging, design, or operational effort to discover?" → Yes.
Prefer skills that encode decision-making heuristics, constraints, pitfalls, and verification steps. Avoid generic snippets, boilerplate, or library usage examples that belong in normal documentation.
Workflow
- Identify the repeatable task the session accomplished.
- Extract:
- inputs
- ordered steps
- success criteria
- constraints / pitfalls
- verification evidence
- best target location for the skill
- Decide whether the workflow belongs as:
- a repo built-in skill
- a user/project learned skill
- documentation only
- When drafting a learned skill file, output a complete skill file that starts with YAML frontmatter.
- Never emit plain markdown-only skill files.
- Do not write plain markdown without frontmatter.
- Minimum frontmatter:
--- name: <skill-name> description: <one-line description> triggers: - <trigger-1> - <trigger-2> --- - Write learned/user/project skills to flat file-backed paths:
${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<skill-name>.md.omc/skills/<skill-name>.md
- Remember that uncommitted skills are still worktree-local until committed or copied to a user-level directory.
- Draft the rest of the skill file with clear triggers, steps, success criteria, and pitfalls.
- Point out anything still too fuzzy to encode safely.
Rules
- Only capture workflows that are actually repeatable.
- Keep the skill practical and scoped.
- Prefer explicit success criteria over vague prose.
- If the workflow still has unresolved branching decisions, note them before drafting.
- Keep
omc-learnedas the storage directory name for compatibility; do not present it as the public invocation name.
Output
- Proposed skill name
- Target location
- Draft workflow structure or complete skill file
- Verification or quality-gate notes
- Open questions, if any
Decide Fit First
Design Intent
How To Use It
Boundaries And Review