View Transitions
thedaviddias/Front-End-Checklist
A skill your agent uses when adding page transition animations, image expand/contract effects, shared-element transitions, or improving navigation UX in a single-page or multi-page application.
How to build scenes: entry, dialogue, pacing, transitions. An agent skill from BingHanOfUESTC/open_agent_team.
MITAuto-check passed
Install Scene Construction
$ npx skills add BingHanOfUESTC/open_agent_team --skill scene-construction -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-construction --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/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/teams/story_team/skills/scene-construction .claude/skills/scene-construction && 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-construction" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-construction into .claude/skills/scene-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-construction", 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/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-constructionType 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 BingHanOfUESTC/open_agent_team --skill scene-construction -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-construction --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/teams/story_team/skills/scene-construction .agents/skills/scene-construction && 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-construction" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-construction into .agents/skills/scene-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-construction", 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 BingHanOfUESTC/open_agent_team --skill scene-construction -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-construction --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/teams/story_team/skills/scene-construction .cursor/skills/scene-construction && 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-construction" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-construction into .cursor/skills/scene-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-construction", 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/BingHanOfUESTC/open_agent_team.git --path teams/story_team/skills/scene-construction--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 BingHanOfUESTC/open_agent_team --skill scene-construction -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-construction --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/teams/story_team/skills/scene-construction .gemini/skills/scene-construction && 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-construction" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-construction into .gemini/skills/scene-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-construction", 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 BingHanOfUESTC/open_agent_team scene-constructionInstalls 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 BingHanOfUESTC/open_agent_team --skill scene-construction -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .github/skills && cp -r skills-src/teams/story_team/skills/scene-construction .github/skills/scene-construction && 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-construction" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-construction into .github/skills/scene-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-construction", 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 BingHanOfUESTC/open_agent_team --skill scene-construction -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-construction --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/teams/story_team/skills/scene-construction .opencode/skills/scene-construction && 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-construction" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-construction into .opencode/skills/scene-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-construction", 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-construction- GitHub stars
- 106
- Token cost
- ~679 tokens
- SKILL.md length
- 369 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
How to build scenes: entry, dialogue, pacing, transitions. An agent skill from BingHanOfUESTC/open_agent_team.
- Evaluating how scenes work on the page
- SKILL.md covers Scene Entry, Dialogue, Pacing and Transitions
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Scene Construction is an agent skill from BingHanOfUESTC/open_agent_team. How to build scenes: entry, dialogue, pacing, transitions. Use when writing or evaluating how scenes work on the page.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Build persistent multi-agent teams that collaborate like real organizations to deliver complex tasks. The licence is MIT.
When your agent uses it
- Evaluating how scenes work on the page
Example prompts
- “/scene-construction”
What it can do on your machine
Read from SKILL.md and the folder at commit 7e28736. 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
No scripts in the folder and no shell commands in SKILL.md.
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 Construction loads about 679 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 369 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from BingHanOfUESTC/open_agent_team at commit 7e28736, republished under its MIT licence (© BingHanOfUESTC). 369 words, ~679 tokens.
Download SKILL.mdSave it as
.claude/skills/scene-construction/SKILL.md (or your agent's skills folder).- name
- scene-construction
- description
- How to build scenes: entry, dialogue, pacing, transitions. Use when writing or evaluating how scenes work on the page.
- type
- reference
- model-invocable
- false
Scene Construction
How scenes work on the page: how to enter, how dialogue works, how to pace
beats within and across scenes, how to transition. /prose-writing covers
sentence-level immersion; /story-architecture covers what scenes do in the
story.
Scene Entry
Open in the middle of something happening. A character mid-task, mid-conversation, or mid-thought gives the reader something to track immediately. Let them orient through action and context.
When the setting itself is the story beat, such as a character seeing a destroyed city for the first time or arriving somewhere that changes everything, the description carries narrative weight and earns the opening.
Dialogue
Dialogue does at least two things at once: advance the plot AND reveal character, or reveal character AND build tension, or build tension AND seed information. Single-purpose dialogue ("As you know, the reactor is on the third floor") feels flat because real conversation is never purely transactional.
Subtext. Characters rarely say exactly what they mean. They deflect, understate, change the subject, answer a different question than the one asked. The gap between what's said and what's meant is where characterization lives.
Voice differentiation. Each character should sound distinct enough that you could identify the speaker without dialogue tags. Vocabulary, sentence structure, speech patterns, what they choose to talk about.
Action beats over dialogue tags. "Said" is invisible; use it freely. Use action beats to show how something is said: "She set the cup down carefully. 'That's not what I meant.'"
Show full SKILL.md (127 more words)Show less
Pacing
Alternate between high-tension and lower-tension beats within a scene. Sustained intensity becomes numbing. The quiet moment after the crisis is what gives the crisis weight.
Chapter-level: end on forward momentum: an unanswered question, a new complication, an emotional shift. Give the reader a reason to continue.
Sentence-level rhythm (length, structure, speed control) lives in
/prose-writing.
Transitions
Move between scenes and time periods without losing the reader. A hard scene break (whitespace or divider) resets time and place cleanly. A soft transition within a scene compresses time: "The next three weeks passed in a blur of training."
Match transition weight to what's being skipped. If nothing important happens between scenes, a hard break is enough. If the skipped time matters emotionally, a brief transitional passage acknowledges it.
© BingHanOfUESTC, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in teams/story_team/skills/scene-construction of BingHanOfUESTC/open_agent_team.
Open the folder on GitHubat commit 7e28736
Compare with similar skills
Scene Construction 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 Construction this skillBingHanOfUESTC/open_agent_team | 106 | — | ~679 | Automated safety check: Pass | MIT | |
| View Transitionsthedaviddias/Front-End-Checklist | 74k | — | ~528 | Automated safety check: Pass | MIT | |
| Changelog Entrysickn33/agentic-awesome-skills | 47k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Vercel React View Transitionssickn33/agentic-awesome-skills | 47k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Paper Cinder TransitionMengTo/Skills | 6.7k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Scene Menu BarPostHog/posthog | 40k | — | ~3.2k | Automated safety check: Pass | Custom licence |
Similar skills
Changelog Entry
sickn33/agentic-awesome-skills
Generate a properly formatted CHANGELOG.md entry in Keep a Changelog format from a commit range or PR.
Vercel React View Transitions
sickn33/agentic-awesome-skills
Guide React and Next.js view transitions, shared element animations, route transitions, transition types, and reduced-motion-safe UI state animation.
Paper Cinder Transition
MengTo/Skills
Change between pages, chapters or scenes with a paper-burn transition, a ragged ember line that sweeps across the frame, chars the old page ahead of it and reveals the next scene live behind it…
- Official
Scene Menu Bar
PostHog/posthog
Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection.
Nexrad Mosaic Construction
sickn33/agentic-awesome-skills
Construct a quality-aware NEXRAD multi-radar mosaic from aligned single-site products with explicit coverage, beam geometry, quality weighting, overlap resolution, and provenance.
More from BingHanOfUESTC/open_agent_team
All 30 skills in this repoSkill Validation And Evaluation
BingHanOfUESTC/open_agent_team
A skill your agent uses when validating a newly created or updated agent skill with structure checks, routing positive and negative examples, contamination checks, progressive disclosure review, and…
Autoresearch Orchestration
BingHanOfUESTC/open_agent_team
A skill your agent uses when autoresearchteam needs to manage an end-to-end research lifecycle from Boss brief to literature, idea, implementation, experiments, synthesis, and LaTeX delivery.
Experiment Iteration Loop
BingHanOfUESTC/open_agent_team
A skill your agent uses when designing, running, logging, diagnosing, or iterating experiments for the selected research idea.
Latex Paper Artifact
BingHanOfUESTC/open_agent_team
A skill your agent uses when producing the final arXiv-style LaTeX paper, BibTeX, figures, tables, reproducibility statement, appendix, and artifact manifest.
Literature Evidence Mapping
BingHanOfUESTC/open_agent_team
A skill your agent uses when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
Media Asset Sourcing
BingHanOfUESTC/open_agent_team
A skill your agent uses when PPT slides need external images, screenshots, logos, product photos, stock-like visuals, diagrams, or videos that must be downloaded, inserted, or linked with source and…
Questions about Scene Construction
What does Scene Construction do?
How to build scenes: entry, dialogue, pacing, transitions. An agent skill from BingHanOfUESTC/open_agent_team. Scene Construction is an agent skill from BingHanOfUESTC/open_agent_team. How to build scenes: entry, dialogue, pacing, transitions.
When should I use Scene Construction?
Scene Construction fits situations like: evaluating how scenes work on the page.
How do I install Scene Construction in Claude Code?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill scene-construction -a claude-code`. Or copy the skill folder (teams/story_team/skills/scene-construction in BingHanOfUESTC/open_agent_team) into .claude/skills/scene-construction in your project. Claude Code loads it when a task matches its description.
How do I install Scene Construction in Codex?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill scene-construction -a codex`. Or copy the skill folder (teams/story_team/skills/scene-construction in BingHanOfUESTC/open_agent_team) into .agents/skills/scene-construction in your project. Codex loads it when a task matches its description.
Can I use Scene Construction 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 BingHanOfUESTC/open_agent_team --skill scene-construction -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-construction, .gemini/skills/scene-construction, .github/skills/scene-construction and .opencode/skills/scene-construction in your project.
What does Scene Construction need to run?
SKILL.md names no scripts, command-line tools or credentials: Scene Construction is instructions for the agent only.
Does Scene Construction 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 Construction 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. Review the folder before installing.
What licence does Scene Construction use?
Scene Construction is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scene Construction use?
About 679 tokens (SKILL.md is roughly 2.7k 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 Construction?
Skills that share tags, products or a category with Scene Construction: View Transitions (thedaviddias/Front-End-Checklist, 74k stars), Changelog Entry (sickn33/agentic-awesome-skills, 47k stars), Vercel React View Transitions (sickn33/agentic-awesome-skills, 47k stars) and Paper Cinder Transition (MengTo/Skills, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scene Construction?
BingHanOfUESTC (a GitHub user) maintains it in BingHanOfUESTC/open_agent_team, which has 106 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on June 23, 2026.
Source: BingHanOfUESTC/open_agent_team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.