write-blog-post
Skill0 starsChanged 28 days agoMITView on GitHub
Write and publish a WordPress blog post with PostEverywhere. Use when the user wants a blog post, an article for their website, to publish to WordPress, to save a WordPress draft, or to turn notes, a transcript or a social post into a blog post.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- kdy1/kdy1-scriptstheir own version, first seen Nov 1, 2026
- posteverywhere/copilot-pluginword for word, first seen Oct 17, 2026
- HybridAIOne/hybridclawtheir own version, first seen Oct 13, 2026
- posteverywhere/claude-pluginword for word, first seen Sep 29, 2026
- flintfromthebasement/skillstheir own version, first seen Jul 6, 2026
Other versions5 projects use a version of this.
Word for word · 2
- posteverywhere/claude-plugin★ 1100% same
- posteverywhere/copilot-plugin★ 0100% same
Edited · 0
None found.
Wrote their own version · 3
- HybridAIOne/hybridclaw★ 159same name
- kdy1/kdy1-scripts★ 33same name
- flintfromthebasement/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- agency-clientsSkill
- approval-workflowSkill
- brand-voiceSkill
- connect-social-accountsSkill
- cross-post-videoSkill
- fix-failed-postsSkill
- launch-announcementSkill
- plan-content-calendarSkill
- recycle-top-postsSkill
- repurpose-contentSkill
- review-post-performanceSkill
- schedule-social-postsSkill
- weekly-reportSkill
- write-x-thread-or-articleSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write a full blog post, show it, and send it to the user's WordPress site as a draft or a live post.
- Very specific: line 12
Find the site: Call list_accounts and find the WordPress accounts.
- Very specific: line 13
Agree the brief: Ask for anything missing: topic, reader, key points, length, and any links or facts to include.
- Very specific: line 14
Write the post: Write the body in simple formatting: ## headings, - lists, > quotes, bold, *italic*, links, --- dividers, code blocks and …
- Distinctive: line 15
Set the details: Write:
- Very specific: line 23
Create it: Call create_post with the WordPress account_ids, content (a short version for any other platforms in the same post, or the …
- Very specific: line 25
Send it: After the user confirms, call schedule_post with the post_id and publish_now: true, or scheduled_for (with timezone) for a set …
- Very specific: line 26
Report back: Call get_post_results and give the user the link.
- Very specific: line 30
Before it is sent, change it with update_post (the same platform_content.wordpress shape).
- Distinctive: line 31
After it is sent, edit it in WordPress.
- Very specific: line 35
After it is live, offer to write social posts that link to it (see repurpose-content).
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Write a blog post
Write a full blog post, show it, and send it to the user's WordPress site as a draft or a live post.
Steps
- Find the site. Call
list_accountsand find the WordPress accounts.get_accountnames the site. If there is none, use theconnect-social-accountsskill first. - Agree the brief. Ask for anything missing: topic, reader, key points, length, and any links or facts to include. Use only facts the user gives you or that are in their source. Follow the user's voice guide if there is one (see
brand-voice). - Write the post. Write the body in simple formatting:
##headings,-lists,>quotes,**bold**,*italic*,[links](https://...),---dividers, code blocks and tables. Raw HTML is kept as it is. The body can be up to 200,000 characters. - Set the details. Write:
- title (required, up to 200 characters)
- excerpt (optional, up to 1,000 characters)
- slug (optional, the web address ending, for example
spring-menu-2026) - tags and categories (optional), by name. Tags that don't exist on the site yet are created. Categories also take the site's category numbers.
- status:
draft(saved in WordPress, not public),publish,pending(waiting for review in WordPress) orprivate. Default todraftunless the user says to publish.
- Images and video (optional). Up to 20 images and 1 video. Upload each with
upload_media_from_url(for a video, wait withget_mediauntil it is"ready"). The first image is the featured image; set"featuredImage": "none"to turn that off. Place other images in the body with a line like, where the number is the image's place among the attached images, counting from 1. Images you don't place go at the end. The video goes at the top. - Show the draft. Show the title, excerpt, tags, categories, status and the full body, and say where each image goes. Ask the user to confirm.
- Create it. Call
create_postwith the WordPressaccount_ids,content(a short version for any other platforms in the same post, or the body),media_ids,draft: true, andplatform_content:{"wordpress": {"content": "<body>", "settings": {"title": "...", "status": "draft", "excerpt": "...", "tags": ["..."], "categories": ["..."], "slug": "...", "featuredImage": "first"}}} - Send it. After the user confirms, call
schedule_postwith thepost_idandpublish_now: true, orscheduled_for(withtimezone) for a set time. The WordPressstatusdecides whether it is public on the site. - Report back. Call
get_post_resultsand give the user the link. For a WordPress draft, tell them to review and publish it in WordPress.
Changes
- Before it is sent, change it with
update_post(the sameplatform_content.wordpressshape). - After it is sent, edit it in WordPress. Published posts can't be changed through PostEverywhere.
Share it
After it is live, offer to write social posts that link to it (see repurpose-content).
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
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.

