Abilities for AI · The Engine · Wicked Evolutions

Abilities for AI / 01 — In one breath

What it is. Why it exists. How it works. What it brings you.

A reading of the engine before any catalogue. The shape of the plugin in operator language — what it is, why it had to exist, what changes the day you install it.

What

A WordPress plugin that registers every platform surface as a named, callable ability.

Posts, blocks, taxonomies, users, options, themes, plugins, files, cron, revisions, multisite — each surface becomes a small, well-described operation an AI can discover, plan with, and run.

Why

So an AI can operate WordPress without raw database access or guesswork.

Without a registry, the AI is improvising against the database. With one, the AI is calling intentions you've named. Safer for the site. Clearer for you. Cheaper to run.

How

Each ability has a name, a description, an input schema, a permission, and an annotation.

When the Adapter exposes them, the AI sees the catalogue and the safety hints together. It can pick the right ability for the job — or decline, citing the gate that stopped it.

What it brings

A WordPress site that can be operated by talking to it.

The admin panel becomes optional. Most of what you used to click — drafting, publishing, tagging, configuring, auditing — is now a sentence. The dashboard is for review, not for routine.

Abilities for AI / 02 — Coverage

Every WordPress surface. All of it.

Not a curated subset. Not "the easy parts." The whole platform — the surfaces operators actually touch, the surfaces only developers used to touch, the surfaces nobody touched because they lived three layers deep in the admin. All registered. All callable. All gated.

Module

Content

Posts, pages, custom post types, drafts, revisions, scheduling.

Module

Blocks

Block patterns, reusable blocks, block-level edits inside any post.

Module

Taxonomies

Categories, tags, custom taxonomies, term relationships, hierarchies.

Module

Media

Library, attachments, alt text, image sizes, replacements.

Module

Users & roles

Accounts, capabilities, role assignment, sessions.

Module

Comments

Threads, moderation, spam handling, comment meta.

Module

Options & settings

Site identity, permalinks, reading, writing, discussion, every options table key.

Module

Themes

Active theme, child themes, template parts, theme.json, customiser fields.

Module

Plugins

Install, activate, deactivate, update, delete — gated by scope.

Module

Filesystem

Theme files, plugin files, uploads — read and write where the OS allows.

Module

Cron & jobs

Scheduled events, queues, retries, the actual reason something didn't run.

Module

Multisite

Network admin, sites, users-across-sites, network options.

Module

REST & routes

Every registered route, namespace, schema — discoverable, callable.

Module

Revisions & history

Diff any post against any past version. Roll back. Compare authors.

Module

Diagnostics

Site health, security posture, taxonomy health, theme audit — compiled in one call.

Open source · GPL-2.0-or-later · Coverage growing every release

Abilities for AI / 03 — Capacity

Possibilities never accessed in WordPress before.

Tier 1 is "do things" — the calls every product in this space gets to. Abilities for AI keeps going. The next two tiers are where the work actually changes.

Tier 02

Understand state.

Compiled diagnostics. Eight sequential checks become one.

The AI doesn't issue ten read calls to figure out the state of your site. One ability does the cross-correlation server-side and returns the picture. Site health, security posture, taxonomy integrity, theme audit, network overview — each one a single call.

faster · cheaper · more accurate · less drift

Tier 03

Understand meaning.

Editorial intelligence on top of the operations.

Voice signatures per author. Opening patterns across every post. Series arcs. Headline statistics. Content depth distributions. WordPress goes from a content management system to a content intelligence system — and nobody else is building this tier.

on your data · in your site · without sending it anywhere

Abilities for AI / 04 — In practice

What it looks like in practice.

Three short scenes from the alpha, in the operator's words. Each one is a real sequence of abilities the AI ran — not a screenshot, not a marketing rendering. The actual shape of the day.

Scene 01

A site you haven't seen before

Cold session. New AI, no prior context. You hand it the URL. It compiles a state report in 29 calls and under two minutes. Site health, security posture, taxonomy integrity, theme audit, content depth, voice signature. The AI now understands the site well enough to recommend — and explain.

Scene 02

A campaign retro

"Pull the contacts who replied to last month's campaign, segment them by behaviour, draft tomorrow's follow-up matched to each segment." The AI runs the segments, reads the prior thread, drafts the messages. Sends nothing. Waits for you to approve. The campaign retro stops being a Saturday job.

Scene 03

"Why is my site slow?"

A question the dashboard never quite answers. The AI runs the diagnostics ability, reads the cron queue, checks the recent revisions, finds a plugin update that landed yesterday and a job that's been retrying for six hours. Names the cause. Suggests the fix. Waits for you.

Abilities for AI / 05 — How it relates

The engine is one of three. All three are needed.

Abilities for AI registers what's possible. The Adapter exposes it through the gate. Abilities MCP routes the conversation. Together: a WordPress site that can be operated by talking to it.

← Layer 01

Abilities MCP

The bridge that runs on your machine and routes the call to the right site.

← Layer 02

MCP Adapter

The gate on each site that authenticates, validates, redacts, and returns.

This page

Abilities for AI

Every WordPress surface registered as a callable named operation behind the gate.