SKILLEMALL.ai

BF Dilbert Skill

This skill fetches a random Dilbert comic from an archive source and sends it to the chat.

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

This skill fetches a random Dilbert comic from an archive source and sends it to the chat.

As a process F 24/100 · Will not run — weak spots: steps, result and completion, when it triggers

Referencetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
75/100
safety, quality, tests
Safety 60%
99
Quality 40%
38
Run on models
none yet
Process rating
F
24/100
Will not run
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-webhook-url daily_dilbert.sh:13
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -s -X POST "https://api.telegram.org/bot<YOUR_BOT_TOKEN>/sendPhoto" \
    placeholder

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 24/100

  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (Dilbert Skill) differs from the folder (dilbert)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Execution cost. Instruction body is 64 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 90: 120–800 characters recommended
  • +4Structure: 1 headings, hard to scan
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -15SKILL.md body under 300 characters: nearly empty
  • +1No license
  • +2Single-language instructions

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