agentleFS
Sign inStart free
jakenutsjakenuts/agent-skills/skills/wordpress-content-manager/SKILL.md

wordpress-content-manager

Skill2 starsChanged 4 months agoMITView on GitHub

WordPress content management via REST API for managing posts. Requires Node.js and WordPress REST API credentials.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before using this skill, the agent must ensure these environment variables are set.

    line 15
  2. Very specific:

    Run the setup script after setting the required environment variables.

    line 38
  3. Very specific:

    If using Codex CLI, replace ~/.claude/skills with ~/.codex/skills.

    line 56
  4. Very specific:

    If Node.js is missing, the setup script will attempt to install it using common package managers.

    line 58
  5. Very specific:

    All commands are non-interactive and return JSON when --json is set.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

WordPress Content Manager

Manage WordPress posts via the REST API. Fully configurable via environment variables - no manual file editing required.

Required Environment Variables

Before using this skill, the agent must ensure these environment variables are set. If any are missing, ask the user for the values and set them before proceeding.

VariableDescriptionExample
WP_SITE_URLWordPress site base URLhttps://blog.example.com
WP_USERNAMEWordPress usernameadmin
WP_APP_PASSWORDWordPress Application Passwordxxxx xxxx xxxx xxxx

How to get an Application Password:

  1. Log in to WordPress admin
  2. Go to Users → Profile
  3. Scroll to "Application Passwords"
  4. Enter a name and click "Add New Application Password"
  5. Copy the generated password (spaces are optional)

Optional Environment Variables

VariableDescriptionDefault
WP_API_URLREST API base URL{WP_SITE_URL}/wp-json/wp/v2

First-Time Setup

Run the setup script after setting the required environment variables. It installs Node.js dependencies and validates the connection.

Linux/macOS

export WP_SITE_URL="https://your-site.com"
export WP_USERNAME="your-username"
export WP_APP_PASSWORD="your-app-password"
bash ~/.claude/skills/wordpress-content-manager/scripts/setup.sh

Windows (PowerShell)

$env:WP_SITE_URL = "https://your-site.com"
$env:WP_USERNAME = "your-username"
$env:WP_APP_PASSWORD = "your-app-password"
pwsh ~/.claude/skills/wordpress-content-manager/scripts/setup.ps1

If using Codex CLI, replace ~/.claude/skills with ~/.codex/skills.

If Node.js is missing, the setup script will attempt to install it using common package managers.

Commands

All commands are non-interactive and return JSON when --json is set.

Describe Connection

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs site info --json

List or Search Posts

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts list --status publish --search "keyword" --per_page 20 --page 1

View a Post

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts get 123 --json

Create a Post (HTML or Markdown)

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts create \
  --title "New Post" \
  --content-file ./post.md \
  --status draft \
  --categories 1,2 \
  --tags 5,7

Schedule a Post

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts create \
  --title "Scheduled Post" \
  --content "<p>HTML body</p>" \
  --status future \
  --date "2025-01-15T15:30:00"

Update a Post

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts update 123 \
  --title "Updated Title" \
  --status publish

Delete a Post

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts delete 123

Bulk Delete (Dry-Run First)

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts delete-many \
  --status draft \
  --search "test" \
  --dry-run

node ~/.claude/skills/wordpress-content-manager/scripts/wp-content.mjs posts delete-many \
  --status draft \
  --search "test" \
  --confirm

Advanced: Profile Files (Optional)

For convenience, you can create profile files in profiles/ to store site configurations. Environment variables always override profile values.

See references/profiles.md for the profile format.

Select a profile with --profile <name> or WP_PROFILE=<name>.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free