CtrlK
BlogDocsLog inGet started
Tessl Logo

create-factory-verification

Generate a project-local verification skill that drives the real app and captures evidence for factory lifecycle gates. Use during setup-factory or when a factory has no scripted way to prove UI, CLI, or service behavior.

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary skill body: tight, imperative, and entirely actionable, with a real validation loop ('a skill that was never executed is a draft') and concrete tool-specific checklists. Nothing is padded and nothing Claude already knows is re-explained.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and imperative with zero concept explanations — 'Write `.factory/skills/verify-<repo>/` for the next agent, not as a human tutorial' sets the tone, and every subsequent line instructs rather than explains. Every token earns its place, matching the level-5 anchor.

5 / 5

Actionability

Provides a copy-paste-ready generator command (`node <factory-supervise>/scripts/write-verification-skill.mjs --code-root ... --factory-root ...`) with explicitly justified placeholders, the exact evidence path `.factory/evidence/<ticket>/<task>/`, named required sections (Launch, Doctor, Drive, Evidence, Cleanup), and a precise checklist of surf subcommands. Fully executable guidance covering the common cases — the level-5 anchor.

5 / 5

Workflow Clarity

Clear sequence — interview from checkout, generate files, replace placeholders, prove one feature, persist the rerunnable command — with an explicit validation feedback loop: 'Run the generated skill once... confirm the evidence file is still there. Fix the skill if that fails. A skill that was never executed is a draft.' Not a 4, because validation is explicit with a fix-and-retry loop rather than merely present.

5 / 5

Progressive Disclosure

A single self-contained SKILL.md under 50 lines with no external references needed and clear sections (Interview, Prove one feature). Per the simple-skill guidance, well-organized sections alone warrant the top score; there is no bundle to disclose further.

5 / 5

Total

20

/

20

Passed

Description

87%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: concrete what-and-when structure in third person, with explicit trigger conditions and a distinctive niche. Keyword coverage is good but could add a few more natural synonyms to make triggering even more reliable.

Suggestions

Add one or two natural synonyms users might say, e.g. 'test or verify the real app' or 'smoke-test factory behavior', to broaden trigger matching.

Optionally enumerate one more concrete capability (e.g. 'produces a rerunnable verification command') to push capability coverage from several actions to comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('project-local verification skill') and lists several concrete actions — generate the skill, 'drives the real app', 'captures evidence for factory lifecycle gates' — with minor coverage gaps. It is not a 5 because it stops short of a comprehensive multi-action enumeration, and not a 3 because it exceeds the 1-2 action bar.

4 / 5

Completeness

Explicitly answers both: what ('Generate a project-local verification skill that drives the real app and captures evidence for factory lifecycle gates') and when ('Use during setup-factory or when a factory has no scripted way to prove UI, CLI, or service behavior'), with concrete trigger phrases matching the level-5 anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user in this domain would say: 'verification skill', 'prove UI, CLI, or service behavior', 'setup-factory', 'captures evidence'. Coverage is good but misses common synonyms and variations such as 'test the app', 'smoke test', or 'verify', keeping it below the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (factory lifecycle verification skill generation) with distinct triggers ('setup-factory', 'factory lifecycle gates', 'scripted way to prove behavior'), so it is unlikely to fire for unrelated skills — matching the minimal-conflict level-5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
geut/factory-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.