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

78%

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 ./.agents/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 tight, well-structured instruction skill: the behavioral rules are crisp, the PRD template makes the deliverable unambiguous, and the seam checkpoint gives the workflow a real validation moment. It consistently sits just below excellent due to minor padding, the unspecified tracker-publish mechanics, and the absence of any post-publish verification.

Suggestions

Tighten the template guidance by merging "A LONG, numbered list" with the "extremely extensive" instruction into one line, and trim the prototype-exception paragraph to its core rule.

Add a brief post-publish verification cue (e.g., "confirm the ticket URL and label applied") to close the workflow with a feedback checkpoint.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it never explains what a PRD is and leads with a sharp behavioral rule ("Do NOT interview the user — just synthesize what you already know") — but has minor trimmable padding such as the redundant "A LONG, numbered list" / "extremely extensive" emphasis and the wordy prototype-exception paragraph.

4 / 5

Actionability

The inline PRD template gives copy-paste-ready section structure with a concrete user-story format and example, and the publishing step carries an explicit conditional labeling rule; the remaining gap is that "publish it to the project issue tracker" gives no concrete command, though this is deliberately tracker-agnostic. This is an instruction-only skill, so the absence of code is not penalized.

4 / 5

Workflow Clarity

A clear three-step sequence (explore repo, sketch seams, write and publish) with an explicit checkpoint — "Check with the user that these seams match their expectations" — before the artifact is produced; no destructive or batch operation applies, but there is no post-publish verification, keeping it below the full-feedback-loop anchor.

4 / 5

Progressive Disclosure

Sections are well organized ("## Before you start", "## Process", "## What happens next") with zero external references and everything needed at invocation time inline; at ~80 body lines it exceeds the under-50-line simple-skill exception, and the large inline template is the only structural question, fitting the good-structure-with-minor-gaps anchor.

4 / 5

Total

16

/

20

Passed

Description

70%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 solid description that clearly states what the skill does and when to use it, with the exact natural trigger phrase a user would say. Its main gaps are limited action coverage and no synonym variations of "PRD" for triggering.

Suggestions

Add one or two more concrete actions (e.g., "synthesize the repo's current state and decision records into the PRD") to lift specificity beyond two actions.

Include trigger synonyms such as "product requirements document", "write a PRD", or "turn this conversation into a spec" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (PRD, issue tracker) and exactly two concrete actions — "Turn the current conversation context into a PRD" and "publish it to the project issue tracker" — matching the 1-2-concrete-actions anchor rather than the several-actions anchors.

3 / 5

Completeness

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") are explicit; the when clause offers only a single trigger phrasing and could be more varied, keeping it below the concrete-trigger-phrases anchor.

4 / 5

Trigger Term Quality

The natural user phrase "create a PRD from the current context" is present, but synonyms such as "product requirements document", "spec", or "write requirements" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

PRD synthesis is a clear niche with a distinct trigger, but the tracker-publishing half is generic and there is minor overlap risk with adjacent spec- or ticket-writing skills, so it fits the "mostly distinct" anchor rather than the minimal-conflict anchor.

4 / 5

Total

15

/

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-haskell

Path

.agents/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.