SKILLEMALL.ai
GitHub ↗ RU Sign in

CC wordpress-content-rest-api

Use the WordPress REST API for content operations only: auth setup (Application Password and Bearer), safe read/write flows for posts/pages/media, draft/publish/update patterns, taxonomy assignment, pagination/search, retry/rate-limit handling, and dry-run-first safety.

ClawHub Agent Skills author: Sebastian Gansca v0.1.0 MIT-0 6 files body ≈ 538 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

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
C
66/100
safety, quality, tests
Safety 60%
60
Quality 40%
74
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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

    ✓ No critical or high findings

    Medium and low: 8
    • medium Exfiltration net-credential-use references/auth.md:11
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -u "$WP_USER:$WP_APP_PASSWORD" \
    • medium Exfiltration net-credential-use references/auth.md:26
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -H "Authorization: Bearer $WP_BEARER_TOKEN" \
    • medium Exfiltration net-credential-use references/content-flows.md:10
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -u "$WP_USER:$WP_APP_PASSWORD" \
    • medium Exfiltration net-credential-use references/content-flows.md:14
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -u "$WP_USER:$WP_APP_PASSWORD" \
    • medium Exfiltration net-credential-use references/content-flows.md:21
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -u "$WP_USER:$WP_APP_PASSWORD" \
    • medium Exfiltration net-credential-use references/content-flows.md:38
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -u "$WP_USER:$WP_APP_PASSWORD" \
    • medium Exfiltration net-credential-use references/content-flows.md:52
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -u "$WP_USER:$WP_APP_PASSWORD" \
    • medium Exfiltration net-credential-use references/query-and-taxonomy.md:31
      Credential used in a network call (verify the destination is the intended service)
      curl -i -sS -u "$WP_USER:$WP_APP_PASSWORD" \

    Files scanned: 6. 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: Use the WordPress REST API for content operations only: auth setup… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

    Process rating: all ten parameters 52/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 6 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 100Steps. 33 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 538 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 270: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 33 items
    • +4Reference files are cited in the instructions (4 of 4)

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

    External checks

    ClawHub: clean
    This skill is narrowly scoped to WordPress content management and clearly discloses its credential and write-access requirements.
    LLM: benign (high) · VirusTotal: · 28 May 2026