CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

62%

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

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

41%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 maximally concise but at the cost of substance: it contains no executable guidance and no workflow sequence for what its own description defines as a multi-step process. Worse, its only reference resolves to a redirect stub pointing outside the bundle, leaving the actual intake/template content unreachable and the rest of the reference files unnavigable.

Suggestions

Inline a short numbered workflow (gather session context / collector evidence → run the structured user interview → draft from the template → validate the artifact) with an explicit validation step, so the multi-step process the description promises is sequenced in the body.

Replace the redirect-stub reference pattern with real one-level-deep content: either populate references/skill-template.md (and session-collector-intake.md) with the actual intake prompts and template, or remove the dead fixtures/... pointer.

Add brief 'Read when' pointers for the other bundle files (contract.yaml, evals.yaml, task-profile.json) so the bundle's content is discoverable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is three lean lines: a goal statement ("Convert a completed workflow into a reusable skill package with explicit invoke syntax") and a single conditioned reference pointer ("Read when: intake and template details are needed"). Nothing explains concepts Claude already knows and every token earns its place — exactly the 'lean and efficient' anchor. Not 4: there are no over-explanations to trim at all.

5 / 5

Actionability

The body only states a goal and points to [skill template](./references/skill-template.md) — a high-level hint with none of the specific steps to execute (no intake prompts, no interview structure, no template usage instructions), matching the 'minimal concrete guidance; high-level hints but missing the specific steps' anchor. Not 1: it does name a concrete file and a read condition rather than being purely abstract; not 3: there is no partially-complete executable guidance, and the one referenced file is a redirect stub rather than usable content.

2 / 5

Workflow Clarity

Despite the skill being inherently multi-step (per its own description: analyze session context, interview the user, write, validate), the body presents no sequence whatsoever — just a one-line goal with no steps and no validation checkpoint, matching the 'steps missing; no sequence; no validation' anchor. Not 2: even a rough partial sequence is absent.

1 / 5

Progressive Disclosure

Judged against the actual bundle: the single signaled reference (references/skill-template.md) is a stub redirecting to an external path ("fixtures/budget-archive/2026-04-19/..."), creating a nested indirection like the bad 'See advanced.md → See details.md' example, while four other bundle files (contract.yaml, evals.yaml, session-collector-intake.md, task-profile.json) are never referenced from SKILL.md and are effectively buried. This matches the 'references are buried / minimal structure' anchor. Not 3: the reference that exists is clearly signaled, but navigation is broken by the stub chain and the bulk of bundle content is undiscoverable; not 1: there is at least one explicitly signaled pointer and the body itself is not a monolithic wall of text.

2 / 5

Total

10

/

20

Passed

Description

67%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 with a clear what/when structure and mostly concrete, third-person action statements. Its main weakness is trigger coverage: it leans on the coined term "skillify" and misses the natural phrasings a user would more likely say when wanting this skill.

DimensionReasoningScore

Specificity

Names the domain ("Capture a completed Codex workflow as a reusable SKILL.md package") and several concrete actions — "analyzing session context plus optional session-collector evidence", "interviewing the user with structured prompts", "writing a validated skill artifact" — matching the anchor for several specific actions with minor gaps (e.g., what validation entails is unspecified). Not 5: coverage is good but not exhaustive, and "validated skill artifact" is slightly abstract; not 3: more than 1-2 actions are concretely listed.

4 / 5

Completeness

Both parts are explicit: a clear 'what' ("analyzing session context... interviewing the user... writing a validated skill artifact") and a 'when' ("Use when the user asks to skillify or operationalize a repeatable process"), matching the anchor where 'when' could be more specific. Not 5: the 'when' clause offers only two trigger phrases with no synonyms or concrete variations; not 3: the 'when' is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Triggers are "Use when the user asks to skillify or operationalize a repeatable process" — "skillify" is a relevant keyword but common natural phrasings users would say are missing ("create a skill", "turn this workflow into a skill", "save this as a skill", "SKILL.md"), matching the anchor for some relevant keywords missing common variations/synonyms. Not 4: the missing variants are obvious and numerous, not just "a few".

3 / 5

Distinctiveness Conflict Risk

The niche is clear (packaging a completed Codex workflow into a SKILL.md artifact) with a distinctive "skillify" trigger, so conflict risk with unrelated skills is minimal — matching the 'mostly distinct, minor overlap' anchor. Not 5: "operationalize a repeatable process" is somewhat broad and could overlap with other skill-authoring or process-packaging skills; not 3: the domain and trigger are far more specific than generic overlap examples.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/scaffolding_templates/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.