SKILLEMALL.ai
GitHub ↗ RU Sign in

CD vscode-release-notes-writer

Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.

foryourhealth111-pixel/Vibe-Skills Agent Skills author: foryourhealth111-pixel Apache-2.0 4 files body ≈ 1 367 tokens Open the sourcegithub.com↗ analyzed 30 h ago

Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.

As a process D 41/100 · Unfinished process — References files that are not bundled: ../../instructions/release-notes-writing.instructions.md, ../../instructions/docs-writing.instructions.md

AnalyzerVS CodeGitHubSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
D
41/100
Unfinished process
References files that are not bundled: ../../instructions/release-notes-writing.instructions.md, ../../instructions/docs-writing.instructions.md
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../../instructions/release-notes-writing.instructions.md
  • warning missing-ref reference to a missing file: ../../instructions/docs-writing.instructions.md

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: ../../instructions/release-notes-writing.instructions.md, ../../instructions/docs-writing.instructions.md
  • 0Tools and files. 2 referenced file(s) missing: ../../instructions/release-notes-writing.instructions.md, ../../instructions/docs-writing.instructions.md
  • 0Result and completion. Does not say what the result is
  • 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
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 13 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1367 tokens
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (6 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)
  • +3Description length 94: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 13 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.