gedsys/skillify
Capture the current session's repeatable process into a reusable SKILL.md skill file. Use when the user wants to create a skill, save a workflow as a skill, turn a process into a reusable skill, or mentions "skillify", "create skill", "make a skill", "save as skill", "capture workflow", "turn this into a skill", "new skill", or wants to automate a repeatable process they just performed.
90
90%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates what the skill does with specific concrete actions, provides comprehensive trigger terms covering many natural user phrasings, and explicitly separates the 'what' from the 'when'. The description occupies a clear, distinctive niche that is unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'interviewing the user', 'extracting steps from the conversation', 'generating YAML frontmatter', and 'writing structured markdown instructions'. These are detailed, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (captures session processes into SKILL.md files by interviewing, extracting, generating frontmatter, writing markdown) and 'when' (explicit 'Use when...' clause with extensive trigger phrases and scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'skillify', 'create skill', 'make a skill', 'save as skill', 'capture workflow', 'turn this into a skill', 'new skill', and 'automate a repeatable process'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — creating SKILL.md files from session workflows is a very specific task. The trigger terms like 'skillify' and 'SKILL.md' are unique and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted meta-skill with excellent workflow clarity and actionability. The interview structure is thoughtfully designed with progressive rounds, and every step has explicit success criteria. The main weakness is moderate verbosity — some sections explain things Claude would already know (like what frontmatter fields mean) and the document could be ~20% shorter without losing clarity.
Suggestions
Trim the frontmatter rules section — Claude already understands YAML frontmatter semantics; focus only on project-specific conventions like the allowed-tools pattern syntax.
Consider extracting the 'Per-step annotations' reference and 'Step structure tips' into a companion file (e.g., SKILL_TEMPLATE.md) to keep the main skill leaner and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-written but includes some unnecessary verbosity, such as explaining what each frontmatter field means (Claude already knows YAML) and some redundant phrasing. The step annotations section and frontmatter rules could be tightened, though most content earns its place given the complexity of the task. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific interview rounds with exact questions to ask, a complete SKILL.md template with frontmatter format, exact annotation types to use, and clear instructions for each phase. The markdown template is copy-paste ready and the interview structure is specific enough to execute directly. | 3 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced with explicit success criteria on every step. It includes a human checkpoint (Review and Save step with AskUserQuestion confirmation before writing), feedback loops (iterate until user is happy in each interview round), and clear progression from analysis → interview → write → review. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sub-sections, but it's a fairly long monolithic document (~150 lines of instruction). The step annotations, frontmatter rules, and step structure tips sections could potentially be split into reference files. However, for a skill of this complexity, keeping it in one file is defensible. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents