wordpress-blog

Files (1)

• SKILL.md

SKILL.md (first lines)

# WordPress Blog

Create one publication-quality article from idea to verified WordPress publication.

This is an editorial operating procedure, not a generic content-generation call.

The skill owns:

**strategy → research → article → SEO package → visual concept → hero-image QA → WordPress delivery → verification**

Bolta is the execution and state layer. The AI client remains responsible for editorial judgment.

## Core principles

1. **Write for the searcher first.**
   The article must answer a real problem or query before introducing the product.

2. **Use Bolta's current brand context.**
   Never assume the voice, positioning, audience, or product capabilities from memory.

3. **ChatGPT writes the article.**
   Do not ask Bolta's generic content generator to create the long-form article.

4. **The image is part of the editorial work.**
   A new file is not enough. The visual concept must be meaningfully different from recent hero imagery.

5. **Publishing is not complete until verified.**
   Drafted, approved, queued, or uploaded is not the same as Published.

6. **Do not destroy good work because one delivery step fails.**
   Preserve the finished article, SEO package, and approved image so the failed step can be retried.

---

# When to use

Use this skill when the user wants:

- a new SEO article for the connected WordPress site;
- a long-form Bolta blog article;
- a publication-ready article rather than an outline;
- an article researched and written in the workspace's brand voice;
- a hero image generated specifically for the article;
- direct WordPress publication through Bolta;
- a repeatable weekly blog operation.

Do not use this skill for:

- a social-media post → use `social-publishing`;
- replying to conversations → use `reddit-engagement`, `cross-platform-engagement`, or `social-inbox`;
- a performance recap → use `analytics-review`.

---

# Tools this skill uses

| Tool | Why |
|-|-|
| `list-workspaces` | Resolve the workspace when the connector does not already scope it. |
| `list-accounts` | Confirm a connected WordPress account and avoid guessing among multiple accounts. |
| `get-voice-context` | Load the resolved Voice Profile + Business DNA context before editorial work. |
| `list-business-dna` | Find the current/default DNA entry when deeper visual brand fields are needed. |
| `get-business-dna` | Pull visual identity, aesthetics, logo guidance, and positioning for image art direction. |
| `list-workspace-posts` | Inspect recent WordPress articles and their media before choosing a topic/image concept. |
| `create-wordpress-blog-post` | Create the article, SEO fields, WordPress media, and requested publication action in one canonical delivery path. |
| `get-post` | Verify the complete Bolta post state after delivery/publication. |
| `get-post-platform-details` | Inspect WordPress-specific fields when troubleshooting or verifying metadata. |
| `update-post-platform-details` | Correct WordPress metadata on an existing post if needed. |
| `update-post` | Repair article/media state in place rather than deleting and recreating the post. |
| `submit-for-review` | Use when the workspace/user requires review instead of direct publication. |
| `approve-post` | Approve the exact reviewed revision when the approval path is active. |
| `publish-post` | Publish an already-created Bolta post when direct WordPress creation did not perform the final publish step. |
| `list-routine-templates` | Discover the recurring blog template. |
| `create-routine` | Save this behavior as a repeatable background operation. |
| `activate-routine` | Arm the saved blog routine. |
| `run-routine-now` | Prove the saved routine dispatches through the same runtime. |
| `list-routine-runs` | Inspect execution history of the routine. |

Image generation is performed by the host AI client's image-generation capability, not by inventing an MCP tool.

Web/search research may be used when current external information materially improves the article. Do not fabricate sources, statistics, market claims, or customer examples.

---

# Prerequisites

Before writing:

- Resolve the Bolta workspace.
- Confirm a healthy connected WordPress account.
- Load `get-voice-context`.
- If deeper Business DNA fields are needed, use the DNA id from the resolved context or `list-business-dna`, then `get-business-dna`.
- Inspect recent WordPress posts with `list-workspace-posts`.
- If there are multiple WordPress accounts, ask the user which account to use rather than guessing.
- Never ask the user for raw WordPress credentials; Bolta owns the connection.

If no WordPress account is connected, use the appropriate Bolta connection flow and stop before writing/publishing unless the user explicitly only wants the article draft.

---

# Workflow

## 1. Understand the brand

Call `get-voice-context`.

Capture:

- what the business actually does;
- who it serves;
- positioning;
- tone;
- dos;
- don'ts;
- banned patterns;
- persona/speaker mode;
- platform adaptations;
- what information is missing.

From boltaai/bolta-skills, MIT.

More from boltaai/bolta-skills