SKILLEMALL.ai
GitHub ↗ RU Sign in

CD codenotify

codenotify

The skillemall take

The skill promises code change notifications based on its name and workflow type. One instruction file at 849 tokens, no scripts or extra logic. Testing shows a C grade: quality at 64, process at 47. No critical or medium findings, but that just means nothing overtly harmful was spotted — doesn't confirm it works as intended.

No model runs, no sandbox testing. Compatible with most platforms including Claude and Cursor. Install if you're okay with a bare-bones instruction set and no guarantees. Not production-ready.

microsoft/vscode Claude Code author: microsoft MIT 1 file body ≈ 849 tokens Open the sourcegithub.com↗ analyzed 2 d ago

codenotify

As a process D 47/100 · Unfinished process — weak spots: when it triggers, inputs and preconditions, failures and branches

ProcedureGitHubSoftware 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
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
D
47/100
Unfinished process
When it triggers w 12
0
Inputs and preconditions w 11
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.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 47/100

  • 0When it triggers. No condition that starts the skill
  • 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
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (git) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 27 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 849 tokens

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 10: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 27 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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