CF docs-governance
Use when writing, restructuring, auditing, or reviewing Cherry Studio repository documentation, READMEs, JSDoc, comments, Agent instructions, or paired English/Chinese docs, including source-linked documentation impact checks.
A skill for auditing Cherry Studio docs: checks READMEs, JSDoc, comments, and agent instructions. Promises help rewriting and reviewing text, including paired English-Chinese documentation.
Checks show 68 quality score against 33 process score. No critical findings, but broken references and missing files are flagged. One file, 529 tokens—modest scope. No model runs or sandbox testing.
If you systematically maintain project documentation, this could work as a first-pass helper. Don't rely on it though: broken links will confuse more than clarify. Install only if you already have your own review process—this skill is an add-on, not a replacement.
Use when writing, restructuring, auditing, or reviewing Cherry Studio repository documentation, READMEs, JSDoc, comments, Agent instructions, or paired…
As a process F 33/100 · No process to follow — References files that are not bundled: ../../../docs/i18n/README.md, ../../../docs/i18n/translation-rules.md, ../../../docs/i18n/terminology.md
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../docs/i18n/README.md - warning
missing-refreference to a missing file: ../../../docs/i18n/translation-rules.md - warning
missing-refreference to a missing file: ../../../docs/i18n/terminology.md
Process rating: all ten parameters 33/100
- 0Tools and files. 3 referenced file(s) missing: ../../../docs/i18n/README.md, ../../../docs/i18n/translation-rules.md, ../../../docs/i18n/terminology.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
- 30Running it twice. 1 mutating operations with no state check
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 529 tokens
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 226: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 5 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.