create-sequence
Skill726 starsChanged 3 months agoMITView on GitHub
Create a multi-scene AI video sequence via OpenStory's public HTTP API — turn a script or brief into a sequence, enhance a script, poll generation, and export a stitched MP4. Use when asked to make, generate, or produce a video or sequence from a script or idea; to enhance or expand an OpenStory script; to check generation status; to export/download an MP4; or when the user runs /create-sequence. Not for creating a library style (that's create-style) and not for editing the OpenStory codebase.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- openstory-so/skillsword for word, first seen Oct 7, 2026
Other versions1 project uses a version of this.
Word for word · 1
- openstory-so/skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/bun-test.mdcCursor rule
- .cursor/rules/context7-integration.mdcCursor rule
- .cursor/rules/drizzle-patterns.mdcCursor rule
- .cursor/rules/production-review-panel.mdcCursor rule
- .cursor/rules/project-context.mdcCursor rule
- .cursor/rules/react-rules.mdcCursor rule
- .cursor/rules/tanstack-react-router_api.mdcCursor rule
- .cursor/rules/tanstack-react-router_guide.mdcCursor rule
- .cursor/rules/tanstack-react-router_installation.mdcCursor rule
- .cursor/rules/tanstack-react-router_routing.mdcCursor rule
- .cursor/rules/tanstack-react-router_setup-and-architecture.mdcCursor rule
- .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdcCursor rule
- sd25-peSkill
- react-patternsSkill
- update-model-versionsSkill
- create-styleSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
If the root _links has device-authorize, POST it (empty JSON body).
- Very specific: line 55
Write the key to ~/.config/openstory/credentials (mode 600) and continue.
- Very specific: line 57
If there is no device-authorize link, stop.
- Very specific: line 116
When the user wants a script, not a video: POST _links.enhance-script.
- Very specific: line 123
Stop after done unless they then want a sequence — follow that response's create-sequence example (enhance: "off").
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Create sequence
Public API at https://openstory.so. Override the origin only when the user
gives a self-hosted base URL.
MCP first
The OpenStory plugin (ChatGPT, Codex, Claude, Grok, and Gemini CLI) connects https://openstory.so/mcp. When this session
has OpenStory MCP tools, call those. They authenticate with the client's
OAuth grant (or a Bearer osk_ key the client already attached). Use the
HTTP API below only when those tools are absent, or the user gave a
self-hosted origin. Do not start a device-code login while MCP tools are
available.
Discover first
GET {origin}/api/v1 (unauthenticated). The body is the contract:
instructions, requestSchema, and _links. Follow _links (each has
method; writes also have contentType and examples). Do not hardcode
paths or paste the schema into later calls from memory — if a field is
unclear, re-read requestSchema or GET {origin}/api/v1/openapi.json.
Auth
Required on every call except the root and the device-login pair. Resolve a key in this order:
OPENSTORY_API_KEYin the environment.~/.config/openstory/credentials— a lineOPENSTORY_API_KEY=<key>.~/.openstory/credentials.json, written by the OpenStory CLI (npx @openstory/cli@latest login):keys["<origin>"], e.g.keys["https://openstory.so"].- If the root
_linkshasdevice-authorize,POSTit (empty JSON body). Reply in the chat withuser_codeandverification_urlas copyable plain text, plus theverification_url_completelink. Opening a browser is extra, never a substitute. Never printdevice_code. Stop this turn. Done when the reply contains the code as visible text. - On the next turn,
GET_links.pollwith?wait=60suntil it returnsapi_key(authorization_pendingmeans keep polling;expired_tokenoraccess_deniedmeans stop and tell the user). Write the key to~/.config/openstory/credentials(mode 600) and continue. - If there is no
device-authorizelink, stop. Tell the user to create a key under Settings → Developer at the origin and exportOPENSTORY_API_KEY. Do not open the dashboard unless they ask.
Send Authorization: Bearer <key> (or x-api-key). A 401 means the
key is bad or revoked — go back to step 4 (or 6) rather than retrying.
Keys are team-scoped. 429 includes Retry-After — honor it. Errors are
always { "error": { "code", "message", "details"? } }.
Create a video
API defaults are stills (motion/music false). Unless the user says
otherwise, send motion: true, music: true, enhance: "auto". Set
targetSeconds from the brief; omit it if they did not imply a length.
music: true requires motion: true.
Pass style, cast, and locations as names or inline { name, ... }
objects. Never invent ids. Omit style to let the API pick. Mint a new
library style from refs with create-style. Do not send person
referenceImageUrls unless the user provided images and the live
schema's portrait-attestation fields.
POST the _links.create-sequence href with a JSON body. Expect 202.
Take sequences[0]; follow its _links.poll (or statusUrl).
Poll generation
Sequence status long-polls. Append ?wait=60s (also 30, 2m,
1500ms; cap 90s). A malformed wait is 400 — do not invent other
syntax.
Repeat GET on the poll link until X-Wait-Done: true. Then:
failed/archived→ report and stop.completed→ readcounts.videosFailed > 0means the run finished with broken shots; say so. Do not call it a full success.
Status is database-backed; reconnecting and polling again is correct.
Export MP4
Export only when counts.videosReady === counts.shots and
videosFailed === 0. Otherwise the export POST rejects a partial cut.
POST_links.create-export(empty JSON object is valid).GET_links.exportsuntil an entry isready(use itsurl) orfailed(surfaceerror). Export list does not long-poll.- Return the HTTPS URL. Download to disk only if the user asked for a local file.
For every still, line, and clip on disk (not just the MP4), with a
shell: npx @openstory/cli@latest pull <sequenceId> --dir <dir>. It
signs in on first use and skips files already there. --exports adds
rendered MP4s.
Enhance only
When the user wants a script, not a video: POST _links.enhance-script.
The response is SSE:
- unnamed
data:frames →{ "delta": "..." } event: done→{ "enhancedScript", "_links" }event: error→ fail
Stop after done unless they then want a sequence — follow that
response's create-sequence example (enhance: "off").
List
GET _links.list-sequences for this key's sequences. Page with the
next link; its absence is the end.
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
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.

