SKILLEMALL.ai
RU Sign in

BC sovereign-project-guardian

Project health and best practices enforcer. Checks security, quality, documentation, CI/CD, and dependencies. Produces a letter grade (A-F) with actionable fixes.

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

Project health and best practices enforcer.

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

IntegrationGitHubDockerInfrastructureData and analyticsWriting and documentstype 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
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
74
Run on models
none yet
Process rating
C
54/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

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 read-dotenv EXAMPLES.md:264
    Reads a .env file (test fixture / example file; documentation of a security skill)
    cp .env.example .env
    fixturesecurity skill

Files scanned: 3. 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")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 54/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
  • 30Running it twice. 16 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 120 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3562 tokens
  • 100Progress reporting. Reports progress
  • low 10 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 162: enough signal without eating the budget
  • +4Structure: 41 headings
  • +3Step-by-step instructions: 120 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)

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