CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skillify

Creates release-ready skill packages from proven workflows by drafting SKILL.md frontmatter, trigger-rich instructions, references/contract.yaml, eval scenarios, task profile, and validation commands. Use when the user asks to create a skill, skillify a workflow, package a process, write SKILL.md, make a reusable skill template, or prepare a skill for release checks.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A highly actionable, well-sequenced skill body with exact commands, a validation ladder, and a properly split reference layer. Its weaknesses are redundancy (First-Principles Gate boilerplate, repeated blocked-plan rules) and references that assume an external repo layout.

Suggestions

Compress or remove the First-Principles Gate boilerplate (desired outcome / rejected assumptions / evidence required bullets) that restates constraints already covered in Constraints, Workflow, and Failure Mode.

Consolidate the repeated read-only/blocked-plan guidance (Workflow step 9-10 paragraph, Execution Boundaries, Failure Mode) into a single section to reclaim tokens.

Clarify or localize the external repo-root references ('Infrastructure/references/...', 'Plugins/skill-factory/...'), which do not resolve from the skill package and conflict with the skill's own portability constraint.

DimensionReasoningScore

Conciseness

The body is mostly telegraphic and free of concept-teaching padding, but the ~11-bullet First-Principles Gate reads as compliance boilerplate rather than actionable guidance, and the read-only/blocked-plan rules are repeated across Workflow, Execution Boundaries, and Failure Mode. Mostly efficient but could be tightened fits anchor 3; it is not anchor 2 because there is no explanation of things Claude already knows, and not anchor 4 because the redundancy is more than minor.

3 / 5

Actionability

Guidance is fully executable: twelve exact './bin/ask ... --json --robot' validation commands, the exact minimal package file list ('SKILL.md', 'references/contract.yaml', 'references/evals.yaml', 'references/task-profile.json'), and a copy-paste YAML output template with concrete fields. Copy-paste ready commands covering the common cases match anchor 5.

5 / 5

Workflow Clarity

The 10-step Workflow is clearly sequenced with explicit validation checkpoints ('Run strict audit. If it fails, fix that failure before broader validation'), and the Validation section defines an ordered proof ladder with a fail-fast rule ('stop at the first failed gate'). Clear sequence with explicit validation steps and error-recovery loops matches anchor 5.

5 / 5

Progressive Disclosure

SKILL.md is a genuine overview and the bulk content (contract.yaml, evals.yaml, task-profile.json, template, examples, interview) is split one level deep into well-signaled references that all exist in the bundle. However, several References-section entries point outside the bundle to repo-root paths ('Infrastructure/references/first-principles-factory-gate.md', 'Plugins/skill-factory/references/context-development-lifecycle.md', lens packs) that do not resolve from the skill package itself — a minor organization gap consistent with anchor 4 rather than anchor 5.

4 / 5

Total

17

/

20

Passed

Description

92%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.

A strong description: concrete deliverables, third-person voice, and an explicit 'Use when...' clause with distinctive trigger phrases. The only gap is a few missing natural trigger synonyms that the body's When To Use section already contains.

Suggestions

Add one or two natural trigger variations to the description, e.g. 'turn a workflow into a skill' or 'save a workflow as a skill', which the body's When To Use section already uses but the description omits.

Consider including the discovery trigger ('look across recent work/sessions for repeated workflows worth packaging') in the description, since discovery is a supported entry point currently only surfaced in the body.

DimensionReasoningScore

Specificity

The description lists the full set of concrete deliverables — 'drafting SKILL.md frontmatter, trigger-rich instructions, references/contract.yaml, eval scenarios, task profile, and validation commands' — giving comprehensive, non-vague coverage of what the skill produces. It matches the anchor for multiple specific concrete actions rather than merely several actions with minor gaps.

5 / 5

Completeness

It clearly answers both 'what' (creates release-ready skill packages by drafting named artifacts) in third person and 'when' via the explicit 'Use when the user asks to create a skill, skillify a workflow, package a process, write SKILL.md...' clause with concrete trigger phrases. This matches the anchor for explicitly answering both what AND when.

5 / 5

Trigger Term Quality

'create a skill', 'skillify a workflow', 'package a process', 'write SKILL.md', 'make a reusable skill template' are natural user phrasings, but common variations such as 'turn a workflow into a skill' or 'save a workflow as a skill' (which the body itself uses in When To Use) are absent from the description. Good keyword coverage with a few natural terms missing fits anchor 4.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct — packaging proven workflows into skill packages — with triggers ('skillify', 'write SKILL.md', 'release checks') that would not naturally fire for sibling skills such as installers, routers, or refactor tools mentioned in the body. Minimal conflict risk fits anchor 5.

5 / 5

Total

19

/

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

jscraik/Agent-Skills

Path

Plugins/skill-factory/skills/scaffolding_templates/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.