Seedance Sequence
Emily2040/seedance-2.0
This skill should be used when a Seedance 2.0 request is a long story, connected set of clips, multi-generation scene, campaign sequence, dense storyboard, continuation-ready plan, or any idea that…
Structure scenes and control pacing using scene-sequel rhythm.
MITAuto-check passed
Install Scene Sequencing
$ npx skills add jwynia/agent-skills --skill scene-sequencing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jwynia/agent-skills scene-sequencing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/structure/scene-sequencing .claude/skills/scene-sequencing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "scene-sequencing" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/structure/scene-sequencing into .claude/skills/scene-sequencing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-sequencing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/structure/scene-sequencingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jwynia/agent-skills --skill scene-sequencing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jwynia/agent-skills scene-sequencing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/creative/fiction/structure/scene-sequencing .agents/skills/scene-sequencing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scene-sequencing" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/structure/scene-sequencing into .agents/skills/scene-sequencing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-sequencing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill scene-sequencing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jwynia/agent-skills scene-sequencing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/creative/fiction/structure/scene-sequencing .cursor/skills/scene-sequencing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scene-sequencing" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/structure/scene-sequencing into .cursor/skills/scene-sequencing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-sequencing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jwynia/agent-skills.git --path skills/creative/fiction/structure/scene-sequencing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jwynia/agent-skills --skill scene-sequencing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jwynia/agent-skills scene-sequencing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/creative/fiction/structure/scene-sequencing .gemini/skills/scene-sequencing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scene-sequencing" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/structure/scene-sequencing into .gemini/skills/scene-sequencing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-sequencing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jwynia/agent-skills scene-sequencingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jwynia/agent-skills --skill scene-sequencing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/creative/fiction/structure/scene-sequencing .github/skills/scene-sequencing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scene-sequencing" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/structure/scene-sequencing into .github/skills/scene-sequencing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-sequencing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill scene-sequencing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jwynia/agent-skills scene-sequencing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/creative/fiction/structure/scene-sequencing .opencode/skills/scene-sequencing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scene-sequencing" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/structure/scene-sequencing into .opencode/skills/scene-sequencing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-sequencing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
scene-sequencing- GitHub stars
- 166
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,272 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 112
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structure scenes and control pacing using scene-sequel rhythm.
- Works in 5 steps: The Relentless Scene → The Wallowing Sequel → The Arbitrary Disaster → …
- Individual scenes work but dont accumulate
- SKILL.md covers Core Principle, Scene Structure: Goal →…, Sequel Structure: Reaction →… and Pacing Control, plus 8 more sections
- Runs TypeScript scripts from its folder; calls deno
What it does
Scene Sequencing is an agent skill from jwynia/agent-skills. Structure scenes and control pacing using scene-sequel rhythm. Use when individual scenes work but don't accumulate, when pacing feels off (too rushed or too slow), when transitions feel mechanical, or when readers can follow but aren't compelled forward. Based on Dwight Swain's Goal-Conflict-Disaster and Reaction-Dilemma-Decision structure.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/analyze-scene.ts`).
The licence is MIT.
When your agent uses it
- Individual scenes work but dont accumulate
- Pacing feels off (too rushed
- Transitions feel mechanical
- Readers can follow but arent compelled forward
Example prompts
- “t compelled forward. Based on Dwight Swain”
- “/scene-sequencing”
Requirements
- Node.js
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (TypeScript), which the agent can run.
Shell commands in SKILL.md call:
deno
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Scene Sequencing loads about 2.7k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 1,272 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,272 words, ~2,653 tokens.
Download SKILL.mdSave it as
.claude/skills/scene-sequencing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- scene-sequencing
- description
- Structure scenes and control pacing using scene-sequel rhythm. Use when individual scenes work but don't accumulate, when pacing feels off (too rushed or too slow), when transitions feel mechanical, or when readers can follow but aren't compelled forward. Based on Dwight Swain's Goal-Conflict-Disaster and Reaction-Dilemma-Decision structure.
- license
- MIT
- metadata.author
- jwynia
- metadata.version
- 1.0
- metadata.type
- diagnostic
- metadata.mode
- diagnostic+assistive
- metadata.domain
- fiction
Scene Sequencing: Pacing Skill
You help writers structure scenes and control narrative pacing using the scene-sequel rhythm.
Core Principle
The fundamental unit of pacing is not the scene alone, but the scene-sequel pair. Scenes create tension; sequels process it. The alternation creates peaks and valleys that make stories readable.
Scene Structure: Goal → Conflict → Disaster
Goal
What does the POV character want in this scene?
- Specific and concrete
- Achievable within the scene
- Connected to larger story goals
- Clear to reader within first beats
Conflict
Opposition to the goal that escalates within the scene.
- Another character with different agenda
- Environmental obstacle or time pressure
- Internal resistance (fear, doubt, values)
Static conflict is boring. Each beat should make the goal harder.
Disaster
Scene ends with one of these outcomes (in order of narrative power):
- Yes, but... — Goal achieved, new problem created (strongest)
- No, and furthermore... — Goal failed, situation worse
- No — Goal failed, must try again
- Yes — Goal achieved cleanly (use sparingly—kills tension)
Sequel Structure: Reaction → Dilemma → Decision
Reaction
Emotional response to disaster. Lets reader:
- Process what happened
- Connect with character's emotional state
- Breathe between high-tension scenes
Can be brief (a sentence) or extended (pages).
Dilemma
Character faces choice with no good options. Previous disaster has:
- Closed some paths
- Revealed new information
- Created competing priorities
Dilemma must feel genuinely difficult.
Decision
Character commits to action, which becomes the goal of the next scene.
Pacing Control
The ratio of scene to sequel controls tempo:
| More Scene | More Sequel |
|---|---|
| Fast-paced | Slow-paced |
| Action-heavy | Reflective |
| Thriller feel | Literary feel |
| Reader breathless | Reader contemplative |
Key technique: Compress or expand sequels to control tempo. Scenes run at natural length; sequels are your pacing lever.
Scene-Level Diagnostic
Missing Goal
"What does the character want here?"
- If you can't answer clearly, scene lacks direction
- Fix: Establish goal in first paragraph
Static Conflict
"Does the opposition escalate?"
- If conflict stays at same level, scene feels flat
- Fix: Each beat makes goal harder to achieve
Weak Disaster
"Is the outcome too clean?"
- "Yes" endings without complications drain tension
- Fix: Add a "but" or "and furthermore"
Missing Sequel
"Did we process the previous scene?"
- Scene-to-scene jumps without sequels exhaust readers
- Fix: Even brief reaction paragraph helps
Too Much Sequel
"Are we wallowing in reaction?"
- Extended introspection without action stalls momentum
- Fix: Compress to essential beats, move to decision
Writing Modes in Scenes
| Mode | Best For | Common In |
|---|---|---|
| Action | Scene conflict | Scenes |
| Dialogue | Character interaction | Scenes |
| Description | Setting, slowing pace | Scene openings, Sequels |
| Introspection | Processing events | Sequels |
| Summarization | Time compression | Between scenes |
Mode should match function. Action in sequels feels rushed. Introspection in action kills momentum.
What You Do
- Ask about the goal — What does character want in this scene?
- Check escalation — Does conflict intensify?
- Examine the disaster — Is it too clean?
- Find the sequel — Is there processing time?
- Map the ratio — More scene or more sequel? Does that match intent?
- Trace the chain — Does decision lead to next scene's goal?
What You Don't Do
- Prescribe specific scene lengths
- Enforce rigid templates
- Demand sequel after every scene (pacing varies)
- Choose what should happen in scenes
Example Interaction
Writer: "The middle of my story feels exhausting but also slow somehow."
Your approach:
- Ask: "Walk me through a typical chapter—what happens?"
- Check for relentless scenes: "Is there processing time between action sequences?"
- Check for scene goals: "In the last scene you wrote, what did the character want?"
- Probe disaster quality: "How did that scene end? Did they get what they wanted?"
- If clean victories: "That might be draining tension. What 'but' could you add?"
- If missing sequels: "Adding even a paragraph of reaction before the next scene helps readers catch up"
Anti-Patterns
1. The Relentless Scene
Pattern: Pure action with no processing time—scene after scene of conflict without sequel beats. Why it fails: Reader becomes numb. Without processing time, emotional stakes flatten. Each new disaster hits with diminishing impact. The reader can't catch up. Fix: Insert sequel beats even in fast-paced stories. Even a paragraph of reaction helps. Compression is fine; elimination exhausts.
2. The Wallowing Sequel
Pattern: Pages of introspection without decision—extended internal monologue going in circles. Why it fails: Reader loses patience. Sequels exist to process and decide, not to wallow. Without forward motion toward decision, introspection becomes self-indulgence. Fix: Dilemma must lead to decision; decision to action. Time-box sequels. If the character isn't moving toward a choice, compress or cut.
Show full SKILL.md (531 more words)Show less
3. The Arbitrary Disaster
Pattern: Scene outcome disconnected from scene events—disaster that appears from nowhere to create drama. Why it fails: Readers sense manipulation. Disaster should be logical consequence of the conflict, not authorial intervention. Unmotivated disaster breaks trust. Fix: Trace the chain backward. How did scene conflict logically produce this disaster? If you can't answer, the disaster is arbitrary. Rework the conflict to set up the disaster.
4. The Clean Victory
Pattern: Character achieves goal without complications—scenes ending with simple "yes." Why it fails: Clean victories drain tension. Each unqualified success makes the next challenge feel less dangerous. Readers stop worrying. Fix: Add a "but" or "and furthermore." Goal achieved but new problem created. Victory came but cost more than expected. Simple success is rare; complications are normal.
5. Missing Goal
Pattern: Scene begins without clear character goal—things happen but there's no drive. Why it fails: Without goal, there's no conflict (nothing to oppose). Without conflict, there's no disaster (nothing to fail). The scene becomes description, not story. Fix: Establish goal in first paragraph. What does the POV character want in this scene specifically? If you can't answer clearly, the scene lacks direction.
Available Tools
analyze-scene.ts
Analyzes scene text for structure elements. Use when you need quick diagnostic on a specific scene.
# Analyze a scene file
deno run --allow-read scripts/analyze-scene.ts scene.txt
# Analyze text directly
deno run --allow-read scripts/analyze-scene.ts --text "She needed to find the key..."
# Get JSON output for further processing
deno run --allow-read scripts/analyze-scene.ts scene.txt --jsonWhat it detects:
- Goal indicators (want, need, trying to)
- Conflict indicators (but, blocked, obstacle)
- Disaster indicators (failed, worse, trapped)
- Reaction indicators (felt, emotion, shock)
- Dilemma indicators (choice, either, what if)
- Decision indicators (decided, will, plan)
Output includes:
- Scene/sequel ratio assessment
- Pacing classification (action-heavy, balanced, reflective)
- Missing element warnings
- Specific recommendations
When to use:
- Quick diagnostic on a draft scene
- Identifying why a scene feels off
- Checking pacing across multiple scenes
- Getting specific recommendations before deeper analysis
Output Persistence
This skill writes primary output to files so work persists across sessions.
Output Discovery
Before doing any other work:
- Check for
context/output-config.mdin the project - If found, look for this skill's entry
- If not found or no entry for this skill, ask the user first:
- "Where should I save output from this scene-sequencing session?"
- Suggest:
explorations/pacing/or a sensible location for this project
- Store the user's preference:
- In
context/output-config.mdif context network exists - In
.scene-sequencing-output.mdat project root otherwise
- In
Primary Output
For this skill, persist:
- Pacing diagnosis - scene/sequel balance, rhythm issues
- Scene analysis - goal, conflict, disaster for each scene
- Sequel analysis - reaction, dilemma, decision elements
- Recommendations - specific interventions for pacing issues
Conversation vs. File
| Goes to File | Stays in Conversation |
|---|---|
| Scene-by-scene breakdown | Discussion of specific scenes |
| Pacing diagnosis | Clarifying questions |
| Recommended interventions | Writer's structural decisions |
| Scene/sequel ratio assessment | Real-time feedback |
File Naming
Pattern: {story}-pacing-{date}.md
Example: novel-chapter5-pacing-2025-01-15.md
Integration
Inbound (feeds into this skill)
| Skill | What it provides |
|---|---|
| story-sense | Diagnosis that pacing is the problem area |
| key-moments | Emotional beats that need scene structure |
| outline-collaborator | Scene-level structure to analyze for pacing |
Outbound (this skill enables)
| Skill | What this provides |
|---|---|
| drafting | Properly paced scenes ready for prose generation |
| story-collaborator | Scene structures to generate prose within |
| revision | Pacing diagnosis for revision passes |
Complementary
| Skill | Relationship |
|---|---|
| key-moments | Key-moments identifies what emotional beats matter; scene-sequencing structures how to deliver them |
| dialogue | Scene-sequencing handles scene-level structure; dialogue operates within scenes at the exchange level |
© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in skills/creative/fiction/structure/scene-sequencing of jwynia/agent-skills.
- SKILL.md
- scripts/analyze-scene.ts
Open the folder on GitHubat commit e02ec7e
Compare with similar skills
Scene Sequencing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scene Sequencing this skilljwynia/agent-skills | 166 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Seedance SequenceEmily2040/seedance-2.0 | 7.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Scene Menu BarPostHog/posthog | 40k | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Sw Scene Craftjtydhr88/screenwriting-skills | 1.6k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Sequencesvellum-ai/vellum-assistant | 1.4k | — | ~589 | Automated safety check: Pass | MIT | |
| Sequence Psychologistsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Scene Menu Bar
PostHog/posthog
Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection.
Sw Scene Craft
jtydhr88/screenwriting-skills
Scene and sequence craft (场景/段落/细节/道具/悬念/情趣) — merged from Robert McKee's scene design and five-step scene analysis (value turn, beats, text/subtext, turning points, pacing, image systems), McKee's…
Sequences
vellum-ai/vellum-assistant
Create and manage automated email drip sequences. An agent skill from vellum-ai/vellum-assistant.
Sequence Psychologist
sickn33/agentic-awesome-skills
One sentence - what this skill does and when to invoke it. An agent skill from sickn33/agentic-awesome-skills.
Scenes
autonomous-ai/openharness
A skill your agent uses when working with Phaser 4 scenes. An agent skill from autonomous-ai/openharness.
More from jwynia/agent-skills
All 112 skills in this repoDevcontainer
jwynia/agent-skills
Diagnose devcontainer configuration problems and guide development environment setup.
Frontend Design
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
Gitea Workflow
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
Godot Asset Generator
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.
Mastra Hono
jwynia/agent-skills
Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.
PPTX Generator
jwynia/agent-skills
Create and manipulate PowerPoint PPTX files programmatically.
Questions about Scene Sequencing
What does Scene Sequencing do?
Structure scenes and control pacing using scene-sequel rhythm. Scene Sequencing is an agent skill from jwynia/agent-skills. Structure scenes and control pacing using scene-sequel rhythm.
When should I use Scene Sequencing?
Scene Sequencing fits situations like: individual scenes work but dont accumulate; pacing feels off (too rushed; transitions feel mechanical; readers can follow but arent compelled forward.
How do I install Scene Sequencing in Claude Code?
Run `npx skills add jwynia/agent-skills --skill scene-sequencing -a claude-code`. Or copy the skill folder (skills/creative/fiction/structure/scene-sequencing in jwynia/agent-skills) into .claude/skills/scene-sequencing in your project. Claude Code loads it when a task matches its description.
How do I install Scene Sequencing in Codex?
Run `npx skills add jwynia/agent-skills --skill scene-sequencing -a codex`. Or copy the skill folder (skills/creative/fiction/structure/scene-sequencing in jwynia/agent-skills) into .agents/skills/scene-sequencing in your project. Codex loads it when a task matches its description.
Can I use Scene Sequencing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill scene-sequencing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scene-sequencing, .gemini/skills/scene-sequencing, .github/skills/scene-sequencing and .opencode/skills/scene-sequencing in your project.
What does Scene Sequencing need to run?
Going by SKILL.md and its folder, Scene Sequencing needs TypeScript for the scripts in its folder and the command-line tools its instructions call (deno). Our summary lists: Node.js.
Does Scene Sequencing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Scene Sequencing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Scene Sequencing use?
Scene Sequencing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scene Sequencing use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Scene Sequencing?
Skills that share tags, products or a category with Scene Sequencing: Seedance Sequence (Emily2040/seedance-2.0, 7.5k stars), Scene Menu Bar (PostHog/posthog, 40k stars), Sw Scene Craft (jtydhr88/screenwriting-skills, 1.6k stars) and Sequences (vellum-ai/vellum-assistant, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scene Sequencing?
jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 166 GitHub stars. The repository holds 112 skills in this directory. The repository was last updated on February 24, 2026.
Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.