agentleFS
chellehonikerchellehoniker/claude-code-storytelleros/skills/wordpress-pages/SKILL.md

wordpress-pages

Skill1 starsChanged 12 days agoMITView on GitHub

Use when the user wants to update or create static pages on their connected WordPress site (About, Contact, Books, Privacy, etc.). Triggers on "update my About page", "create a Books page", "edit the Contact page", "what does my homepage look like?".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not delete pages without confirming.

    line 56
  2. Distinctive:

    Do not change the slug of a published page without warning the user — it breaks any external link to that URL.

    line 57

≈ “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 pages

Pages are the static content on a WordPress site (About, Contact, Books, Privacy, Terms, etc.). Different from posts: no categories, no tags, usually long-lived.

Tools

stos_wp_pages_list({ status, search, page, per_page })
stos_wp_pages_get({ id })
stos_wp_pages_create({ fields: { title, content, excerpt, slug, status, featured_media } })
stos_wp_pages_update({ id, fields: { ... } })
stos_wp_pages_delete({ id })   // moves the page to WordPress trash; permanent deletion is done in WordPress itself

All tools take an optional penNameId — the user can connect one WordPress site per pen name plus an account default. Omit for the account default; pass a pen name id (from stos_pen_names_list) to act on that pen name's site. When the user has multiple pen names and it's ambiguous which site they mean, ask.

Field shapes match wordpress-posts minus categories, tags, and date (pages don't schedule the same way).

Patterns

Refresh the About page

// Find the page first
const list = await stos_wp_pages_list({ search: "About" });
const aboutPage = list.data[0];

stos_wp_pages_update({
  id: aboutPage.id,
  fields: {
    content: "<p>Updated bio...</p>",
  }
});

Create a new "Books" landing page

stos_wp_pages_create({
  fields: {
    title: "Books",
    slug: "books",
    content: "<h2>Available now</h2><p>...</p>",
    status: "publish",
  }
});

Anti-patterns

  • Do not delete pages without confirming. Pages often anchor menu items and breaking links is silent.
  • Do not change the slug of a published page without warning the user — it breaks any external link to that URL.

Composes well with

  • wordpress-media — featured images for landing-style pages

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.