CD sync-changelog
Use after a release succeeds, when maintainers need to sync apps/kimi-code/CHANGELOG.md into docs/en/release-notes/changelog.md and docs/zh/release-notes/changelog.md, then open a PR on a dedicated branch.
Use after a release succeeds, when maintainers need to sync apps/kimi-code/CHANGELOG.md into docs/en/release-notes/changelog.md and…
As a process D 44/100 · Unfinished process — References files that are not bundled: ..., ../configuration/config-files.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
body-longSKILL.md body ≈ 9299 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ... - warning
missing-refreference to a missing file: ../configuration/config-files.md
Process rating: all ten parameters 44/100
- 0Tools and files. 2 referenced file(s) missing: ..., ../configuration/config-files.md
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 9299 tokens: crowds the task out of the window
- 65Failures and branches. 3 branches
- 100Steps. 118 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (5 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
- +1No license
- +2Single-language instructions
- +3Description length 205: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 118 items
- +4Has examples (23 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.