wp-rest-api

Transmit assets that already exist — block markup, CSS, and animation JS — to a WordPress site over /wp-json/, using curl and an admin Application Password. This is the last mile that used to be a copy-paste into the Code Editor. The markup is generated elsewhere; this skill transmits bytes unchanged and tells you the truth about what the site did with them.

Everything needs curl and jq (1.6+), plus grep and diff for the verification steps. Nothing else — no MCP server, no CLI, no SSH, no database access.

Reference	Read it when
`reference/endpoints.md`	before any request — exact paths, payload shapes, copy-pasteable curl
`reference/safety-rules.md`	once per session, before the first write. The rules that are not negotiable
`reference/gutenberg-traps.md`	before pushing markup, and whenever the editor looks wrong while the frontend looks right
`reference/code-snippets.md`	only when shipping PHP or JS — the snippet route, end to end
`reference/animation.md`	only when the page carries GSAP or any other JS animation
`reference/troubleshooting.md`	a 500, a non-JSON body, a socket error, or a plugin that will not activate
`reference/integrations.md`	the user mentions a markup validator or a credential-masking plugin, or you are running one