Update to WordPress

{
  "description": "Create and edit serialized WordPress block content for posts, pages, patterns, templates, and template parts. Use when a task creates, edits, or transforms content containing WordPress block markup.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 121
    }
  ],
  "name": "edit-wordpress-block-content",
  "skill_md_contents": "---\nname: edit-wordpress-block-content\ndescription: Create and edit serialized WordPress block content for posts, pages, patterns, templates, and template parts. Use when a task creates, edits, or transforms content containing WordPress block markup.\n---\n\n# Edit WordPress Block Content\n\n## Discover Site Context\n\n- When a target site and the WordPress.com MCP server are available, prefer individual tools when available and sufficient. Call `wpcom-blocks-allowed` to discover registered blocks before creating or editing content.\n- When styling content, use `wpcom-theme-presets` and `wpcom-theme-styles` for theme tokens and styles, and `wpcom-global-styles-get` for the site's overrides. Prefer returned theme tokens in supported block attributes over hard-coded values or custom style settings; use custom styles only when theme and block attributes cannot achieve the requested result.\n- If the target site or WordPress.com MCP server is unavailable, limit new content to core blocks and custom blocks already present in the supplied content.\n\n## Requirements\n\n- You must keep content editable in the Block Editor or Site Editor which requires using only registered core blocks or existing plugin blocks.\n- Do not add decorative HTML comments outside block delimiters.\n- Preserve unfamiliar custom blocks, dynamic blocks, references, attributes, classes, and inner markup unless the request explicitly changes them.\n- Keep block attributes and saved markup consistent. Do not invent media IDs, URLs, reusable-block references, or custom block attributes.\n"
}