菜单
Consult OpenSymphony project memory before planning nontrivial work, during review rework, and before documentation updates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when producing a finished video end-to-end from raw source media. This skill covers the full render → verify → iterate workflow: transcribe → pack → reason → EDL → render → verify → iterate. It is the single entry-point skill for end-to-end video production, delegating to sub-skills for ingestion, subtitle pipeline, and rough-cut assembly where appropriate.
Use when building a rough cut from a storyboard, shot list, or EDL spec. Covers EDL-based rendering (the primary path), color grading, audio fades, loudness normalization, and self-evaluation — plus the simpler card/image/clip workflow for quick assemblies.
Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric/mathematical content.
Use this skill when a docs/tasks/task-package.yaml planning wave should be validated, previewed, or published to Linear with milestone assignments, parent/sub-issue relationships, blocker relations, and publish state.
Generate a structured implementation plan from project requirements with decomposed tasks, milestones, dependencies, and acceptance criteria. Use when starting a new project or planning a new development wave that should produce docs/tasks/task-package.yaml and issue-ready task files.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
| name | opensymphony-memory |
| description | Consult OpenSymphony project memory before planning nontrivial work, during review rework, and before documentation updates. |
Use this skill when working in a repository that has OpenSymphony memory enabled. Memory is the post-merge record of completed issue work. It is useful context, but current code, tests, and explicit user instructions remain authoritative.
Run the smallest command that answers the question:
opensymphony memory context --issue COE-456
opensymphony memory related --issue COE-456
opensymphony memory related --paths crates/opensymphony-openhands
opensymphony memory related --area openhands-runtime
opensymphony memory search "subscription credential refresh"
opensymphony memory docs --area openhands-runtime
opensymphony memory brief COE-123
Use opensymphony memory status when you need to know whether memory exists,
is pending docs sync, or has capture warnings. Use opensymphony memory lint --public-docs before relying on generated public docs in a public repository.
memory.auto_capture is enabled.opensymphony memory sync-docs so the managed sections and indexes stay consistent.Memory output separates source-derived facts from generated synthesis when the
capture has enough evidence. Prefer source refs such as Linear issue IDs, PR
URLs, and merge SHAs when making audit claims. Merge SHA is an immutable pointer
to the merged code state, not an area inference signal. If memory is stale,
missing, or warning-heavy, inspect the linked PRs, current docs, and
opensymphony debug ISSUE-ID before depending on it.