Skip to content
Skills Library
Marketing & content · Automation

studio

/studio

Operate a self-hosted Studio deployment — write, publish, schedule and edit posts and short-form video, read publication and audience analytics, and diagnose a post that did not reach a platform. Use whenever the request is about publishing, a channel, a draft, a scheduled post, delivery to Telegram/X/Threads/Instagram/YouTube, or why something did not go out.

Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Operate a self-hosted Studio deployment — write, publish, schedule and edit posts and short-form video, read publication and audience analytics, and diagnose a post that did not reach a platform. Use whenever the request is about publishing, a channel, a draft, a scheduled post, delivery to Telegram/X/Threads/Instagram/YouTube, or why something did not go out.

Original author description

Operate a self-hosted Studio deployment — write, publish, schedule and edit posts and short-form video, read publication and audience analytics, and diagnose a post that did not reach a platform. Use whenever the request is about publishing, a channel, a draft, a scheduled post, delivery to Telegram/X/Threads/Instagram/YouTube, or why something did not go out.

How it works

  1. Publish or prepare
  2. Reaching an audience
  3. Diagnosing
  4. Analytics
  5. Language
Original SKILL.md headings · 72 lines, 615 words
SKILL.md preview
---
name: studio
description: Operate a self-hosted Studio deployment — write, publish, schedule and edit posts and short-form video, read publication and audience analytics, and diagnose a post that did not reach a platform. Use whenever the request is about publishing, a channel, a draft, a scheduled post, delivery to Telegram/X/Threads/Instagram/YouTube, or why something did not go out.
---

# Studio

The `studio` MCP server is the whole interface to one deployment. There is no repository, database
or SSH here: if a task cannot be done with a tool, it cannot be done. Never ask for the server, the
container or the token.

Deployments differ — some publish a website and two languages, some are video only. Call
`studio_capabilities` before choosing a command, and read `tools/list` for the actual surface. Those
describe the deployment you are connected to; this file does not.

## Publish or prepare

Take the wording literally, and when it is ambiguous, prepare.

- "Post it", "publish now", "send it" — publish: create, `studio_post_validate`, then
  `studio_post_publish`. Video: `studio_video_preflight`, then `studio_video_publish`.
- "Let's prepare a post", "draft this", "get it ready" — create and stop at the draft. Report
  `studio_post_preview` and wait. The draft is already visible for approval in the deployment's own
  Telegram bot and Command Center. Do not publish it later without being told to.
- A time — "tomorrow at nine" — is `studio_post_schedule` or `studio_video_schedule`, not publish.

Media is attached to a draft, not passed to publish: `studio_post_attach_media` after the file is
uploaded to the deployment. A post with media publishes only once the media is attached.

## Reaching an audience

`studio_post_publish`, `studio_video_publish`, `ops_retry`, `ops_edit`, `ops_delete` and
`ops_use_other_media` change what other people see. Run them only when asked for that specific
thing, once, and report what actually happened rather than what was intended. Publishing twice
because a call looked like it failed is worse than reporting the uncertainty.

## Diagnosing

Start with `ops_status` — the guide is a CLI command, not a tool an agent can call — then:

- `ops_audit` — failed jobs, stuck targets and inconsistencies across the text and video pipelines.
- `ops_recent` — the last posts, their targets, and the targets each one is missing. This is the
  whole diagnosis for "post X did not go to Y".
- `ops_verify` — fetches a published target and reports whether it is really live.
- `ops_find` with a fragment of the text resolves an older post's ref. Refs are `post:N`.

Read the tool output before reasoning about causes, and never retry a target blindly: `ops_recent`
first, then one `ops_retry` for the target actually missing.

## Analytics

`studio_analytics_dashboard` is the overview; `studio_analytics_post_metrics`,
`studio_analytics_video_metrics` and `studio_analytics_audience` are the detail. Audience numbers
come from live platform APIs and can legitimately be absent — that is not a bug to chase. Metrics
are sampled over time, so a post published minutes ago having no numbers is expected.

For a question about how videos are doing rather than one video, `ops_brief` answers the whole week
in one call and names the command behind each of its sections; `ops_video_report` is that detail,
and `ops_video_metrics` one video. Two habits make the difference between a report and advice worth
acting on:

- Read the `reading` block. Every report carries one and it says what its numbers do not mean.
- Say the sample size, and refuse to recommend on `confidence: anecdotal` or `low`. A slot flagged
  `dominatedBySingleVideo` rests on one lucky video.

`openings` in `ops_video_report` is the one block about a choice rather than an outcome: what was on
screen two seconds in, and what kind of line the video opened with, against retention at three
seconds. The kind is a model's judgement about ten words — show the line beside the label when a
finding rests on it. [Telling an agent how to read the numbers](../../../docs/analytics-agent.md)
is the long form.

## Language

Post text, captions and titles are written in the language of the channel they publish to.
Everything written to the operator — reports, questions, summaries — is in the operator's language.

Versions

RepositoryScoreLicence
This page · alexgetmancom/solo-publisher90Apache-2.0
teemukinos/creator-studio-mcp100MIT
afrotools/afrotools100Apache-2.0
remotion-dev/remotion100MIT
gilrotem/web-studio100MIT
lucasbonutti/motion100MIT
AlpacaLabsLLC/skills-for-architects100MIT
remocn/remocn100MIT
per-simmons/claude-game-studio100MIT

Database snapshot: 13.11.2026 · package version 8568ecbb883b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90quegly
    Schedule, publish and measure social media posts on Quegly through its MCP tools: Instagram, TikTok, YouTube, Facebook, X, Threads, LinkedIn, Bluesky, Pinterest and Telegram, from one post to every channel, with photos, videos, carousels, stories, Pins, video covers and…
  • 100threads-post
    Post to Threads and schedule Threads posts from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own Threads account via the 1Social MCP server (OAuth, no API key), checks the Threads 500-character limit and image rules first, schedules up to 30 days ahead and…
  • 100schedule-posts
    Schedule and publish social media posts through PostFast, with the user's approval before anything goes out. Use when someone wants to post or schedule something on X, Instagram, Facebook, TikTok, LinkedIn, YouTube, Threads, Pinterest, Bluesky, Telegram or Google Business…
  • 90vidiq-publishing
    Prepare and adapt supplied content for YouTube, Instagram, TikTok, X, and Facebook Pages; save drafts, publish or schedule approved versions, and track each destination. Use when asked 'post this everywhere', 'publish a Reel', 'upload to YouTube', 'tweet this', 'schedule these…
  • 100sendcove
    Draft, schedule and publish social media posts, upload media, check engagement and best times to post, and answer inbox comments with the Sendcove MCP server (X, Instagram, TikTok, Threads, Bluesky, YouTube, Facebook Pages, LinkedIn). Use when the user asks to write, schedule,…
  • 100reelspan
    Publish, schedule and track social media posts with the Reelspan API (TikTok, YouTube, Instagram, Facebook, X, Threads, LinkedIn, Pinterest, Bluesky, Reddit and more). Use when the user wants to post or schedule a video, photos, a carousel, text or a PDF to social networks,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.