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

64

Quality

76%

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 body is an efficient, well-sequenced instruction skill: copy-paste clarification and adversarial-review prompts, a concrete PRD structure, and explicit phase gating with a user-input checkpoint. Weaknesses are minor — a validation step (self-score) with no threshold or revise-if-low loop, a slightly vague research phase, and a dangling reference to a `prd.md` command not shipped in the bundle.

Suggestions

Add a feedback loop to Phase 3: define a self-score threshold and instruct revision (e.g., "if any category scores below 70%, revise that section before saving").

Resolve the dangling `prd.md` reference — either inline the dispatch syntax for the adversarial review or remove the pointer since the file is not in the skill bundle.

Tighten Phase 1 by specifying what to extract from each search (e.g., "market context: existing solutions and known gaps") and give Phase 4 a default filename convention.

DimensionReasoningScore

Conciseness

The body is compact and phase-structured with little padding; the Phase 2 PRD outline and 100-point scoring breakdown are tight and earn their tokens. Minor trimmable bits remain — the "STOP - SKILL ALREADY LOADED" banner and repeated emphasis lines like "**WAIT for user response...**" and "Do NOT over-research" — keeping it at anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Mostly executable guidance: the Phase 0 clarification question block is copy-paste ready, the adversarial-review prompt is given verbatim in a quotable block, and the PRD section structure is concrete (FR-001 format, P0/P1/P2, 2-3 personas). Minor gaps: Phase 1's "one for domain/market context" is vague, the 100-point framework has no stated pass threshold or action if the score is low, and Phase 4 does not specify a default filename pattern.

4 / 5

Workflow Clarity

A clear six-phase sequence (clarify → research → write → adversarial review → self-score → save) with an explicit user-input checkpoint ("WAIT for user response") and skip conditions (--fast). It stops short of anchor 5 because the self-score step has no feedback loop — no threshold, revision step, or checklist — and Phase 2.5 relies on an external `prd.md` command whose dispatch syntax is not in this file.

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well organized with clearly labeled phases, so structure is appropriate. The reference to "See `prd.md` command for full dispatch syntax" points to a file that is not present in the skill bundle, an unresolved navigation pointer that keeps it below the fully clean organization of anchor 5.

4 / 5

Total

16

/

20

Passed

Description

78%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 answers both what the skill does and when to use it, with a concrete trigger clause and a reasonably distinct niche. Its main weakness is thin capability coverage — it states a single action and leans on buzzwordy phrasing ("AI-optimized", "multi-AI orchestration") rather than listing the concrete actions the skill performs.

Suggestions

Enumerate 2-3 concrete actions in the description (e.g., "Draft a structured PRD, adversarially review it via a second provider, and self-score it against a 100-point framework") so capabilities are explicit rather than implied by "multi-AI orchestration".

Add natural trigger synonyms users would say, such as "product requirements document", "spec", or "write a PRD", to broaden keyword coverage.

Trim buzzword phrasing like "AI-optimized" in favor of what the output concretely contains (phased structure, FR-001 requirements, personas, risks).

DimensionReasoningScore

Specificity

"Write an AI-optimized PRD using multi-AI orchestration" names the domain (PRD writing) and one concrete action, but does not enumerate what the skill actually does (draft, adversarially review, score, revise). It names 1-2 actions without comprehensive coverage, matching anchor 3; it lacks the several-specific-actions list of anchor 4.

3 / 5

Completeness

It explicitly answers both questions: what — "Write an AI-optimized PRD using multi-AI orchestration" — and when — "use when scoping a new feature or product". Both are concrete and explicitly stated with a trigger phrase, matching anchor 5; anchor 4 applies only when the 'when' clause could be more explicit, which is not the case here.

5 / 5

Trigger Term Quality

Trigger keywords present are "PRD", "scoping", "new feature", and "product", plus an explicit natural trigger phrase "use when scoping a new feature or product". Coverage is good but common variations like "product requirements document", "spec", or "requirements" are missing, matching anchor 4 rather than the synonym-complete anchor 5.

4 / 5

Distinctiveness Conflict Risk

PRD authoring is a fairly distinct niche with its own trigger ("scoping a new feature or product"), but the scope "new feature or product" could overlap with general planning or spec-writing skills. Mostly distinct with minor overlap risk against closely related skills, matching anchor 4.

4 / 5

Total

16

/

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.

Validation — 15 / 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.