CanAI Blocks Skill

Opt-in companion skill to canai-mcp. Attaching this skill is the user's signal that they want a page deployed as native WordPress blocks — editable in Gutenberg — instead of Twig. Without it, pages are Twig; canai-mcp never steers toward blocks on its own. Same server, same API key, same transport as canai-mcp ({site}/wp-json/mcp/wpcanai) — this skill only adds the block-page tools and the page-format concept on top of it.

Install and configure canai-mcp first. It covers MCP client setup, the API key, the "MCP only — no shell, no curl, no file edits" transport rule, and every other CanAI tool (templates, Twig pages and layouts, blog posts via wpcanai-write-post, settings, media sideload, i18n, Tailwind builds). This skill assumes all of that already applies and does not repeat it. The one documented exception to "MCP only" — binary media uploads via the sideload REST route — is canai-mcp's; this skill only tells you to sideload an image before referencing it by attachment id (see Images below).

Blog posts are not this skill. A blog post is block content by nature — there is no Twig alternative — so wpcanai-write-post lives in canai-mcp and needs no opt-in. This skill is only about pages, where blocks are a choice against Twig.