SKILLEMALL.ai
GitHub ↗ RU Sign in

BB Business Automation Strategy — AfrexAI

Before building anything, map where time and money leak.

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

Before building anything, map where time and money leak.

As a process B 65/100 · Nearly there — weak spots: when it triggers, consistency

GeneratorZapierInfrastructureData and analyticsAI and agentstype 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
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
B
65/100
Nearly there
When it triggers w 12
20
Consistency w 8
40
Tools and files w 18
60
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.
  2. 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: 2. 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")
  • warning body-long SKILL.md body ≈ 6912 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 65/100

  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (Business Automation Strategy — AfrexAI) differs from the folder (afrexai-automation-strategy)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 6912 tokens
  • 85Steps. 127 steps, 2 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 16 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)
  • +3Description length 56: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 58 headings
  • +3Step-by-step instructions: 127 items
  • +3Output format is stated explicitly
  • +4Has examples (13 code blocks)

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