SKILLEMALL.ai

BC invoice

Creates and manages invoices as JSON files on GitHub with sequential numbering, preview, and upload.

modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files · 4 scripts body ≈ 2 900 tokens Open the sourcegithub.com analyzed 2 d ago

Creates and manages invoices as JSON files on GitHub with sequential numbering, preview, and upload.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

GeneratorGitHubTelegramFinancetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
77/100
safety, quality, tests
Safety 60%
80
Quality 40%
72
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Inputs and preconditions w 11
30
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 · 4

✓ No critical or high findings

Medium and low: 4
  • medium Exfiltration net-credential-use scripts/get-invoices.sh:24
    Credential used in a network call (verify the destination is the intended service)
    RESPONSE=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use scripts/get-invoices.sh:38
    Credential used in a network call (verify the destination is the intended service)
    RESPONSE=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use scripts/get-next-number.sh:23
    Credential used in a network call (verify the destination is the intended service)
    RESPONSE=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use scripts/push-invoice.sh:33
    Credential used in a network call (verify the destination is the intended service)
    RESPONSE=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \

Files scanned: 9. 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 57/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 12 mutating operations with no state check
  • 40Consistency. Frontmatter name (invoice) differs from the folder (netsnek-invoice)
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 45 steps
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 2900 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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 100: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 45 items
  • +4Has examples (8 code blocks)
  • +3All 4 scripts are documented

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