Install and use the OpenPost skill

The openpost-cli skill gives a terminal-capable assistant instructions for operating OpenPost. It does not install the CLI, provide a connection, or store credentials. Use it when your assistant supports Agent Skills. A working MCP connection does not need this skill.

Install the CLI

Install the npm wrapper:

npm install -g @getopenpost/cli

Sign in and confirm the CLI context:

openpost auth login https://app.openpo.st
openpost auth status --json
openpost workspace list --json

For a self-hosted instance, replace the Hosted origin with your instance URL.

Install the skill

Use the Agent Skills installer for a compatible assistant:

npx skills add https://github.com/getopenpost/openpost --skill openpost-cli

The skill is also published as a deterministic archive at openpo.st/.well-known/agent-skills/openpost-cli.tar.gz for clients that support Agent Skills discovery or archive installation.

Installation controls differ by assistant. Follow the assistant's Agent Skills documentation when it does not support the npx skills command.

Check the setup

Start a new assistant session so it can discover the skill. Ask it to use openpost-cli to inspect the current OpenPost context without making changes.

The assistant should run commands such as:

openpost instance diagnostics --json
openpost auth status --json
openpost workspace list --json

If the openpost command is missing, install the CLI. If authentication is missing, sign in yourself. The skill should not install software or create credentials unless you explicitly ask for that action.

Use the skill

Confirm context

The skill tells the assistant to inspect the active instance, identity, and available workspaces. It uses --json for reads so it can parse IDs and status fields instead of scraping terminal tables.

When the saved context is missing or ambiguous, the assistant should pass an explicit --profile, --instance, or --workspace value. It should use the stored keyring token or environment token without printing it.

Choose a command

The skill distinguishes the main CLI paths:

• openpost post handles short text, text with media, and editable text drafts.
• openpost thread create reads two or more posts separated by --- from a Markdown file.
• openpost publication handles format-first work such as link shares, image posts, carousels, stories, short video, long video, and provider-specific settings.

It also directs the assistant to check provider readiness and capabilities before using a new destination or format.

Authorize changes

The skill treats scheduling, publishing, retries, comment moderation, account disconnection, slot generation, and deletion as changes. The assistant should run them only when your request authorizes that effect.

It should default to an unpublished draft when you did not ask to schedule or publish. It should not add --force after a revision conflict or bypass an interactive confirmation without your authorization.

Check results

After a change, the assistant should read the saved object and current server state. For Post work, that includes the Post, lifecycle events, related job, and each destination Variant.

The skill does not make the assistant infallible. Read the proposed command before a destructive or public action, and inspect the result in OpenPost.

Try a task

Use the openpost-cli skill to create an unpublished LinkedIn link-share post in the Company workspace. Check readiness and capabilities, validate the saved post, and stop before scheduling.

For a thread, provide a Markdown file with two or more posts separated by --- and ask for openpost thread create. To schedule reviewed work, specify the post, workspace, accounts, and exact time, such as 2026-10-02T14:00:00+01:00.

For a failure, ask the assistant to inspect the post, its variants, lifecycle events, and jobs without retrying. Authorize a retry only for the failed destination, then check its new state.