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

75%

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

The canonical home for this skill is to-prd in agranado2k/google-books-clojure

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-structured, token-efficient instruction skill with a concrete process, an explicit user checkpoint, and a complete PRD template with an example. The main gaps are minor: no verification step after publishing and a publish step that depends on external project files for its mechanism.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — it never explains what a PRD is and packs high-value guidance like 'Do NOT interview the user — just synthesize' — with only minor trims available (the opening sentence partly restates the description).

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: specific file pointers (docs/domain-glossary.md, docs/adr/), an explicit ready-for-agent labeling rule, and a complete PRD template with a worked user-story example; the publish step delegates tracker specifics to project files rather than giving a direct mechanism.

4 / 5

Workflow Clarity

The three-step process (explore, sketch seams, write and publish) is clearly sequenced with an explicit checkpoint ('Check with the user that these seams match their expectations') and an ask-once rule for the tracker; only a post-publish verification step is missing, and no destructive/batch cap applies.

4 / 5

Progressive Disclosure

This single-file skill has no bundle directories, keeps all content appropriately inline, uses clear section headers, and references only one-level-deep project files (AGENTS.md, docs/adr/); it is well organized but slightly over the ~50-line threshold where organization alone would merit a 5.

4 / 5

Total

16

/

20

Passed

Description

62%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, honest description that clearly states what the skill does and when to use it, with a distinctive PRD niche. Its main weaknesses are limited action coverage and thin trigger-term variety — no synonyms or expanded phrasing beyond 'PRD'.

Suggestions

Expand the what-clause with one or two more concrete actions, e.g. 'synthesizes requirements, sketches test seams, and labels the ticket ready-for-agent'.

Broaden trigger coverage with natural synonyms users would say, such as 'product requirements document', 'spec', or 'turn this conversation into a PRD'.

Make the when-clause discriminating rather than restating the what, e.g. 'Use when requirements are already settled and the user wants to formalize them; not for interrogating unclear requirements.'

DimensionReasoningScore

Specificity

The description names two concrete actions — 'Turn the current conversation context into a PRD' and 'publish it to the project issue tracker' — but coverage stops there, matching the anchor for 1-2 concrete actions rather than the several specific actions of a 4.

3 / 5

Completeness

It 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'), but the when-clause mostly restates the what without adding discriminating trigger phrases, so it falls just short of the anchor-5 example.

4 / 5

Trigger Term Quality

'PRD' and 'create a PRD' are the relevant natural keywords, but common variations like 'product requirements document', 'spec', or 'requirements doc' are absent, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'PRD from the current conversation context' is a clear niche with a distinctive trigger term, with only minor overlap risk against generic spec- or requirements-writing skills.

4 / 5

Total

14

/

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/tic-tac-toe-with-agentic-sdlc

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.