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.

71

Quality

86%

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

The canonical home for this skill is intent in tdg-ninja/context-specs-factory-ai

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is a well-structured interactive workflow with strong sequencing, an explicit validation feedback loop, and clean one-level-deep references. It is slightly verbose in the philosophy section and delegates some executable detail to recipe files, modestly capping conciseness and actionability.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and avoids explaining basic concepts, with each of the nine principles kept to one sharp line; minor padding in the philosophy section and 'how to run' prose keeps it just below the leanest anchor.

4 / 5

Actionability

Provides concrete, copy-pasteable commands in Step 7 and a specific author-slug derivation in Step 0, with file-pointed templates and recipes; the runner authoring detail is delegated to a recipe file rather than inlined, leaving small gaps.

4 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced with an explicit validation gate (the Step 6 failing-for-the-right-reason feedback loop), a decide-to-build gate, idempotency handling, and a 'Hard nevers' checklist, matching the top anchor for explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that signals four real one-level-deep references (elicitation.md, right-reason.md, prd-template.md, runner-recipes.md), each labeled with its purpose and marked as a hackable seam, with content appropriately split and easy to navigate.

5 / 5

Total

18

/

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.

The description is concrete, trigger-rich, and fully answers both what and when with quoted natural phrases a developer would say. Its only minor weakness is that the capability list is artifact-oriented rather than a broad enumeration of distinct actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions/artifacts — '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' — with only minor coverage gaps, so it sits above the '1-2 concrete actions' anchor but short of comprehensive multiple-action listing.

4 / 5

Completeness

Explicitly answers both 'what' (produce a PRD plus a runnable definition of done, yielding named files) and 'when' via a 'Use when...' clause with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes many natural phrases a developer would say — 'start a new feature', 'file a PRD', 'spec out', 'scope an idea', 'think through what to build' — giving strong keyword coverage with synonyms, just below the comprehensive-with-extensions bar.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (PRD + executable DoD on a branch, 'the one human-attentive skill in the chain') with distinct triggers and minimal overlap with other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tdg-ninja/context-specs-claude-code
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.