FD prd-writer
Write PRD, 写产品需求文档。Use when: 需要写新功能 PRD（有UI/无UI）、第三方集成、功能重构、性能/安全优化需求。
Write PRD, 写产品需求文档。Use when: 需要写新功能 PRD（有UI/无UI）、第三方集成、功能重构、性能/安全优化需求。
As a process D 35/100 · Unfinished process — References files that are not bundled: ../../references/workflow-execution.md, ../../references/document-amendments.md
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 4
-
high Obfuscation
uni-zero-widthassets/integration.en.md:52Zero-width / invisible characters (possible hidden text) (4 occurrences)| Properties | Values ␀␀|
-
high Obfuscation
uni-zero-widthassets/new-feature-backend.en.md:52Zero-width / invisible characters (possible hidden text) (6 occurrences)| Properties | Values ␀␀|
-
high Obfuscation
uni-zero-widthassets/new-feature-ui.en.md:52Zero-width / invisible characters (possible hidden text) (4 occurrences)| Properties | Values ␀␀|
-
high Obfuscation
uni-zero-widthassets/refactoring.en.md:52Zero-width / invisible characters (possible hidden text) (4 occurrences)| Properties | Values ␀␀|
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../references/workflow-execution.md - warning
missing-refreference to a missing file: ../../references/document-amendments.md
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: ../../references/workflow-execution.md, ../../references/document-amendments.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 168 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2551 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 70: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 41 headings
- +3Step-by-step instructions: 168 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.