SKILLEMALL.ai

AC openclaw-plus

A modular super-skill combining developer and web capabilities. Use when the user needs Python execution, package management, git operations, URL fetching, or API interactions. Triggers include requests to run code, install packages, check git status, commit changes, fetch web content, or call APIs. This skill provides a unified workflow for development and web automation tasks.

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

A modular super-skill combining developer and web capabilities.

As a process C 60/100 · Has gaps — weak spots: inputs and preconditions

ProcedureSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
60/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
50
Tools and files w 18
60
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
  • 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: 10. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5378 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 60/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (web, git, python) that frontmatter does not declare
  • 60Steps. 134 steps, 4 vague phrases
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 5378 tokens
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 top-level sections: this looks like several domains in one skill
  • medium 10 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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)
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 381: enough signal without eating the budget
  • +4Structure: 46 headings
  • +3Step-by-step instructions: 134 items
  • +3Output format is stated explicitly
  • +4Has examples (29 code blocks)
  • +1License stated

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