CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-prd

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Quality

80%

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 ./.claude/skills/to-prd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-crafted, instruction-only skill body: concrete template, named project artifacts, a user confirmation checkpoint, and clear downstream routing, with no filler or background exposition. Remaining improvements are minor — slight redundancy in the seams guidance and a missing verification step after publishing the ticket.

DimensionReasoningScore

Conciseness

The body is tight, project-specific instruction with no explanations of concepts Claude already knows, but has minor trimmable redundancy — 'Use the highest seam possible. If new seams are needed, propose them at the highest point you can.' repeats one idea, and the attribution footer adds tokens — matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Concrete guidance throughout: a full section-by-section PRD template, a worked user-story example, named project files (docs/domain-glossary.md, docs/adr/, AGENTS.md, constitution/local-workflow.md), and an explicit labeling rule for publishing. Minor gaps (e.g., no example of a seams decision, no sample tracker ticket) keep it below the copy-paste-ready top anchor.

4 / 5

Workflow Clarity

A clear three-step sequence (explore → sketch seams → write and publish) with an explicit user checkpoint ('Check with the user that these seams match their expectations') and a 'What happens next' routing rule. It falls short of anchor 5 because there is no post-publish verification step, though the operation is neither destructive nor batch so no cap applies.

4 / 5

Progressive Disclosure

Well-organized self-contained sections (Before you start / Process / template / What happens next) with no nested or buried references. The ~55-line inline PRD template pushes the body past the ~50-line simple-skill range and could arguably live in a references file, a minor organization gap that fits anchor 4 rather than the ideal split of anchor 5.

4 / 5

Total

16

/

20

Passed

Description

75%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 concise, well-structured description that clearly states both capability and trigger with low conflict risk. Its main weaknesses are narrow keyword coverage (no expansion of 'PRD' or synonyms like 'requirements doc'/'spec') and listing only two actions, which limits specificity for users who phrase the request differently.

Suggestions

Expand the trigger clause with natural variations, e.g. 'Use when the user wants to create a PRD (product requirements document) from the current context or conversation'.

Add one or two more concrete actions to the capability sentence, such as drafting extensive user stories and applying the tracker's agent-autonomy label when publishing.

Consider naming the routing distinction (requirements already settled vs. needing interrogation) in the description to further reduce overlap with requirements-gathering skills.

DimensionReasoningScore

Specificity

The description names the domain and exactly two concrete actions — 'Turn the current conversation context into a PRD and publish it to the project issue tracker' — but omits what the PRD contains or the labeling/triage steps, matching the anchor for 1-2 concrete actions without comprehensive coverage rather than anchor 4's 'several specific actions'.

3 / 5

Completeness

It explicitly answers both what ('Turn the current conversation context into a PRD and publish it to the project issue tracker') and when ('Use when user wants to create a PRD from the current context') with a concrete trigger phrase, matching the top anchor; it is not anchor 4 because the 'when' clause is already explicit and specific rather than needing more precision.

5 / 5

Trigger Term Quality

'PRD', 'create a PRD', and 'current context' are natural terms a user would say, but the description misses common variations and synonyms such as 'product requirements document', 'requirements doc', or 'spec', fitting the anchor for relevant keywords missing common variations rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

PRD synthesis from the current conversation context is a clear niche with a distinct trigger phrase, and the description is unlikely to fire for unrelated skills; there is no meaningful overlap risk, matching the top anchor.

5 / 5

Total

16

/

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

agranado2k/google-books-clojure

Path

.claude/skills/to-prd/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.