agentleFS
Sign inStart free
UXMagicaiUXMagicai/seosorted-skills/skills/publish-to-cms/SKILL.md

publish-to-cms

Skill0 starsChanged 40 days agoMITView on GitHub

Publish or republish SEOsorted articles to the connected CMS (WordPress, Webflow, Shopify, Strapi or a custom webhook). Use when the user asks to publish an article now, push changes live, republish an updated post, or check which publishing integrations are connected.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Run it again with confirm: true.

    line 13
  2. Very specific:

    If a publish failed, get_publishing_calendar operation: "deliveries" with article_id shows the attempt and its error.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Publish to CMS

Steps

  1. get_publishing_calendar operation: "destinations" — connected destinations (WordPress, Webflow, Shopify, Strapi, Ghost, HubSpot, Notion, Headless API, webhook), whether each is ready, and the default. If none is ready, stop and explain how to connect one in Settings → Integrations.
  2. Confirm the article: manage_articles operation: "get". It must be READY (generated) and reviewed.
  3. publish_articles operation: "publish" with article_id, integration_id if not the default, and dryRun: true — say exactly what will happen ("Publish 'X' to WordPress at example.com/blog") and get a yes.
  4. Run it again with confirm: true. Poll check_job_status if a job id comes back, and return the live URL.
  5. For an already-published article that was edited: operation: "republish" (same dry run, then confirm: true). It is refused when nothing changed since the last publish.
  6. If a publish failed, get_publishing_calendar operation: "deliveries" with article_id shows the attempt and its error.

Guardrails

Publishing is public and outward-facing. Never publish without an explicit yes for that article. Do not bulk-publish; schedule instead (content-calendar).

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.

Check your setup, free