AC windows-notifier
Send native Windows desktop notifications for local reminders, alerts, and background-attention events. Use when the user wants a Windows popup, a local toast notification, or when reminder/alert messages should prefer local desktop notification instead of only chat delivery.
As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:39High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Zcn+TtXH…Lww==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:71High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…8CM+MzKM…4lA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:89High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-+NYs2QeMWy+GWFO…UmJ+93Q5…iX3/fpC6afS8Dhb/gz7R7eg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:98High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…64i+awpwXqsGBYWkkqMtnbXgrMD+yj7r…ibA==",
detector
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 85Steps. 20 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 620 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 276: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.