create-style
Skill726 starsChanged 3 months agoMITView on GitHub
Create an OpenStory library style from reference images, video, URLs, or a written look. Scans the inputs, drafts a v2 config, POSTs create-style. Use when asked to create, extract, capture, or craft a style or look from refs; to turn footage or a brand into an OpenStory style; or when the user runs /create-style. Not for generating a video (that's create-sequence).
- 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-sequenceSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
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 90
If ffmpeg is missing, say so and continue with stills + text you do have.
- Distinctive: line 102
Write the recipe from the pixels:
- Distinctive: line 112
If list-styles already has that slug, pick another.
≈ “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 style
Mint a team-owned OpenStory library style from whatever the user handed
you. 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.
This skill uses _links.create-style and _links.list-styles.
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"? } }.
Gather
Collect every ref before drafting. Accept mixed input:
| Input | Scan |
| Image (file or URL) | Read it with vision. |
| Video (file or URL) | Download if needed. Pull 3–5 stills across the clip with ffmpeg, then Read each still. Also note camera move, cut pace, and energy from the timeline. |
| Web page | Fetch or screenshot; treat visible art direction as refs. |
| Text / brand notes | Hard constraints. They win when they conflict with a ref. |
Video stills (need ffmpeg + ffprobe):
mkdir -p /tmp/create-style
dur=$(ffprobe -v error -show_entries format=duration -of default=nk=1:nw=1 "$VIDEO")
for p in 15 40 65 90; do
t=$(awk -v d="$dur" -v p="$p" 'BEGIN { printf "%.2f", d*p/100 }')
ffmpeg -y -ss "$t" -i "$VIDEO" -frames:v 1 -q:v 2 "/tmp/create-style/f$p.jpg"
doneIf ffmpeg is missing, say so and continue with stills + text you do have.
Skip a ref only when it is unreadable; list what you skipped.
Done when every provided ref is observed or explicitly skipped.
Draft
GET list-styles (for slug clashes and as a specificity bar). Re-read
the live create-style schema; fill every required field it names. Omit
optional fields you cannot support. Never send server-managed fields
(isTemplate, ids, usage counts).
Write the recipe from the pixels:
- Palette — hexes sampled from the refs, 3–8 colors. No stock teal-and-orange cinematic set unless that is actually on screen.
- Lighting / grading / mood / artStyle — sources, direction, medium you can see (e.g. "35mm live action, window-side key, crushed teal shadows"). Not "cinematic, high quality".
- Motion —
cameraalways.pace/energywhen video or the user implied movement. - Name — short distinctive title from the look, not the filename. If list-styles already has that slug, pick another.
- references — hosted URLs when the user gave them; otherwise short labels of the files you scanned.
Text-only input is allowed: draft the same complete config from the description.
Done when the body satisfies the live required set.
Create
POST the create-style href. Use that link's examples for shape, not
memory.
201— take the document and stop retrying.409— rename once and POST again.4xxwithdetails— fix the named fields and POST again.
There is no update/delete on v1. A tweak is a new style.
Report
Return name, id, a one-line look summary, and a compose URL:
{origin}/?style=<slug>&prefill=style#compose
Slug the name: lowercase, spaces to hyphens. Use a slug field on
the created document when the API sends one.
To generate via the API, pass style: "<name>" (the create-sequence
skill). Follow _links.create-sequence on the style document only if
they asked for a video next.
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.

