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

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skill-prd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a crisp, well-sequenced phase workflow with concrete clarification questions and an adversarial-review feedback loop, and it wastes few tokens. Its main gaps are the unspecified dispatch mechanism for cross-provider review, a self-score with no follow-up action, and references to bundle files ('prd.md', codex-host-adapter.md) that are not present in the skill bundle.

Suggestions

Give a concrete dispatch instruction for Phase 2.5 (e.g. an explicit subagent/task call with the provider, prompt, and how to retrieve the result) instead of deferring to a 'prd.md' command that is not in the bundle.

Add a remediation rule after Phase 3 self-scoring, e.g. 'If any category scores below 70%, revise that section before saving'.

Either ship the referenced files (skills/blocks/codex-host-adapter.md, prd.md) in references/ with clear links, or remove/inlines the references so no path in the body is dangling.

DimensionReasoningScore

Conciseness

The body is a lean phase list with almost no explanation of concepts Claude already knows; the Phase 2 structure outline and 100-point breakdown are terse. Minor trimming is possible (the 'STOP - SKILL ALREADY LOADED' header and the one-sentence rationale in Phase 2.5), so it fits 'Efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place ideal of a 5.

4 / 5

Actionability

Phase 0's clarification questions and the adversarial-review prompt are copy-paste ready, and Phase 2 gives concrete formats (FR-001, SMART, P0/P1/P2). But the core of Phase 2.5 — how to actually dispatch to a second provider — has no concrete command and defers to a 'prd.md' command that is not in the bundle, and Phase 3 lists point totals without scoring criteria. This lands on 'Some concrete guidance but incomplete; missing key details', below the mostly-executable bar of 4.

3 / 5

Workflow Clarity

The sequence Phase 0→4 is explicit with checkpoints: 'WAIT for user response before proceeding', search/time limits, skip conditions ('--fast'), and an adversarial-review feedback loop (challenge → revise → note dismissed challenges). It falls just short of a 5 because the Phase 3 self-score has no remediation path — no threshold or revision instruction if the score is low.

4 / 5

Progressive Disclosure

Sections are well organized by phase and the skill is short (~90 lines), but the body references bundle paths that do not exist — 'skills/blocks/codex-host-adapter.md' and the 'prd.md' command — with no references/ directory present. Dangling, weakly-signaled references fit 'Some structure but could be better organized; references present but not clearly signaled' rather than the well-placed structure of a 4.

3 / 5

Total

14

/

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 what the skill does and when to use it, with a genuinely explicit 'use when' clause. Its weaknesses are thin action coverage (only 'write a PRD') and missing natural trigger variations like 'product requirements document' or 'requirements doc' that users would actually say.

Suggestions

Expand the 'what' with 1-2 more concrete actions, e.g. 'Write an AI-optimized PRD, run an adversarial cross-model review, and self-score it against a 100-point framework'.

Add natural trigger variations users would say: 'product requirements document', 'requirements doc', 'feature spec', 'define scope for a new feature'.

Narrow the 'when' clause to concrete triggers, e.g. 'use when the user asks for a PRD, product requirements document, or help scoping a new feature'.

DimensionReasoningScore

Specificity

The description names the domain ("Write an AI-optimized PRD") and one concrete action, with "using multi-AI orchestration" describing method rather than additional actions. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' and does not list several specific actions needed for a 4.

3 / 5

Completeness

It answers both: what — "Write an AI-optimized PRD using multi-AI orchestration"; when — "use when scoping a new feature or product". The 'when' is explicit but broad and could be more specific, matching 'Has both what and when; when could be more explicit or specific' rather than the fully concrete trigger phrases of a 5.

4 / 5

Trigger Term Quality

"PRD", "scoping a new feature or product" are relevant keywords, but common variations users naturally say — "product requirements document", "requirements doc", "feature spec", "write a spec" — are missing. This fits 'Some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

"PRD" is a clear niche with a distinct artifact, and "multi-AI orchestration" differentiates it from generic writing skills; minor overlap risk remains with general product-planning/spec-writing skills. It is 'Mostly distinct; minor overlap risk with closely related skills', not the minimal-conflict clear-niche of a 5.

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