CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skillify

Turn a repeatable workflow from the current session into a reusable OMC skill draft

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/skillify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable process skill: a concrete quality gate, a sequenced workflow with a real frontmatter template and exact storage paths, and clear rules and output expectations. Its only flaws are minor — one duplicated instruction and the lack of a worked example or explicit post-draft verification step.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no concept explanations, just decision heuristics, a template, and paths. The only redundancy is the duplicated prohibition ("Never emit plain markdown-only skill files" followed immediately by "Do **not** write plain markdown without frontmatter"), which keeps it just short of the lean anchor at 5.

4 / 5

Actionability

Guidance is mostly executable: a copy-paste-ready YAML frontmatter template, exact output paths (${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<skill-name>.md and .omc/skills/<skill-name>.md), and a concrete extraction checklist. Minor gaps — e.g., no worked example of a finished learned-skill draft — keep it below the fully-executable anchor at 5.

4 / 5

Workflow Clarity

The 6-step workflow is clearly sequenced with an explicit pre-flight validation checkpoint (the three-question Quality Gate) and a fuzziness check in step 6. Post-draft verification is only implied via the Output section ("Verification or quality-gate notes") rather than an explicit validate-and-fix step, matching the 'most checkpoints present' anchor at 4 rather than the feedback-loop anchor at 5.

4 / 5

Progressive Disclosure

This is a small (~60-line), self-contained, single-purpose skill with well-organized sections (Goal, Quality Gate, Workflow, Rules, Output) and no bundle files referenced or needed — nothing belongs in a separate file, so well-organized sections alone satisfy the top anchor.

5 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description communicates a clear, distinct purpose in third person, but it omits any explicit 'when to use' trigger clause and lacks natural trigger terms users would say when needing this skill. Adding a 'Use when...' clause with concrete invocation phrases would raise both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g., "Use when the session just solved a multi-step problem worth reusing, or when the user asks to save, capture, or turn this workflow into a skill."

Include natural synonyms users would actually say — "make a skill", "save this workflow", "skillify this", "reusable skill" — alongside the existing keywords.

Sharpen the 'what' by naming 1-2 more concrete actions, e.g., "extract the steps, pitfalls, and verification evidence, then draft a complete skill file with frontmatter".

DimensionReasoningScore

Specificity

The description names its domain (session workflows → OMC skills) and one concrete action — "Turn a repeatable workflow from the current session into a reusable OMC skill draft" — but does not list several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

The 'what' is clear (turn a session workflow into a reusable skill draft), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by "from the current session", which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It contains some relevant keywords ("repeatable workflow", "reusable", "OMC skill") but misses the natural phrases a user would say, such as "make this a skill", "save this workflow", or "skillify this" — matching the 'relevant keywords but missing common variations' anchor rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — drafting OMC skills from session workflows — with only minor overlap risk against general skill-authoring or documentation skills. It falls short of anchor 5 because it offers no explicit trigger phrases to disambiguate invocation from those related skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/skillify/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.