CtrlK
BlogDocsLog inGet started
Tessl Logo

intent

Turn an open-ended idea into a PRD plus a runnable definition of done. Use when a developer wants to start a new feature, "file a PRD", "spec out" or "scope" an idea, think through what to build, or kick off the harness for a piece of work. Produces prds/<feature>/prd.md + an executable prds/<feature>/run-prd-test.sh on a prd/<author-slug>/<feature> branch. The one human-attentive skill in the chain.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-architected skill body that delegates detail to clearly signaled reference files and sequences the work with explicit validation feedback loops. Concise and actionable with strong progressive disclosure.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence throughout — it never explains what a PRD or an exit code is, and the philosophy section earns every line; no padded sections.

5 / 5

Actionability

Provides executable git commands in Step 7, an explicit chmod + run loop in Step 6, and concrete file paths; the per-check runner recipes are correctly delegated to runner-recipes.md rather than inlined, leaving only minor detail gaps.

4 / 5

Workflow Clarity

Steps 0-7 are clearly sequenced, with Step 6 as an explicit validate-run → fix → re-run feedback loop and a "Hard nevers" guardrail set; the right-reason check before commit is the validation checkpoint.

5 / 5

Progressive Disclosure

The body is a well-organized overview that points to four real one-level-deep reference files (elicitation.md, right-reason.md, prd-template.md, runner-recipes.md), each clearly signaled with its purpose — easy navigation with no nesting.

5 / 5

Total

19

/

20

Passed

Description

100%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, specific description that clearly states what it produces and when to invoke it, with natural trigger terms drawn from real user phrasing. Both the what and when are concrete and explicit.

DimensionReasoningScore

Specificity

Names multiple concrete actions and outputs — "Turn an open-ended idea into a PRD plus a runnable definition of done" and "Produces prds/<feature>/prd.md + an executable prds/<feature>/run-prd-test.sh on a prd/<author-slug>/<feature> branch" — giving comprehensive coverage of what it does.

5 / 5

Completeness

Explicitly answers both what (PRD + runnable definition of done, concrete file outputs) and when (a clear "Use when..." clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Includes natural user phrasings in quotes — "file a PRD", "spec out", "scope", "think through what to build", "start a new feature" — strong coverage of the ways a developer would actually request this.

5 / 5

Distinctiveness Conflict Risk

The narrow artifact contract (prd.md + run-prd-test.sh on a specific branch) and the claim "The one human-attentive skill in the chain" carve a clear, low-conflict niche.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tdg-ninja/context-specs-factory-ai
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.