SKILLEMALL.ai
GitHub ↗ RU Sign in

AC wordpress-rest-api

Work with the WordPress REST API for route discovery, authentication, reads and writes, core endpoint selection, and custom namespace inspection. Use when a WordPress task needs `/wp-json`, application passwords, cookie or nonce auth, post or media endpoints, settings access, or live discovery of plugin-defined REST routes.

ClawHub Agent Skills author: Matthew Murphy v0.6.0 7 files · 1 script body ≈ 885 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

IntegrationWordPressInfrastructuretype 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
A
96/100
safety, quality, tests
Safety 60%
99
Quality 40%
91
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Exfiltration net-credential-use scripts/inspect-rest-api.sh:109
      Credential used in a network call (verify the destination is the intended service) (test fixture / example file)
      CURL_ARGS+=(--user "${USER_NAME}:${APP_PASSWORD}")
      fixture

    Files scanned: 7. 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 50/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 27 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 885 tokens
    • 100Running it twice. No mutating operations

    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 325: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 27 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: suspicious
    The skill mostly does what it says, but its helper can send WordPress application-password credentials to an unrelated URL if a full route URL is supplied.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026