write-mrd

Generate a market requirements document (MRD) from a product idea and save it as Markdown under the current project's markdown/ directory. Use when the user asks to write, draft, create, produce, or refine an MRD, market requirements document, product opportunity document, market demand analysis, product idea validation document, or asks for "写 MRD", "市场需求文档", "产品立项文档", "产品机会分析", especially when input is only an idea and the output should be structured, visual, and decision-oriented.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 well-structured, instruction-oriented skill body with a clear sequenced workflow, concrete naming/output guidance, and clean one-level-deep references to real bundle files. It could improve by adding an explicit error-recovery loop in the self-check step and tightening a few verbose list items.

Suggestions

Add an explicit fix-and-retry loop to step 6: if a self-check criterion fails, state that the MRD should be revised and re-checked before the final response.

Tighten the 'MRD Writing Rules' and self-check lists by merging overlapping items (e.g., assumption-naming appears in both Inputs and the self-check) to reduce token cost.

Inline a one-line pointer to the playbook's minimum MRD structure so the body remains actionable even before the referenced file is opened.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude already knows what an MRD is, avoiding concept padding; a few sections (e.g., the self-check list and writing rules) could be tightened slightly but every item is actionable.	4 / 5
Actionability	Provides concrete, executable guidance — file-naming patterns ('markdown/<产品或主题>-MRD-<YYYYMMDD>.md'), diagram formats, and a self-check checklist — but delegates the actual MRD structure to referenced files, leaving minor gaps in the body itself.	4 / 5
Workflow Clarity	A clear six-step Required Workflow ends with an explicit self-check checkpoint and concrete verification criteria, but there is no explicit fix-and-retry feedback loop for when a check fails.	4 / 5
Progressive Disclosure	The body is an overview that points one level deep to clearly signaled, real bundle files ('Follow references/mrd-playbook.md for the writing logic. Use assets/mrd-template.md as the output skeleton'), with content appropriately split and easy to navigate.	5 / 5
	Total	17 / 20 Passed

Description

95%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, third-person description that crisply states what the skill does and when to invoke it, with rich bilingual trigger synonyms. The only minor gap is that the action list is narrow (generate + save) rather than enumerating several distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the MRD domain and concrete actions ('Generate a market requirements document (MRD) from a product idea and save it as Markdown under the current project's markdown/ directory'), but coverage is focused on a single generate-and-save task rather than multiple distinct actions.	4 / 5
Completeness	Explicitly answers both 'what' (generate and save an MRD as Markdown) and 'when' ('Use when the user asks to write, draft, create, produce, or refine an MRD…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage in both English ('write, draft, create, produce, or refine an MRD, market requirements document, product Opportunity document, market demand analysis, product idea validation document') and Chinese ('写 MRD', '市场需求文档', '产品立项文档', '产品机会分析'), including synonyms.	5 / 5
Distinctiveness Conflict Risk	Targets a clear MRD niche with distinctive bilingual triggers unlikely to fire for unrelated skills; minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: digoal/blog
Path: skills/write-mrd/SKILL.md
Commit: 3b9c83d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.