LinkedIn queue skill

Run the LinkedIn queue in CMO.so: review and approve drafts, turn articles into posts, plan days, campaigns, pause and resume.

It's one of cmo.so's open CMO.so core skills: a SKILL.md file that tells an AI agent when to use it, what to ask you first, the steps to follow, the checks to pass and what to hand back, so the job is done the same careful way every time.

Reach for it when you'd otherwise say something like “Show my LinkedIn queue”, “Approve drafts 812 and 813 and move 815 up”, “Post about my latest blog article on LinkedIn”. Your agent reads the skill's description and picks it for requests like these, so you don't need to name it.

If a request is close but not quite right, the skill says so and points to the related skill that fits better, instead of forcing a poor answer.

It works best with the website (`workspace`) the LinkedIn account is linked to; which drafts to approve, edit or skip; for campaigns: name, brief, objective, link to send readers to, start day and posts per day; and the user's timezone, for planning days.

You don't have to prepare everything up front. The skill asks for missing pieces one at a time and says plainly when it's working from an assumption instead of your data.

You get a reviewed LinkedIn queue in CMO.so; new posts written from articles, ideas or a campaign, waiting for approval; and a started, paused or resumed campaign or posting schedule.

Every result comes from a written method with a quality bar, so numbers name their source, claims are checked and the output is ready to use or share rather than a rough draft.

Yes. The skill is open source under the MIT licence, so you can use it, change it and share it, including for client work.

Seeing, copying and downloading the whole file on cmo.so needs a free sign-in. Copying also upvotes and saves it, so you can find it again under Saved on the skills page.

Claude Code installs it from the cmo.so marketplace. Any agent that reads SKILL.md folders, such as Codex or Cursor, can use it once the folder is in its skills directory.

As a core skill it also works in Claude, ChatGPT and other MCP clients through the cmo.so MCP server, so you can use whichever assistant you already have.

In Claude Code, run /plugin marketplace add AI-Marketing-OS-LTD/cmo-so-skills, then /plugin install cmo-so@cmo-so. That installs this skill together with the rest of the CMO.so core group.

For other agents, sign in, press Copy or Download above and put the file in your agent's skills folder as SKILL.md inside a folder named after the skill.

Yes. LinkedIn queue is a core skill: it works through the cmo.so MCP server with tools such as social_list, social_setup_get, linkedin_connect_link, social_approve, so it acts on your own website, drafts and channels.

The free plan is enough to start, and every change it makes is shown to you as a preview first and only goes ahead after you say yes.

It pairs well with LinkedIn post writing; Facebook Page queue; Social media strategy; and Social crisis response. The agent can hand over from one to the next in the same conversation, for example research first, then the plan, then the writing.

Each of them has its own page with what it needs and what it returns, linked below.

Yes. It's a plain Markdown file, so you can edit the steps, add your own checks and examples, and keep your version in your own repo. The MIT licence allows it.

If your change would help others too, suggest it on the skills page or open a pull request on GitHub, and it may be folded into the library for everyone.

It's written by cmo.so and adapts open work by others, credited on this page: gokulsvision/Crewm8-Social-Media-Manager-Skill-Graph (MIT); stickerdaniel/linkedin-mcp-server (Apache-2.0); and gitroomhq/postiz-app (AGPL-3.0).

Only permissively licensed work is adapted; copyleft repos are used for ideas only and repos without a licence aren't used at all.

No. The skill only guides your own agent; your files, documents and data stay wherever your agent and its tools keep them.

As a core skill it reads and changes your cmo.so data through the MCP server, with your sign-in, and only after you confirm each change.