Orchestration Graph Runner
Yeachan-Heo/oh-my-claudecode
Runs deterministic DAG pipelines from a JSON descriptor with journal-based crash recovery, so an interrupted run resumes without repeating finished nodes.
Runs agency-orchestrator YAML workflows inside the current agent session, with the session's own model playing each role in turn and no API key needed.
SKILL.md written in Chinese; this summary is our English description.
Install Agency Orchestrator Workflow Runner
$ npx skills add jnMetaCode/superpowers-zh --skill workflow-runner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jnMetaCode/superpowers-zh workflow-runner --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/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/workflow-runner .claude/skills/workflow-runner && 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 "workflow-runner" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/workflow-runner into .claude/skills/workflow-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-runner", 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/jnMetaCode/superpowers-zh/tree/main/skills/workflow-runnerType 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 jnMetaCode/superpowers-zh --skill workflow-runner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jnMetaCode/superpowers-zh workflow-runner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/workflow-runner .agents/skills/workflow-runner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workflow-runner" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/workflow-runner into .agents/skills/workflow-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-runner", 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 jnMetaCode/superpowers-zh --skill workflow-runner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jnMetaCode/superpowers-zh workflow-runner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/workflow-runner .cursor/skills/workflow-runner && 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 "workflow-runner" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/workflow-runner into .cursor/skills/workflow-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-runner", 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/jnMetaCode/superpowers-zh.git --path skills/workflow-runner--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 jnMetaCode/superpowers-zh --skill workflow-runner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jnMetaCode/superpowers-zh workflow-runner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/workflow-runner .gemini/skills/workflow-runner && 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 "workflow-runner" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/workflow-runner into .gemini/skills/workflow-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-runner", 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 jnMetaCode/superpowers-zh workflow-runnerInstalls 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 jnMetaCode/superpowers-zh --skill workflow-runner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/workflow-runner .github/skills/workflow-runner && 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 "workflow-runner" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/workflow-runner into .github/skills/workflow-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-runner", 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 jnMetaCode/superpowers-zh --skill workflow-runner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jnMetaCode/superpowers-zh workflow-runner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/workflow-runner .opencode/skills/workflow-runner && 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 "workflow-runner" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/workflow-runner into .opencode/skills/workflow-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-runner", 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
workflow-runner- GitHub stars
- 8.3k
- Used in
- 1 other repo
- Token cost
- ~885 tokens
- SKILL.md length
- 219 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Runs agency-orchestrator YAML workflows inside the current agent session, with the session's own model playing each role in turn and no API key needed.
- Works in 4 steps: 当前工作目录下的 {agents_dir}/（如… → ../{agents_dir}/（上级目录） → 相对于 YAML 文件所在目录的 {agents_dir}/ → …
- Running a .yaml workflow file from the agency-orchestrator project
- SKILL.md covers 适用场景, 执行流程（5 步）, 重要规则 and 没有 YAML 文件时的快捷模式, plus 1 more section
- Calls git and npm; reaches github.com
What it does
This skill executes a multi-role workflow defined in a YAML file without the separate CLI. It parses the file, ignores CLI-only settings such as llm, concurrency, timeout and retry, and looks for the role definition folder (agency-agents-zh) in the working directory, its parent, the YAML file's directory and node_modules, stopping with install instructions if none exists. Required inputs are requested from you, and optional ones take their defaults.
Steps are sorted into layers from their depends_on links, and the plan is shown. For each layer the agent reads every role's markdown file, fills the task template with inputs and earlier outputs, then plays the role itself or, for parallel steps, starts one sub-agent per step with the full role text. Results go under .ao-output in a folder named for the workflow and date, with per-step outputs, a summary and metadata.json. Hard rules forbid skipping steps or running one without reading its role file. The skill text is in Chinese.
When your agent uses it
- Running a .yaml workflow file from the agency-orchestrator project
- Having several roles, such as a product manager and an architect, review a PRD together
- Running multi-role workflows without setting up an API key
Example prompts
- “Run workflows/story-creation.yaml and show me each role's step.”
- “Have a product manager and an architect review this PRD together.”
- “Execute my workflow file and save every step's output to disk.”
Requirements
- A workflow .yaml file
- The agency-agents-zh role definitions, from git clone or npm install
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 当前工作目录下的 {agents_dir}/（如 ./agency-agents-zh/）
- ../{agents_dir}/（上级目录）
- 相对于 YAML 文件所在目录的 {agents_dir}/
- node_modules/agency-agents-zh/
What it can do on your machine
Read from SKILL.md and the folder at commit fe34019. 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
Shell commands in SKILL.md call:
gitnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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
Agency Orchestrator Workflow Runner loads about 885 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 219 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 jnMetaCode/superpowers-zh at commit fe34019, republished under its MIT licence (© jnMetaCode). 219 words, ~885 tokens.
Download SKILL.mdSave it as
.claude/skills/workflow-runner/SKILL.md (or your agent's skills folder).- name
- workflow-runner
- description
- 在 Claude Code / OpenClaw / Cursor 中直接运行 agency-orchestrator YAML 工作流——无需 API key，使用当前会话的 LLM 作为执行引擎。当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发。
- version
- 1.0.0
- license
- MIT
工作流执行器：在 AI 工具内运行多角色编排
直接在当前会话中执行 agency-orchestrator 的 YAML 工作流，无需配置 API key。当前 LLM 就是执行引擎——依次扮演每个角色完成任务。
适用场景
- 用户提供了一个
.yaml工作流文件（如运行 workflows/story-creation.yaml） - 用户要求多个角色协作完成任务（如"用产品经理和架构师一起评审这个 PRD"）
- 用户安装了
agency-agents-zh并希望直接在 AI 工具内编排多角色
执行流程（5 步）
按以下顺序执行，不要跳步：
第 1 步：解析工作流
用 Read 工具读取用户指定的 YAML 文件，提取以下字段：
name: "工作流名称"
agents_dir: "agency-agents-zh" # 角色定义目录
inputs: # 输入变量
- name: xxx
required: true/false
default: "默认值"
steps: # 执行步骤
- id: step_id
role: "category/agent-name" # 角色路径
task: "任务描述 {{变量}}" # 支持模板变量
output: variable_name # 输出变量名
depends_on: [other_step_id] # 依赖关系忽略 llm、concurrency、timeout、retry 配置——Skill 模式使用当前会话的 LLM，这些字段仅用于 CLI 模式。
定位角色目录：用 Bash test -d 按以下顺序检查，用第一个存在的：
- 当前工作目录下的
{agents_dir}/（如./agency-agents-zh/） ../{agents_dir}/（上级目录）- 相对于 YAML 文件所在目录的
{agents_dir}/ node_modules/agency-agents-zh/
如果全部找不到，停止执行并提示用户：
找不到角色目录。请先安装：
git clone --depth 1 https://github.com/jnMetaCode/agency-agents-zh.git
或：npm install agency-agents-zh第 2 步：收集输入
- 对每个
required: true的输入，检查用户消息中是否已提供值 - 未提供的必填输入：立即向用户询问，不要猜测或用空值
- 有
default的可选输入：使用默认值 - 无默认值的可选输入：设为空字符串
第 3 步：构建执行顺序
根据 depends_on 进行拓扑排序，将步骤分成多个层级：
- 无 depends_on 的步骤 → 第 1 层
- depends_on 全部在第 N 层或之前的步骤 → 第 N+1 层
- 同一层内的步骤互不依赖，可并行
在回复中展示执行计划：
执行计划（共 N 步）：
第 1 层: [step_id] — 角色名
第 2 层: [step_a, step_b] — 并行
第 3 层: [step_id] — 角色名第 4 步：逐层执行
对每一层：
4a. 预读角色文件
用 Read 工具读取该层所有步骤的角色 .md 文件：{角色目录}/{role}.md
从文件中提取：
- 角色名：frontmatter 中的
name字段 - 角色 system prompt：第二个
---之后的全部 markdown 内容
4b. 渲染 task 模板
将 task 中的 {{变量名}} 替换为：
- 来自 inputs 的用户输入值
- 来自前序步骤 output 的结果文本
4c. 执行
单步骤层：直接在主会话中扮演该角色执行。格式：
### Step N/Total: step_id（角色名）
[以该角色身份完成 task，使用角色的专业知识和沟通风格]多步骤层（并行）：使用 Agent 工具为每个步骤启动子代理。每个子代理的 prompt 必须包含：
- 角色文件的完整文本内容（不是路径——子代理可能无法读文件）
- 渲染后的 task 文本
- 指令："以上是你的角色定义，请以该角色身份完成以下任务，直接输出结果"
4d. 保存输出到上下文
如果 step 有 output 字段，将该步骤的输出文本存入变量上下文，供后续步骤的 {{变量}} 使用。
第 5 步：保存结果并展示
用 Write 工具将结果保存到文件：
.ao-output/{工作流名称}-{YYYY-MM-DD}/
├── steps/
│ ├── 1-{step_id}.md # 每步的输出
│ ├── 2-{step_id}.md
│ └── ...
├── summary.md # 最后一步的完整输出（最终成果）
└── metadata.json # 基本元数据metadata.json 格式：
{
"name": "工作流名称",
"date": "2026-03-22",
"success": true,
"steps": [
{"id": "step_id", "role": "category/agent", "status": "completed"},
...
]
}执行完毕后，向用户展示：
- 最终成果（summary.md 的内容）
- 文件保存位置
- 执行了几个步骤
重要规则
<HARD-GATE>
- 每个步骤都必须真正扮演对应角色，使用该角色的专业知识和沟通风格，不能泛泛回答
- 角色切换必须明确——每步开始时标注角色名
- 不要跳过步骤或合并步骤，严格按 DAG 层级顺序执行
- 如果角色文件找不到，告知用户并建议安装 agency-agents-zh
- 不要在没有读取角色 .md 文件的情况下执行步骤——必须先 Read 再执行
</HARD-GATE>没有 YAML 文件时的快捷模式
如果用户没有指定 YAML 文件，但描述了需要多角色协作的任务：
- 根据用户描述，自动生成 YAML 工作流定义
- 展示给用户确认
- 确认后按上述流程执行
示例：
- 用户说"帮我用叙事学家和心理学家写个故事" → 生成 story-creation 类似的工作流
- 用户说"让产品经理和架构师评审这个 PRD" → 生成 product-review 类似的工作流
故障处理
- 角色文件不存在：提示用户运行
ao init或npm install agency-agents-zh - 模板变量未定义：检查上下文，如果是必填输入则向用户询问
- 步骤执行失败：标记该步骤为失败，跳过所有依赖它的下游步骤，继续执行其他独立步骤
© jnMetaCode, 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 skills/workflow-runner of jnMetaCode/superpowers-zh.
Open the folder on GitHubat commit fe34019
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jnMetaCode/superpowers-zh, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Agency Orchestrator Workflow Runner 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 |
|---|---|---|---|---|---|---|
| Agency Orchestrator Workflow Runner this skilljnMetaCode/superpowers-zh | 8.3k | 1 repos | ~885 | Automated safety check: Pass | MIT | |
| Orchestration Graph RunnerYeachan-Heo/oh-my-claudecode | 40k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Prowl Agent Workflowsonevcat/Prowl | 631 | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| cmux Agent Surface Controldisler/learning-cmux-with-agents | 115 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Parallel Batch OperationsQwenLM/qwen-code | 28k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Flow Nexus Swarmruvnet/agentic-flow | 816 | 4 repos | ~4.2k | Automated safety check: Pass | None |
Similar skills
Prowl Agent Workflows
onevcat/Prowl
Authors, validates, runs and participates in Prowl Agent Workflows, bundles that orchestrate several live coding agents inside the Prowl macOS app.
cmux Agent Surface Control
disler/learning-cmux-with-agents
Drives the cmux terminal multiplexer from natural language to open, inspect, prompt, read and close windows, workspaces, panes, surfaces and agent sessions.
Parallel Batch Operations
QwenLM/qwen-code
Runs one operation across many files with parallel worker agents: finds files by glob pattern, splits them into chunks, launches workers and summarizes the results.
Flow Nexus Swarm
ruvnet/agentic-flow
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform
Fastgpt Workflow Generator
YYH211/Claude-meta-skill
Generates production-ready FastGPT workflow JSON from natural language requirements.
More from jnMetaCode/superpowers-zh
All 21 skills in this repoBrainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
Git Worktree Isolation
jnMetaCode/superpowers-zh
Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.
Inline Plan Execution
jnMetaCode/superpowers-zh
Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.
Chinese Code Review Etiquette
jnMetaCode/superpowers-zh
Gives Chinese-language templates and priority labels for code review feedback, plus guidance on bilingual comments, commit messages and common team anti-patterns.
Chinese Commit Conventions
jnMetaCode/superpowers-zh
Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.
Chinese Documentation Style Guide
jnMetaCode/superpowers-zh
Reference rules for typesetting Chinese technical documents: spacing around English and digits, punctuation, term handling, bilingual API docs and README layout.
Related
Categories
Questions about Agency Orchestrator Workflow Runner
What does Agency Orchestrator Workflow Runner do?
Runs agency-orchestrator YAML workflows inside the current agent session, with the session's own model playing each role in turn and no API key needed. This skill executes a multi-role workflow defined in a YAML file without the separate CLI. It parses the file, ignores CLI-only settings such as llm, concurrency, timeout and retry, and looks for the role definition folder (agency-agents-zh) in the working directory, its parent, the YAML file's directory and node_modules, stopping with install instructions if none exists.
When should I use Agency Orchestrator Workflow Runner?
Agency Orchestrator Workflow Runner fits situations like: running a .yaml workflow file from the agency-orchestrator project; having several roles, such as a product manager and an architect, review a PRD together; running multi-role workflows without setting up an API key.
How do I install Agency Orchestrator Workflow Runner in Claude Code?
Run `npx skills add jnMetaCode/superpowers-zh --skill workflow-runner -a claude-code`. Or copy the skill folder (skills/workflow-runner in jnMetaCode/superpowers-zh) into .claude/skills/workflow-runner in your project. Claude Code loads it when a task matches its description.
How do I install Agency Orchestrator Workflow Runner in Codex?
Run `npx skills add jnMetaCode/superpowers-zh --skill workflow-runner -a codex`. Or copy the skill folder (skills/workflow-runner in jnMetaCode/superpowers-zh) into .agents/skills/workflow-runner in your project. Codex loads it when a task matches its description.
Can I use Agency Orchestrator Workflow Runner 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 jnMetaCode/superpowers-zh --skill workflow-runner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-runner, .gemini/skills/workflow-runner, .github/skills/workflow-runner and .opencode/skills/workflow-runner in your project.
What does Agency Orchestrator Workflow Runner need to run?
Going by SKILL.md and its folder, Agency Orchestrator Workflow Runner needs the command-line tools its instructions call (git and npm). Our summary lists: A workflow .yaml file; The agency-agents-zh role definitions, from git clone or npm install.
Does Agency Orchestrator Workflow Runner access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Agency Orchestrator Workflow Runner 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 Agency Orchestrator Workflow Runner use?
Agency Orchestrator Workflow Runner 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 Agency Orchestrator Workflow Runner use?
About 885 tokens (SKILL.md is roughly 3.5k 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 Agency Orchestrator Workflow Runner?
Skills that share tags, products or a category with Agency Orchestrator Workflow Runner: Orchestration Graph Runner (Yeachan-Heo/oh-my-claudecode, 40k stars), Prowl Agent Workflows (onevcat/Prowl, 631 stars), cmux Agent Surface Control (disler/learning-cmux-with-agents, 115 stars) and Parallel Batch Operations (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agency Orchestrator Workflow Runner?
jnMetaCode (a GitHub user) maintains it in jnMetaCode/superpowers-zh, which has 8,265 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 4, 2026.
Source: jnMetaCode/superpowers-zh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.