菜单
Install or update project-local open_supports packages from .claude/open_supports_name_list.txt by using scripts/install-open-supports.sh.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fix npm global install failures for @openai/codex when ENOTEMPTY rename conflicts occur in the global node_modules path.
Write skill_for_setup/SKILL.md and skill_for_setup/README.md for any open-source library in the open_supports/ system. Use after scripts_for_install/ is complete. Implements the script-first pattern: primary path runs the install script; fallback follows repo_readme_summary.md Part 2.
Use when creating or updating an open_supports support package end-to-end, especially when coordinating repo summary, install script, setup skill, clarification, resume, or optional install verification.
帮助用户安装并配置 OpenSpec。主路径：运行支持包内的一键脚本；脚本不可用时回退到 repo_readme_summary.md 第 2 部分。范围：安装/更新 CLI、验证版本、可选初始化或更新项目；不含卸载、删除生成文件或详细使用教程。
Write scripts_for_install/install.sh for any open-source library in the open_supports/ system. Use when adding a new support package that needs a one-click installation script. Produces a POSIX sh script with platform detection, flag-driven interface, and idempotent behavior.
Write repo_readme_summary.md for any open-source library in the open_supports/ system. Use when adding a new support package or updating an existing summary. Produces a concise 5-part structured document distilled from the official README.
| name | open-supports-install |
| description | Install or update project-local open_supports packages from .claude/open_supports_name_list.txt by using scripts/install-open-supports.sh. |
| argument-hint | -t <project> [--skills-only|--no-skills|--dry-run|-F] |
Use this Skill when the user asks to install, update, vendor, or inspect
open_supports/ packages for a project.
Before running commands:
.claude/open_supports_name_list.txt.open_supports/README.md.docs/superpowers/specs/2026-07-01-open-supports-installer-design.md if present.Default to the current working directory as the target project when the user does not specify a target.
Run from the rule source repository:
sh scripts/install-open-supports.sh -t /path/to/project
Useful modes:
sh scripts/install-open-supports.sh -t /path/to/project --dry-run
sh scripts/install-open-supports.sh -t /path/to/project --skills-only
sh scripts/install-open-supports.sh -t /path/to/project --no-skills
sh scripts/install-open-supports.sh -t /path/to/project -F
If a custom list file is requested:
sh scripts/install-open-supports.sh -t /path/to/project -l /path/to/open_supports_name_list.txt
If a custom open_supports/ source root is requested:
sh scripts/install-open-supports.sh -t /path/to/project -s /path/to/open_supports
After the command finishes, report:
missing, no_script, failed, or conflict counts;