CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-prd

Write an AI-optimized PRD using multi-AI orchestration — use when scoping a new feature or product

59

Quality

68%

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

The content is an efficient, well-sequenced instruction skill with concrete paste-ready prompts and a self-score rubric. Its main weakness is the dangling reference to a missing prd.md file, which slightly undermines both actionability and navigation.

Suggestions

Inline the adversarial-review dispatch syntax (or remove the 'See prd.md' reference) so the guidance is fully executable without a missing file.

Add an explicit validation gate after the self-score phase (e.g., 'only save if score >= threshold') to strengthen the workflow feedback loop.

Trim the 'STOP - SKILL ALREADY LOADED' banner and time-budget lines to push conciseness toward a 5.

DimensionReasoningScore

Conciseness

The phased body is lean with no padding or beginner-concept explanations, though minor non-essential lines (the STOP banner, time budgets) keep it just short of a 5.

4 / 5

Actionability

Concrete guidance is provided as a literal clarification block, a numbered PRD section list, a point-based self-score rubric, and an exact adversarial-review prompt; the missing inline dispatch syntax (referenced to an absent prd.md) is a minor gap.

4 / 5

Workflow Clarity

Phase 0 to 4 sequencing is explicit with a hard checkpoint ('WAIT for user response before proceeding to Phase 1') and an adversarial review feedback loop, but lacks an error-recovery checklist that would reach 5.

4 / 5

Progressive Disclosure

The under-50-line single-purpose body is well-organized into clear phases, but it references a non-existent 'prd.md' for dispatch syntax, a minor navigation defect that prevents 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.

The description cleanly states a purpose and an explicit trigger, but its action list and trigger vocabulary are narrow for a top score. It is solid and usable rather than comprehensive.

Suggestions

Expand the action list to name several concrete PRD-related actions (e.g., 'draft, score, and adversarially review a PRD') to lift specificity.

Add natural trigger synonyms such as 'product spec', 'requirements doc', or 'feature brief' so the trigger term coverage is comprehensive.

Tighten the 'when' clause into a fuller trigger phrase set to move completeness from 4 to 5.

DimensionReasoningScore

Specificity

Names the domain (PRD writing) plus one concrete action ('Write an AI-optimized PRD using multi-AI orchestration'), but does not enumerate multiple distinct actions as required for a 4.

3 / 5

Completeness

Explicitly answers both what ('Write an AI-optimized PRD using multi-AI orchestration') and when ('use when scoping a new feature or product'), matching the anchor where both are present but the 'when' could be more comprehensive.

4 / 5

Trigger Term Quality

Includes one natural trigger phrase ('use when scoping a new feature or product') and the 'PRD' keyword, but lacks common synonyms like 'product spec' or 'requirements doc' that would warrant a 4.

3 / 5

Distinctiveness Conflict Risk

The 'AI-optimized PRD via multi-AI orchestration' niche is mostly distinct with only minor overlap risk against generic planning/spec skills, fitting the 'mostly distinct' anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nyldn/claude-octopus
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.