SKILLEMALL.ai
GitHub ↗ RU Sign in

BC End-to-End API Testing Expert

Enterprise API testing assistant. Supports six modes: developer self-test, single API deep test, business flow test, security audit, defect diagnosis, and report generation. Automatically understands API docs, accumulates a global knowledge base, and requires confirmation before each step. Multi-user session isolation is enforced.

ClawHub Agent Skills author: Simon v1.0.0 MIT-0 4 files body ≈ 4 453 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

IntegrationData and analyticsInfrastructuretype 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
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
57
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
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 · 5

✓ No critical or high findings

Medium and low: 5
  • low Risky intent intent-offensive-security README.md:10
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **Security Audit Mode**: privilege escalation, unauthorized access, and sensitive data exposure checks
  • low Risky intent intent-offensive-security SKILL.md:233
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    Detect common API security issues: unauthorized access, horizontal/vertical privilege escalation, and sensitive data leakage.
    detector
  • low Risky intent intent-offensive-security SKILL.md:240
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Horizontal privilege escalation: user A accesses user B's resource (e.g. modify another user's order).
  • low Risky intent intent-offensive-security SKILL.md:241
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Vertical privilege escalation: normal user calls admin-only APIs.
  • low Risky intent intent-offensive-security SKILL.md:245
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Use provided accounts to obtain tokens and craft privilege escalation requests.

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Enterprise API testing assistant. Supports six modes: developer se… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • 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")

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 18 mutating operations with no state check
  • 40Consistency. Frontmatter name (End-to-End API Testing Expert) differs from the folder (full-flow-testing)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4453 tokens
  • 100Steps. 136 steps
  • 100Failures and branches. 13 branches, has a failure section
  • 100Progress reporting. Reports progress
  • low 15 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (30 tags): a typed call is more reliable

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 332: enough signal without eating the budget
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 136 items
  • +4Has examples (7 code blocks)

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

External checks

ClawHub: clean
This is a disclosed API-testing assistant that creates local workspaces, runs user-confirmed tests, and writes reports, but users should handle credentials and shared knowledge-base updates carefully.
LLM: benign (high) · VirusTotal: · 29 May 2026