SKILLEMALL.ai
GitHub ↗ RU Sign in

AB compass

Navigating the skill ecosystem and guiding onboarding. Lists agents, recommends best fit for tasks. Don't use for task execution (Nexus), agent design (Architect).

simota/agent-skills Agent Skills author: simota 8 files body ≈ 4 016 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Navigating the skill ecosystem and guiding onboarding.

As a process B 68/100 · Nearly there — weak spots: inputs and preconditions

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
95
Quality 40%
91
Run on models
none yet
Process rating
B
68/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
50
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

    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 · 5

    ✓ No critical or high findings

    Medium and low: 5
    • low Risky intent intent-offensive-security reference/catalog.md:73
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | **Breach** | Red team | Attack-scenario design, MITRE ATT&CK | No |
    • low Risky intent intent-offensive-security reference/catalog.md:74
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | **Probe** | Dynamic security testing | OWASP ZAP / Burp Suite, penetration testing | Mixed |
    • low Risky intent intent-offensive-security reference/patterns.md:118
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | Red team | Breach | Attack-scenario design |
    • low Risky intent intent-offensive-security reference/patterns.md:156
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Sentinel (static) → Probe (dynamic) → Breach (red team)
    • low Risky intent intent-offensive-security reference/recipes-directory.md:70
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **probe**: zap★ / burp / nuclei / pentest / api / mobile / recon

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 68/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Execution cost. Instruction body is 4016 tokens
    • 100Steps. 56 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 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 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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 163: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 56 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (7 of 7)

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