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.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

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

38%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 token-efficient but provides almost no executable guidance, no sequenced workflow with validation, and its only reference is a broken redirect stub. Substantive content needs to be inlined or a real reference file supplied.

Suggestions

Replace the skill-template.md stub with real template content (or inline a concise template) so the reference resolves in one hop instead of redirecting to a missing fixtures path.

Add a concrete, sequenced intake-to-artifact workflow with explicit validation checkpoints (e.g., confirm captured steps with the user, validate the written SKILL.md against the template before finishing).

Include at least one actionable artifact: a minimal SKILL.md skeleton or the structured interview prompts, so the skill gives executable guidance rather than only a high-level description.

DimensionReasoningScore

Conciseness

The body is lean with no concept re-explanation, but the lone reference is a stub that redirects to another path, adding a wasteful navigation hop that keeps it just short of the 5 anchor.

4 / 5

Actionability

The body offers only a high-level restatement ('Convert a completed workflow into a reusable skill package with explicit invoke syntax') with no concrete steps, commands, or examples; it points to a stub rather than executable guidance.

2 / 5

Workflow Clarity

No sequenced multi-step process or validation checkpoints appear in the body; the analyze-interview-write flow from the description is not operationalized, and the artifact-writing task lacks any validation gate.

2 / 5

Progressive Disclosure

The single reference resolves to a stub ('Read when: full content is needed at fixtures/budget-archive/.../skill-template.md') that itself points elsewhere, creating a nested 2-level-deep redirect to a path not present in the bundle, which is hard to navigate.

2 / 5

Total

10

/

20

Passed

Description

85%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 well-constructed description that explicitly covers both what the skill does and when to invoke it, with concrete actions and a distinctive coined trigger. Minor room for more comprehensive trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ('analyzing session context', 'interviewing the user with structured prompts', 'writing a validated skill artifact'), with only minor gaps in coverage compared to the 5 anchor.

4 / 5

Completeness

Clearly answers both 'what' (capture a workflow as a reusable SKILL.md package via analysis, interview, and artifact writing) and 'when' with an explicit 'Use when...' trigger phrase, matching the 5 anchor.

5 / 5

Trigger Term Quality

The trigger 'Use when the user asks to skillify or operationalize a repeatable process' uses natural phrasing, but relies on the coined term 'skillify' and offers limited synonyms, a few natural terms short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The coined 'skillify' trigger and 'operationalize a repeatable process' framing carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

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.