agentleFS
chellehonikerchellehoniker/claude-code-storytelleros/skills/blog-post-and-newsletter/SKILL.md

blog-post-and-newsletter

Skill1 starsChanged 16 days agoMITView on GitHub

Use when the user wants to publish a blog post AND turn it into a newsletter in one step. The flagship WordPress + Email Studio flow. Triggers on "write and send a blog post about X", "blog this and email the list", "draft a post and a newsletter on X", "publish to WP and send to my readers".

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If this 404s, route to wordpress-connect.

    line 34
  2. Distinctive:

    Use Media Studio on the StorytellerOS connector (it uses the image provider the user has configured).

    line 48
  3. Distinctive:

    Before running silently, confirm:

    line 118
  4. Distinctive:

    Do not send the newsletter automatically.

    line 131
  5. Distinctive:

    Do not skip the upload step.

    line 132
  6. Very specific:

    Do not auto-create new categories.

    line 133
  7. Distinctive:

    Do not stuff the newsletter body with the entire post.

    line 134

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blog post → newsletter (flagship composite flow)

This is the highest-leverage WordPress + Email Studio combo. The user gives you a topic; you draft once, publish to WordPress with a featured image, then queue the newsletter pointing at the published URL — without copy-pasting between tools.

The pipeline

1. Discovery       → confirm site is connected         (stos_wp_site)
2. Draft post      → write title + body                (in-conversation)
3. Featured image  → generate in Media Studio          (stos_media_generate, then
                                                        stos_media_generation_status)
4. Upload image    → push to WP media library          (stos_wp_media_create)
5. Publish post    → save + publish on WP              (stos_wp_posts_create)
6. Compose email   → newsletter using the same body    (stos_email_campaigns_create)
7. Confirm         → show user the WP URL + draft id

Skip steps the user explicitly opts out of (e.g. "no image" → skip 3-4). The post saves as a draft unless the user says to publish; then set status publish in step 5.

Step-by-step

1. Confirm the connection

const site = await stos_wp_site();
// site.siteName, site.pluginVersion, site.hasWooCommerce, etc.

If this 404s, route to wordpress-connect.

2. Draft the post

Compose the title and HTML body in conversation. Aim for the user's voice — pull pen-name guidance via stos_pen_names_list if the user has a primary pen name with a brand voice doc.

Default structure:

  • 1-line lede
  • 2-3 paragraph development
  • 1-paragraph practical takeaway / call to action
  • HTML, not Markdown

3. Generate featured image

Use Media Studio on the StorytellerOS connector (it uses the image provider the user has configured). Aim 16:9, evocative-not-literal.

sizes must name at least one platform size. Valid keys: instagram_feed, instagram_story, tiktok, facebook_feed, linkedin, twitter, pinterest, youtube_thumb, bluesky, threads, googlebusiness, reddit, telegram, snapchat, whatsapp, discord. The 16:9 ones (twitter, youtube_thumb, bluesky, reddit, discord) suit a blog header; an unknown key is refused with "Unknown size key".

await stos_media_generate({
  taskType: "image",
  prompt: "Watercolor sketch of a writer at dawn, soft pastel palette",
  sizes: ["twitter"],  // required for images; "twitter" is 1200×675 (16:9), a good blog header
});
// poll until the job completes; the finished image then appears in the media library
const jobs = await stos_media_generation_status({});
const assets = await stos_media_assets_list({ source: "generated", kind: "image" });
const imageUrl = /* the new asset's public url */;

4. Upload to WP media library

const media = await stos_wp_media_create({
  fields: {
    url: imageUrl,
    alt: "Watercolor sketch of a writer at dawn",
    title: "Featured image: " + postTitle,
  }
});

5. Publish the post

const post = await stos_wp_posts_create({
  fields: {
    title: postTitle,
    content: postHtml,
    excerpt: postExcerpt,
    status: "draft",           // publish only after the user says so
    featured_media: media.id,
    tags: postTags,            // string[]
    categories: postCategoryIds, // number[] — list via stos_wp_categories_list first
  }
});
const wpUrl = post.link; // user-facing URL

6. Draft the newsletter

stos_email_campaigns_create({
  fields: {
    campaign_name: postTitle,   // required
    pen_name_id: penNameId,     // required to send; the sender comes from the pen name
    subject_line: postTitle,
    preheader: postExcerpt,
    email_body_html: `${teaserHtml /* the lede + a paragraph, not the whole post */}<p><a href="${wpUrl}">Read the full post on the blog →</a></p>`,
    list_ids: defaultListIds,   // ask user OR pull "Main list" via stos_email_lists_list
  }
});

The campaign starts as a draft. Confirm with the user before sending — never auto-send.

7. Confirm

Reply with:

  • The published post URL
  • The newsletter's name + a "Send when ready in Email Studio → Campaigns" line

Decision points to surface

Before running silently, confirm:

DecisionDefault if user doesn't say
Publish or draft?Draft. Ask before publishing.
CategoriesSkip if user doesn't mention. Don't auto-assign.
TagsUp to 5 you infer from content. Confirm.
Image styleWatercolor / soft / brand-matching when no preference.
Newsletter list"Main list" if exactly one obvious match; otherwise ask.
Send newsletter or save as draft?Always draft. The user sends from Email Studio.

Anti-patterns

  • Do not send the newsletter automatically. The user reviews and sends.
  • Do not skip the upload step. Linking directly to a StorytellerOS-hosted image can break when its link expires; the copy in the WordPress media library is the one to use.
  • Do not auto-create new categories. If the user mentions one that doesn't exist, ask before creating with stos_wp_categories_create.
  • Do not stuff the newsletter body with the entire post. A teaser + "read more →" link converts better and respects the WP site as the canonical home.

Composes well with

  • wordpress-connect — when the connection is missing
  • wordpress-media — featured image work in detail
  • marketing-studio — list / send the campaign once it's drafted

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.