CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

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 tight, well-structured instruction-only skill body: it is maximally lean, gives a concrete section-by-section layout spec with an explicit output contract, and is appropriately self-contained with no bundle files. The only gaps are the lack of an example artifact/HTML skeleton and an explicit output-verification step.

Suggestions

Add a minimal example artifact or HTML skeleton under the Output contract so the expected result is copy-paste concrete rather than only structurally described.

Append a final verification step to the Workflow (e.g., confirm the output fits one page and uses the active design system's color/typography sections) to close the validation gap.

DimensionReasoningScore

Conciseness

The ~30-line body contains zero concept explanations or padding — every line instructs ("Three-line summary at the top — what, who, why now", "accent used twice max"), fully matching the lean anchor-5 example.

5 / 5

Actionability

Guidance is highly concrete — section-by-section layout specs ("'Success metrics' table with metric / target / measurement", "as-a / I-want / so-that format", "'Scope' milestone tracker (3–4 phases)") plus a literal output contract — but no sample HTML skeleton or example artifact is provided and the artifact body is elided, leaving minor gaps versus the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The 4-step sequence (read DESIGN.md → identify feature and audience → layout → styling constraints) is clear and specific, but there is no explicit verification of the output (e.g., confirming the one-page constraint or design-system adherence), leaving the minor validation gap of anchor 4; the task is low-risk generation so no feedback-loop cap applies.

4 / 5

Progressive Disclosure

The body is under 50 lines, no bundle files exist, and no external references are needed; the well-organized 'Workflow' and 'Output contract' sections satisfy the simple-skill guideline that progressive disclosure can score 5 on well-organized sections alone.

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 description: it states a clear deliverable with an explicit, well-triggered 'Use when' clause and concrete quoted trigger terms in third-person voice. Its only weaknesses are the absence of a few common synonyms (e.g., "product requirements document") and slight overlap risk from the generic term "spec".

DimensionReasoningScore

Specificity

"Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions" enumerates seven concrete deliverable components, giving comprehensive coverage that goes beyond the 1–2 items of a score-3 description, though it is phrased as a noun list rather than the explicit action verbs of the anchor-5 example.

4 / 5

Completeness

It clearly states what the skill produces ("Product spec / PRD as a single page" with enumerated sections) and explicitly answers when to use it ("Use when the brief mentions 'PRD', 'spec', 'product spec', 'feature brief', or '需求文档'") with concrete trigger phrases, matching the anchor-5 pattern exactly.

5 / 5

Trigger Term Quality

The quoted triggers "PRD", "spec", "product spec", "feature brief", "需求文档" are natural phrases users would say, but common synonyms like "product requirements document", "requirements doc", or "one-pager" are missing, keeping it just short of the comprehensive anchor-5 set.

4 / 5

Distinctiveness Conflict Risk

"PRD", "product spec", and "feature brief" carve a clear niche, but the bare trigger "spec" could plausibly fire for an API-spec or design-spec skill, leaving minor overlap risk consistent with the anchor-4 case rather than the minimal-conflict anchor 5.

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.

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

nexu-io/open-design

Path

design-templates/pm-spec/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.