CtrlK
BlogDocsLog inGet started
Tessl Logo

pm-spec

Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured single-purpose skill that assumes Claude's competence and gives concrete layout guidance. The only notable gaps are the missing HTML starter template and the absence of an output-verification checkpoint or DESIGN.md fallback.

DimensionReasoningScore

Conciseness

Roughly 25 lines with no concept over-explanation; it assumes Claude knows semantic HTML and user-story format, and every line is actionable guidance, matching the lean-and-efficient anchor.

5 / 5

Actionability

Concrete structural guidance (section formats, "metric / target / measurement" columns, "accent used twice max") but no HTML starter template — the output contract shows only a `<!doctype html>...` placeholder — leaving a minor executable gap.

4 / 5

Workflow Clarity

A clear 4-step sequence is present, but there is no verification checkpoint (e.g., confirm all sections present) and step 1 ("Read the active DESIGN.md") has no fallback if absent, which are minor validation gaps.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a simple, single-purpose, under-50-line document with well-organized Workflow and Output contract sections, so the simple-skills exception applies and self-contained structure scores full marks.

5 / 5

Total

18

/

20

Passed

Description

83%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 strong, concise description that clearly states what the skill produces and gives explicit trigger guidance with natural keywords. The main weaknesses are the noun-heavy framing (contents vs. actions) and the generic "spec" trigger creating minor overlap risk.

DimensionReasoningScore

Specificity

Lists several concrete spec sections ("problem, success metrics, scope, user stories, design notes, rollout plan, open questions"), but these describe the artifact's contents rather than verb-based actions, so it sits just below the comprehensive-action anchor.

4 / 5

Completeness

Explicitly answers both what ("Product spec / PRD as a single page — problem, success metrics, scope...") and when ("Use when the brief mentions 'PRD', 'spec', 'product spec', 'feature brief', or '需求文档'") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ("PRD", "spec", "product spec", "feature brief", "需求文档") with a multilingual synonym, but omits common variations like "product requirements document" and "requirements doc".

4 / 5

Distinctiveness Conflict Risk

The PRD/product-spec niche is clear, but the bare trigger "spec" creates minor overlap risk with technical-spec or API-spec skills, keeping it just below the minimal-conflict anchor.

4 / 5

Total

17

/

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
nexu-io/open-design
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.