Make Interfaces Feel Better
affaan-m/ECC
Apply concrete design-engineering details that make interfaces feel polished.
Scene-level tension and causation engine. An agent skill from BingHanOfUESTC/open_agent_team.
MITAuto-check passed
Install Scene Tension Engine
$ npx skills add BingHanOfUESTC/open_agent_team --skill scene-tension-engine -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-tension-engine --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-tension-engine .claude/skills/scene-tension-engine && 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-tension-engine" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-tension-engine into .claude/skills/scene-tension-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-tension-engine", 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-tension-engineType 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-tension-engine -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-tension-engine --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-tension-engine .agents/skills/scene-tension-engine && 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-tension-engine" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-tension-engine into .agents/skills/scene-tension-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-tension-engine", 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-tension-engine -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-tension-engine --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-tension-engine .cursor/skills/scene-tension-engine && 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-tension-engine" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-tension-engine into .cursor/skills/scene-tension-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-tension-engine", 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-tension-engine--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-tension-engine -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team scene-tension-engine --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-tension-engine .gemini/skills/scene-tension-engine && 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-tension-engine" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-tension-engine into .gemini/skills/scene-tension-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-tension-engine", 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-tension-engineInstalls 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-tension-engine -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-tension-engine .github/skills/scene-tension-engine && 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-tension-engine" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-tension-engine into .github/skills/scene-tension-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-tension-engine", 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-tension-engine -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-tension-engine --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-tension-engine .opencode/skills/scene-tension-engine && 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-tension-engine" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/scene-tension-engine into .opencode/skills/scene-tension-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scene-tension-engine", 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-tension-engine- GitHub stars
- 106
- Token cost
- ~234 tokens
- SKILL.md length
- 21 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Scene-level tension and causation engine. An agent skill from BingHanOfUESTC/open_agent_team.
- Works in 5 steps: 场景四问 → 变化类型 → 场景进入 → …
- Scenes feel flat
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Over-explanatory
What it does
Scene Tension Engine is an agent skill from BingHanOfUESTC/open_agent_team. Scene-level tension and causation engine. Use when scenes feel flat, sequential, over-explanatory, or when revision needs every scene to change power, knowledge, relationship, or stakes.
Its SKILL.md is about 230 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
- Scenes feel flat
- Over-explanatory
- Revision needs every scene to change power
Example prompts
- “/scene-tension-engine”
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 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 Tension Engine loads about 234 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 21 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). 21 words, ~234 tokens.
Download SKILL.mdSave it as
.claude/skills/scene-tension-engine/SKILL.md (or your agent's skills folder).- name
- scene-tension-engine
- description
- Scene-level tension and causation engine. Use when scenes feel flat, sequential, over-explanatory, or when revision needs every scene to change power, knowledge, relationship, or stakes.
- type
- reference
- model-invocable
- false
Scene Tension Engine
一个场景存在的理由不是“这里发生了一些事”，而是“读者、人物或关系在这里发生了不可逆变化”。
1. 场景四问
每场必须回答：
谁想要什么？
谁或什么阻止他？
场景结束时什么变了？
这个变化如何逼出下一场？没有变化的场景，删除、合并或重写。
2. 变化类型
场景至少改变一种东西：
权力：谁占上风发生变化。
知识：人物或读者知道了新事实。
关系：亲密、信任、亏欠、威胁发生变化。
风险：损失变得更近、更具体或更不可逆。
自我认知：人物对自己的谎言出现裂缝。短篇优先选择能同时改变两种以上的场景。
3. 场景进入
默认从压力已经开始的地方进入：
谈判已经破裂
尸体已经被发现
谎言已经说出口
钱已经不见
门外的人已经敲第三次把铺垫埋在动作、对话和细节里，不要先铺完再开戏。
4. 场景退出
不要在情绪解释完之后才离场。优先停在：
人物刚做完无法撤回的动作
读者刚意识到某个事实更糟
一句话改变了关系
一个细节让前文意义反转5. 重写方法
把闲聊改成交易、审问、隐瞒、告别或勒索。
给每个场景设置一个倒计时或外部压力。
删掉人物已经知道、读者也已经知道的信息交换。
让对话每三到五轮发生一次权力转移。
用动作暴露情绪，用物件承载关系变化。© 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-tension-engine of BingHanOfUESTC/open_agent_team.
Open the folder on GitHubat commit 7e28736
Compare with similar skills
Scene Tension Engine 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 Tension Engine this skillBingHanOfUESTC/open_agent_team | 106 | — | ~234 | Automated safety check: Pass | MIT | |
| Make Interfaces Feel Betteraffaan-m/ECC | 276k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Scene Menu BarPostHog/posthog | 40k | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Scenesautonomous-ai/openharness | 1.2k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Scene Establishing-Shot Promptchatfire-AI/huobao-drama | 16k | — | ~378 | Automated safety check: Pass | Custom licence | |
| Horizontal Scroll ScenesMengTo/Skills | 6.7k | — | ~2.5k | 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.
Scenes
autonomous-ai/openharness
A skill your agent uses when working with Phaser 4 scenes. An agent skill from autonomous-ai/openharness.
Scene Establishing-Shot Prompt
chatfire-AI/huobao-drama
Writes the final image prompt for a clear wide establishing shot of an empty scene, fixing foreground, midground, background, exits, floor, walls and key furnishings.
Horizontal Scroll Scenes
MengTo/Skills
Build scene-by-scene chapters that advance left to right on one fixed stage while the user scrolls vertically, with native scroll as the only input.
Scene
autonomous-ai/Physical-AI-Operating-System
Activate predefined lighting scene presets (reading, focus, relax, movie, night, energize) when the user asks for activity-based or environment lighting.
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 Tension Engine
What does Scene Tension Engine do?
Scene-level tension and causation engine. An agent skill from BingHanOfUESTC/open_agent_team. Scene Tension Engine is an agent skill from BingHanOfUESTC/open_agent_team. Scene-level tension and causation engine.
When should I use Scene Tension Engine?
Scene Tension Engine fits situations like: scenes feel flat; over-explanatory; revision needs every scene to change power.
How do I install Scene Tension Engine in Claude Code?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill scene-tension-engine -a claude-code`. Or copy the skill folder (teams/story_team/skills/scene-tension-engine in BingHanOfUESTC/open_agent_team) into .claude/skills/scene-tension-engine in your project. Claude Code loads it when a task matches its description.
How do I install Scene Tension Engine in Codex?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill scene-tension-engine -a codex`. Or copy the skill folder (teams/story_team/skills/scene-tension-engine in BingHanOfUESTC/open_agent_team) into .agents/skills/scene-tension-engine in your project. Codex loads it when a task matches its description.
Can I use Scene Tension Engine 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-tension-engine -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-tension-engine, .gemini/skills/scene-tension-engine, .github/skills/scene-tension-engine and .opencode/skills/scene-tension-engine in your project.
What does Scene Tension Engine need to run?
SKILL.md names no scripts, command-line tools or credentials: Scene Tension Engine is instructions for the agent only.
Does Scene Tension Engine 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 Tension Engine 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 Tension Engine use?
Scene Tension Engine 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 Tension Engine use?
About 234 tokens (SKILL.md is roughly 936 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 Tension Engine?
Skills that share tags, products or a category with Scene Tension Engine: Make Interfaces Feel Better (affaan-m/ECC, 276k stars), Scene Menu Bar (PostHog/posthog, 40k stars), Scenes (autonomous-ai/openharness, 1.2k stars) and Scene Establishing-Shot Prompt (chatfire-AI/huobao-drama, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scene Tension Engine?
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.