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.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./Infrastructure/references/deferred-skill-context/skill-factory-skillify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Scale 1-3

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

This is a meta-skill (creating skills from workflows) that provides reasonable structure and clear scope, but suffers from a lack of concrete, executable guidance—the procedure steps are descriptive rather than actionable, and validation is described separately rather than integrated as checkpoints. The content is moderately concise but has some redundancy across sections (anti-patterns vs. constraints vs. gotchas) and defers most actionable detail to referenced files that aren't available in the bundle.

Suggestions

Integrate validation checkpoints directly into the procedure steps (e.g., after step 4: 'Validate: confirm all required sections exist per template checklist; if missing, loop back to step 3') rather than listing them in a separate section.

Add a concrete example showing a mini input (e.g., a brief session excerpt) and the corresponding output (e.g., a skeleton SKILL.md with frontmatter and key sections filled in) to make the skill actionable rather than purely descriptive.

Consolidate 'Anti-patterns', 'Gotchas', and 'Failure mode' into a single 'Constraints & failure handling' section to reduce redundancy and improve token efficiency.

Ensure bundle files (skill-template.md, session-collector-intake.md) are provided so the progressive disclosure structure actually works; alternatively, inline the essential template structure so the skill is self-contained.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some sections that could be tightened—'Philosophy' restates general good practices Claude already knows, and 'Gotchas' partially overlaps with 'Anti-patterns' and 'Constraints'. The examples section just lists trigger phrases without showing input/output, adding limited value.

2 / 3

Actionability

The procedure provides a clear sequence of steps but remains at a descriptive/abstract level—there are no concrete commands, executable code, specific file structures, or copy-paste-ready templates inline. The actual actionable content is deferred to referenced files (skill-template.md, session-collector-intake.md) which are not provided in the bundle.

2 / 3

Workflow Clarity

The 6-step procedure is sequenced and step 6 mentions 'run structure checks and iterate until clean,' but validation checkpoints are not explicit inline—there's no concrete validation command or clear feedback loop (validate → fix → retry) embedded in the procedure steps themselves. The separate 'Validation' section lists what to verify but doesn't integrate into the workflow as checkpoints.

2 / 3

Progressive Disclosure

The skill references companion files (skill-template.md, session-collector-intake.md) with conditional 'Read when' directives, which is good structure. However, the bundle files are not provided, making it impossible to confirm the references resolve. Additionally, some inline content (anti-patterns, gotchas, failure modes) could be consolidated, and the reference links are listed redundantly—once at the top and again mid-body.

2 / 3

Total

8

/

12

Passed

Description

85%Scale 1-3

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 defines a specific niche (creating SKILL.md files from Codex workflows), lists concrete actions in the process, and includes an explicit 'Use when' clause. The main weakness is that trigger terms could be broader to capture more natural user phrasings beyond 'skillify' and 'operationalize'.

Suggestions

Expand trigger terms to include more natural user phrasings like 'create a skill', 'save as skill', 'make a skill file', 'package this workflow', or 'turn this into a skill'.

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 trigger terms like 'skillify' and 'SKILL.md', but 'operationalize a repeatable process' is somewhat jargon-heavy. Missing common variations a user might say like 'create a skill', 'save as skill', 'make a skill file', or 'package workflow'.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive niche — creating SKILL.md files from Codex workflows is a very specific task unlikely to conflict with other skills. Terms like 'skillify', 'SKILL.md package', and 'session-collector evidence' 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.