CtrlK
BlogDocsLog inGet started
Tessl Logo

skillify

Capture a completed Codex workflow as a reusable SKILL.md package by analyzing session context plus optional session-collector evidence, interviewing the user with structured prompts, and writing a validated skill artifact. Use when the user asks to skillify or operationalize a repeatable process.

47

Quality

50%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/scaffolding_templates/scaffolding_templates/skillify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

14%

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

This skill body is essentially a stub—it contains a one-line description and a single reference to a template file, with no actionable content, workflow steps, examples, or meaningful structure. The description promises a rich multi-step process (session analysis, structured interviews, validated artifact writing) but the body delivers none of it. This needs substantial content to be a functional skill.

Suggestions

Add a concrete multi-step workflow covering the key phases described in the skill description: (1) analyze session context, (2) interview the user with structured prompts, (3) write and validate the skill artifact.

Include at least one concrete example showing input (e.g., a completed workflow scenario) and expected output (e.g., a skeleton SKILL.md with frontmatter and body).

Add validation checkpoints, such as verifying the generated skill against a schema or checklist before finalizing.

Provide a brief quick-start overview in the SKILL.md itself so it's useful without requiring the reader to immediately navigate to the referenced template file.

DimensionReasoningScore

Conciseness

The content is very brief (only 3 lines of actual instruction), which is lean, but it's so sparse that it's hard to judge efficiency—it essentially delegates everything to a reference file without providing any overview or quick-start content itself.

2 / 3

Actionability

There is no concrete guidance, no steps, no commands, no examples, and no executable content. The entire skill body is a single sentence pointing to a reference file, providing no actionable instruction on its own.

1 / 3

Workflow Clarity

The description mentions a multi-step process (analyzing session context, interviewing the user, writing a validated artifact), but the body contains zero workflow steps, no sequencing, and no validation checkpoints.

1 / 3

Progressive Disclosure

While it references a template file, the SKILL.md itself contains essentially no overview or navigational structure. It's not a well-organized overview pointing to details—it's an empty shell pointing to a single file. Additionally, no bundle files were provided, so the reference cannot be verified.

1 / 3

Total

5

/

12

Passed

Description

85%

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 a well-crafted description that clearly articulates a specific, niche capability with concrete actions and explicit trigger guidance. Its main weakness is that the trigger terms could be broader to capture more natural user phrasings beyond 'skillify' and 'operationalize', which are somewhat specialized terms that not all users would naturally use.

Suggestions

Expand trigger terms to include more natural phrasings like 'create a skill', 'save as skill', 'document this workflow', 'make this repeatable', or 'package this process' to improve discoverability.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'analyzing session context plus optional session-collector evidence', 'interviewing the user with structured prompts', and 'writing a validated skill artifact'. These are distinct, concrete steps in a workflow.

3 / 3

Completeness

Clearly answers both what ('Capture a completed Codex workflow as a reusable SKILL.md package by analyzing session context...interviewing the user...writing a validated skill artifact') and when ('Use when the user asks to skillify or operationalize a repeatable process') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes some natural keywords like 'skillify', 'SKILL.md', and 'reusable' but misses common variations users might say such as 'create a skill', 'save as skill', 'make a template', 'document this workflow', or 'package this process'. The term 'operationalize' is somewhat jargon-heavy.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive niche — creating SKILL.md packages from Codex workflows is a very specific task unlikely to conflict with other skills. The triggers 'skillify' and 'SKILL.md' are unique identifiers.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

10

/

11

Passed

Repository
jscraik/Agent-Skills
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.