Clarify Codex Claude scope and private skills

AGENTS.md

@@ -25,6 +25,28 @@ Rule #1: If you want exception to ANY rule, YOU MUST STOP and get explicit permi
 - We discuss architectural decisions (framework changes, major refactoring, system design) together before implementation. Routine fixes and clear implementations don't need discussion.
 - You may use sub-agents or parallel agents for independent work without asking again each time when the current host/runtime provides the capability. This is a standing preference, not a requirement: use them when they create clear leverage, and stay local when they do not.
 
+## Access and approval boundary
+
+- Broad filesystem or tool access is operational capability, not blanket approval.
+- High-risk actions require an explicit stop and ask before proceeding.
+- High-risk actions include anything that would delete data, prune history, rotate credentials, change permissions, touch production, deployment, billing, external accounts, secrets, auth state, browser profiles, public sharing, protected branches, hooks, or test enforcement.
+- Use permission profiles, hooks, or approval layers when the current host/runtime supports them, but never treat those mechanisms as a replacement for judgment.
+
+## Source of truth and memory
+
+- Memory is a recall layer, not a source of truth.
+- When memory or prior summaries conflict with current evidence, repo docs, scripts, tests, AGENTS files, and observed runtime output win.
+- Project-specific operating knowledge belongs in project docs or project skills, with repo-local source-of-truth pointers when a skill is required.
+
+## Skill creation and QA
+
+- When creating or editing a skill, treat the skill as tested process code, not just prose.
+- Start with a failing test or explicit pressure scenario before writing the skill change when the host or repo can support it.
+- Keep skill bodies concise and move detailed procedures into reference files when that makes the trigger behavior clearer.
+- After skill edits, run the skill validator, run relevant repo tests, check for private paths and secrets, and inspect the rendered or installed result when applicable.
+- When a skill has both a repo catalog source and runtime copy, verify any runtime copy separately from the repo catalog source.
+- Do not claim a skill is ready only because the Markdown looks reasonable.
+
 # Proactiveness
 
 When asked to do something, just do it - including obvious follow-up actions needed to complete the task properly.

README.ja.md

@@ -36,6 +36,14 @@ Codex、Claude Code、OpenCode向けのプロセス重視AIコーディング環
 
 > この文書は `README.md` の日本語訳です。正本は英語版です。
 
+## 現在の公開スコープ
+
+Codex と Claude Code が現在の first-class setup target です。OpenCode と OpenClaw は optional/reference surface として残し、互換性維持に役立つ場合だけ既存文書を参照します。これらをデフォルトのセットアップ経路として扱わないでください。
+
+## Private Project Skills
+
+auto-eva のような private project skill はこの public repository にコミットしません。実際のプロジェクト別 skill は、Codex 用の `~/.codex/skills` や Claude Code 用の `~/.claude/skills` などローカル runtime home に置きます。このリポジトリには templates and public-safe process guidance だけを置き、private access path、credential、auth state、browser profile、customer data、machine-specific trust setting は入れません。
+
 ## agent-bootstrap を使う理由
 
 - Codex、Claude Code、OpenCodeごとに別々のプロンプトスタックを管理せず、1つの `superpowers` ベースのワークフローを共有できます。

README.ko.md

@@ -36,6 +36,14 @@ Codex, Claude Code, OpenCode를 위한 프로세스 중심 AI 코딩 환경 부
 
 > 이 문서는 `README.md`의 한국어 번역본입니다. 기준 문서는 영어판입니다.
 
+## 현재 공개 범위
+
+Codex와 Claude Code가 현재 first-class setup target입니다. OpenCode와 OpenClaw는 optional/reference surface로 남겨 두며, 호환성 유지에 도움이 될 때만 기존 문서를 참고하고 기본 설정 경로로 취급하지 않습니다.
+
+## Private Project Skills
+
+auto-eva 같은 private project skill은 이 public repository에 커밋하지 않습니다. 실제 프로젝트별 skill은 Codex용 `~/.codex/skills`와 Claude Code용 `~/.claude/skills` 같은 로컬 runtime home에 둡니다. 이 레포에는 templates and public-safe process guidance만 남기고, private access path, credential, auth state, browser profile, customer data, machine-specific trust setting은 넣지 않습니다.
+
 ## 왜 agent-bootstrap을 써야 하나?
 
 - Codex, Claude Code, OpenCode 각각에 따로 프롬프트 스택을 유지하지 않고, 하나의 `superpowers` 기반 워크플로우를 공유할 수 있습니다.

README.md

@@ -34,6 +34,14 @@ Bootstrap a process-first AI coding environment for Codex, Claude Code, and Open
 
 `agent-bootstrap` gives you a shared `superpowers` workflow, role-based subagents, token-efficient execution, and multilingual setup docs for modern AI coding tools.
 
+## Current Public Focus
+
+Codex and Claude Code are the current first-class setup targets for this public repository. OpenCode and OpenClaw remain optional/reference surfaces: keep their existing docs only when they help preserve compatibility, but do not treat them as the default setup path.
+
+## Private Project Skills
+
+Do not commit private project skills such as auto-eva to this public repository. Keep actual project-specific skills in local runtime homes such as `~/.codex/skills` for Codex and `~/.claude/skills` for Claude Code. This repository should contain templates and public-safe process guidance, not private access paths, credentials, auth state, browser profiles, customer data, or machine-specific trust settings.
+
 ## Why use agent-bootstrap?
 
 - Shared `superpowers` workflow across Codex, Claude Code, and OpenCode instead of maintaining separate prompt stacks for each tool.
@@ -53,6 +61,7 @@ Use this repository as an operating guide, not only as an installer.
 - Install global defaults: use [docs/global-guardrail-setup.md](docs/global-guardrail-setup.md) to install the shared guardrails into Codex, Claude Code, or OpenCode user-level defaults.
 - Apply guardrails to a project: paste [prompts/apply-vibe-coding-guardrails.md](prompts/apply-vibe-coding-guardrails.md) into an agent session inside a target repository.
 - Start feature work inside a guarded project: paste [prompts/start-with-vibe-coding-guardrails.md](prompts/start-with-vibe-coding-guardrails.md) before asking for a feature, bugfix, or refactor.
+- Review optional Codex skills: read [skills/README.md](skills/README.md) and [docs/codex-skills.md](docs/codex-skills.md), then use [prompts/setup-codex-skills.md](prompts/setup-codex-skills.md) when you want an agent to browse, compare, and install approved skills.
 - Update this bootstrap after repository changes: paste [prompts/update-agent-bootstrap.md](prompts/update-agent-bootstrap.md) after pulling new changes or when you want an agent to re-audit this repository.
 - Explain this repository's own structure: read [docs/agent-bootstrap-structure.md](docs/agent-bootstrap-structure.md) before editing shared prompts, installers, generated plugin output, or setup docs.
 
@@ -123,6 +132,7 @@ Choose the scope first. Most failed agent setup work starts by configuring too m
 - `prompts/setup-claude-current-harness.md`: use inside Claude Code when the Claude plugin and shared role prompts should be set up.
 - `prompts/setup-opencode-current-harness.md`: use inside OpenCode when OpenCode should receive the generated agents and native plugin wiring.
 - `prompts/setup-shared-core.md`: use when the target environment is unclear and the safest answer is only the shared prompt/skills layer.
+- `prompts/setup-codex-skills.md`: use when you want an agent to inspect this repository's optional Codex skill catalog, compare selected skills with `~/.codex/skills`, and install only approved skills.
 - `prompts/apply-vibe-coding-guardrails.md`: use in an application repository that needs structure maps, edge-case-first tests, dependency-boundary checks, and local project knowledge.
 - `prompts/start-with-vibe-coding-guardrails.md`: use for day-to-day feature, bugfix, or refactor work after a repository already has a project map and guardrail workflow.
 - `prompts/update-agent-bootstrap.md`: use for this repository when new changes need to be pulled, rendered, installed, audited, documented, and reviewed.
@@ -203,6 +213,7 @@ These copy-paste prompts are the fastest way to keep another agent inside the in
 - Generic shared core setup: [prompts/setup-shared-core.md](prompts/setup-shared-core.md)
 - OpenClaw shared core only: [prompts/setup-openclaw-shared-core.md](prompts/setup-openclaw-shared-core.md)
 - OpenClaw ACP integration: [prompts/setup-openclaw-acp.md](prompts/setup-openclaw-acp.md)
+- Optional Codex skill catalog setup: [prompts/setup-codex-skills.md](prompts/setup-codex-skills.md)
 - Apply vibe-coding guardrails to another repository: [prompts/apply-vibe-coding-guardrails.md](prompts/apply-vibe-coding-guardrails.md)
 - Start work with vibe-coding guardrails: [prompts/start-with-vibe-coding-guardrails.md](prompts/start-with-vibe-coding-guardrails.md)
 - Update this bootstrap after repository changes: [prompts/update-agent-bootstrap.md](prompts/update-agent-bootstrap.md)
@@ -277,6 +288,8 @@ The intent is to reuse upstream `superpowers` instead of copying the skill libra
   - repository-level Claude marketplace entry
 - `plugins/process-first-agents/`
   - generated Claude plugin package
+- `skills/`
+  - optional Codex skill catalog; see [docs/codex-skills.md](docs/codex-skills.md)
 - `scripts/render_claude_plugin.py`
   - rebuilds the Claude plugin package from the shared prompt corpus
 - `docs/`

README.zh-CN.md

@@ -36,6 +36,14 @@
 
 > 本文档是 `README.md` 的简体中文翻译。以英文版为准。
 
+## 当前公开范围
+
+Codex 和 Claude Code 是当前 first-class setup target。OpenCode 和 OpenClaw 保持为 optional/reference surface；只有在需要兼容性说明时才参考现有文档，不要把它们当作默认设置路径。
+
+## Private Project Skills
+
+不要把 auto-eva 这类 private project skill 提交到这个 public repository。实际项目专用 skill 应放在本地 runtime home，例如 Codex 的 `~/.codex/skills` 和 Claude Code 的 `~/.claude/skills`。这个仓库只保留 templates and public-safe process guidance，不放 private access path、credential、auth state、browser profile、customer data 或 machine-specific trust setting。
+
 ## 为什么使用 agent-bootstrap？
 
 - 不需要为 Codex、Claude Code、OpenCode 分别维护不同的提示词栈，而是共享一套基于 `superpowers` 的工作流。

codex-home/AGENTS.md

@@ -25,6 +25,28 @@ Rule #1: If you want exception to ANY rule, YOU MUST STOP and get explicit permi
 - We discuss architectural decisions (framework changes, major refactoring, system design) together before implementation. Routine fixes and clear implementations don't need discussion.
 - You may use sub-agents or parallel agents for independent work without asking again each time when the current host/runtime provides the capability. This is a standing preference, not a requirement: use them when they create clear leverage, and stay local when they do not.
 
+## Access and approval boundary
+
+- Broad filesystem or tool access is operational capability, not blanket approval.
+- High-risk actions require an explicit stop and ask before proceeding.
+- High-risk actions include anything that would delete data, prune history, rotate credentials, change permissions, touch production, deployment, billing, external accounts, secrets, auth state, browser profiles, public sharing, protected branches, hooks, or test enforcement.
+- Use permission profiles, hooks, or approval layers when the current host/runtime supports them, but never treat those mechanisms as a replacement for judgment.
+
+## Source of truth and memory
+
+- Memory is a recall layer, not a source of truth.
+- When memory or prior summaries conflict with current evidence, repo docs, scripts, tests, AGENTS files, and observed runtime output win.
+- Project-specific operating knowledge belongs in project docs or project skills, with repo-local source-of-truth pointers when a skill is required.
+
+## Skill creation and QA
+
+- When creating or editing a skill, treat the skill as tested process code, not just prose.
+- Start with a failing test or explicit pressure scenario before writing the skill change when the host or repo can support it.
+- Keep skill bodies concise and move detailed procedures into reference files when that makes the trigger behavior clearer.
+- After skill edits, run the skill validator, run relevant repo tests, check for private paths and secrets, and inspect the rendered or installed result when applicable.
+- When a skill has both a repo catalog source and runtime copy, verify any runtime copy separately from the repo catalog source.
+- Do not claim a skill is ready only because the Markdown looks reasonable.
+
 # Proactiveness
 
 When asked to do something, just do it - including obvious follow-up actions needed to complete the task properly.

docs/agent-bootstrap-structure.md

@@ -47,6 +47,10 @@ Harness adapters translate the shared core into each host's native shape.
 - `plugins/process-first-agents/`
   - Generated Claude Code plugin package.
   - Built by `scripts/render_claude_plugin.py`.
+- `skills/`
+  - Optional Codex skill catalog.
+  - `skills/README.md` lists available catalog skills.
+  - Skill source directories such as `skills/chatgpt-collaboration-harness/` are reviewable catalog copies, not automatically installed runtime state.
 
 ## Generated Artifacts
 
@@ -76,6 +80,8 @@ python3 scripts/render_claude_plugin.py --partner-name "Hun"
 - Guardrail workflow explanation: `docs/vibe-coding-guardrails.md`.
 - Global installation and optional tooling rules: `docs/global-guardrail-setup.md`.
 - Project-local knowledge shape: `docs/local-project-knowledge-template.md`.
+- Optional Codex skill catalog workflow: `docs/codex-skills.md`.
+- Optional Codex skill setup prompt: `prompts/setup-codex-skills.md`.
 
 ## Dependency Direction
 
@@ -147,6 +153,7 @@ Check these areas carefully:
 - Claude renderer changes that silently accept unknown placeholders.
 - Docs that mention commands not implemented by this repository.
 - Optional tool docs that imply installation without user approval.
+- Skill catalog changes that confuse the repo catalog source with the runtime copy under `~/.codex/skills`.
 
 ## Privacy Boundary
 

docs/agent-setup-playbook.md

@@ -57,6 +57,7 @@ Choose the smallest valid scope that satisfies the user's request.
 | Harness is unclear | shared-core-only | Apply only shared operating guidance and ask before harness-specific setup. |
 | User points at an application repository | project guardrails | Add project-local knowledge guidance and repo-appropriate checks. Do not install global harness defaults unless requested. |
 | User says this repository was updated | agent-bootstrap maintenance | Read the structure doc, regenerate generated output when needed, verify tests and audit. |
+| User asks what Codex skills are available in this repository | skill catalog review | Read `skills/README.md` and `docs/codex-skills.md`. Compare selected skills with `~/.codex/skills`, then ask before installing or overwriting anything. |
 | User asks for OpenClaw ACP | explicit integration path | Follow OpenClaw docs. Do not infer provider, backend, or gateway choices. |
 
 When two valid scopes could apply, prefer the smaller one and explain what is intentionally left untouched.
@@ -196,6 +197,16 @@ python3 scripts/audit_agent_stack.py
 
 This writes user-level Codex defaults. Existing sessions may need a restart or a focused instruction to apply the new guardrails.
 
+### Optional Codex Skills
+
+Read:
+
+- `skills/README.md`
+- `docs/codex-skills.md`
+- `prompts/setup-codex-skills.md`
+
+This is a browse and selective install path, not a blanket installer. The repo copy is the catalog source, and the runtime copy lives under `~/.codex/skills/<skill-name>`. Ask before installing or overwriting any skill, then run the documented `quick_validate.py` validation path.
+
 ### Claude Code
 
 Read: