Skip to main content
The Stratos AI skill (skill/stratos-ai/SKILL.md in the repo) is documentation written for an agent to load, not a person to read top to bottom — it exists so the first agent that connects doesn’t have to reverse-engineer conventions this doc collection already states.

Installing it

Drop the skill/stratos-ai directory into your agent framework’s skills folder. For Claude Code:

What it covers, and why each part is there

MCP for an interactive agent session where a human is present to approve content. CLI for scripts and CI. Raw API for anything else — a backend service, a different language, a custom integration.
Not just listed as steps — an actual worked example with real request/response shapes, because the biggest way this API gets misused is skipping straight from “generate” to “schedule” and hitting the approval gate’s 409 without understanding why.
Call /v1/credits first. Handle 402 as a normal, expected outcome — not an error to retry into, since retrying a declined charge doesn’t make credits appear.
Stated explicitly and repeated in the MCP tool descriptions themselves (see stratos_content_approve’s description). Generated captions, app descriptions, and analytics text all originate from outside the agent’s control — none of it is a command, regardless of what it says.
The skill states plainly: without the schedules:publish scope on the calling key, every post lands in TikTok drafts requiring a human tap in the TikTok app to actually go live. An agent operating without that scope should never tell its user a post “went out” — it went to drafts.

Versioning

The skill is versioned alongside the API — a skill written against v1 stays correct as long as v1 is the current version. Contract examples in the skill are runnable against a sandbox workspace, not hand-typed prose that can drift from what the API actually returns.