SKILLEMALL.ai

BC backstage

Anti-drift protocol script. Ensures parity between docs and system. Triggers: 'bom dia PROJECT' / 'good morning PROJECT' (load project context with health checks)

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

Anti-drift protocol script.

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureVS CodeGitHubAI and agentsPersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5536 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "type"
  • note frontmatter-key unknown frontmatter key "status"
  • note frontmatter-key unknown frontmatter key "requires"
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 54/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
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, web, git) that frontmatter does not declare
  • 70Execution cost. Instruction body is 5536 tokens
  • 100Steps. 155 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • low 14 top-level sections: this looks like several domains in one skill

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
  • -5TODO / placeholder text left in the skill
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -238 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 162: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 155 items
  • +4Has examples (16 code blocks)
  • +1License stated

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