SKILLEMALL.ai
GitHub ↗ RU Sign in

BC beaverhabits

Track and manage your habits using the Beaver Habit Tracker API.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 769 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Track and manage your habits using the Beaver Habit Tracker API.

As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
90
Quality 40%
72
Run on models
none yet
Process rating
C
64/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Exfiltration net-credential-use SKILL.md:49
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $BEAVERHABITS_API_KEY" \
  • medium Exfiltration net-credential-use SKILL.md:56
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $BEAVERHABITS_API_KEY" \

Files scanned: 1. 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")

Process rating: all ten parameters 64/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 769 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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

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