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?

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 ./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%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 skill body is essentially empty — it contains a one-line description and a single reference link with no actionable content, no workflow steps, and no examples. The description promises a rich multi-step process (session analysis, structured interviews, validated artifact writing) but the body delivers none of it. This is a stub, not a functional skill.

Suggestions

Add a concrete multi-step workflow outlining the skillify process: e.g., 1) Gather session context, 2) Interview user with specific prompts, 3) Draft SKILL.md, 4) Validate against template, 5) Output final artifact.

Include at least one concrete example showing input (a completed workflow description) and expected output (a SKILL.md skeleton or snippet).

Add validation checkpoints — e.g., verify the generated skill has required YAML frontmatter fields, check that referenced files exist, confirm the skill matches the template structure.

Provide the actual interview prompts or a structured question list inline rather than deferring everything to the reference 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 delegates almost everything to a reference file without providing any actionable overview content itself.

2 / 3

Actionability

There is no concrete guidance, no steps, no code, no commands, and no examples. The entire skill body is a single sentence plus a link to a reference file, providing zero executable or actionable content 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 no steps, no sequence, and no validation checkpoints whatsoever.

1 / 3

Progressive Disclosure

The skill references a single file (skill-template.md) but provides no overview content, no structure, and no navigation. It's not progressive disclosure — it's complete delegation with no useful top-level content. The bundle files note also says no bundle files were provided, so the reference path cannot be verified.

1 / 3

Total

5

/

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.