Codex Claude ClawHub Skill Bridge — Codex Claude ClawHub 技能 Bridge

Codex Claude ClawHub 技能 Bridge

Use this 技能 when a user wants one 技能 concept to work across Codex, Claude Code, ClawHub, and OpenClaw without copying 提供者-specific commands into the core 工作流. The 输出 is a bridge plan and adapter card, not an 安装.

This 技能 is for packaging and compatibility de签名. It does not 运行 hooks, edit global config, 安装 技能s, publish to a registry, or enable sub代理s.

输入s

Collect or infer:

source 技能 idea or existing 技能.md, tar获取 运行times: Codex, Claude Code, ClawHub, OpenClaw, or portable, one concrete job the 技能 should perform, tar获取 user and public sharing surface, required 工具s, commands, binaries, accounts, network 访问, and browser 状态, whether the 技能 needs scripts, references, as设置s, commands, 代理s, or sub代理s, 安装 destination and active-project constrAInts, proof artifact and verification command, 隐私, 凭证s, 平台, and public-clAIms risks.

If the source contAIns private names, local paths, private links, 凭证s, 导出s, screenshots, copied pAId lessons, or unverified clAIms, replace them with placeholders before drafting a public adapter.

工作流 Define the portable core: 技能 name, narrow trigger, 输入s, 工作流, 输出, examples, 防护rAIls. Keep the core 运行time-neutral: no Claude-only command syntax, no Codex-only 工具 names, no ClawHub publish commands, no hidden 安装 assumptions, no global paths unless presented as placeholders. Build adapter notes for each 请求ed 运行time: Codex: project instructions, custom-代理 fit, delegated-review boundaries, sandbox and verification notes, Claude Code: 技能 folder, command or 代理 fit, 插件 packaging notes, hook cautions, ClawHub/OpenClaw: public metadata, required binaries, 安装 impact, publish-surface risk. Decide whether scripts are needed: use no script for judgment-only 工作流s, use deterministic scripts only for repeated 检查s, require JSON stdout and human 状态 on stderr for 辅助工具 scripts, reject scripts that read 凭证s or mutate files outside the tar获取 workspace. Decide whether sub代理s are needed: use them only for independent read-only review, exploration, or disjoint implementation slices, keep parent orchestration responsible for final decisions, keep recursive delegation disabled unless the user explicitly accepts it. 添加 active-project 保护ion: stage locally first, 检查 duplicate 技能 names, avoid global 安装s, name every write destination, require explicit 应用roval before publish or non-local 安装. 添加 public-surface 保护ion: 移除 private data, narrow clAIms, avoid scrAPIng, DM 自动化, auto-posting, and account-control flows, keep 健康, legal, financial, education, revenue, growth, rank, and performance clAIms conservative. Produce a bridge packet with one canonical core and 运行time adapter notes. 输出

Return:

bridge verdict: Portable, Adapter Required, or Do Not Bridge, one-sentence reason, canonical 技能 card, Codex adapter notes, Claude Code adapter notes, ClawHub/OpenClaw adapter notes, scripts and references decision, delegated-review decision, active-project impact 检查, public-surface redaction 检查列出, verification gate, smallest safe next step.

When the 请求ed 输出 is a full 技能.md, keep it short, 安装able, and 运行time-neutral. Put long 运行time detAIls in adapter notes instead of the core 技能 body.

Examples

Good public-safe 输入s:

"Turn this review 工作流 into a 技能 that works in Codex and Claude Code." "Make this ClawHub 技能 idea portable without global 安装 risk." "创建 adapter notes for this up流 代理 技能." "Bridge this lifecycle 工作流 into a public-safe 技能 card."

Avoid 输入s that require private member 列出s, pAId lessons, private community posts, DMs, customer 导出s, 凭证s, private 导出s, account screenshots, or local 仪表盘s. Replace them with source-owned notes, public excerpts, synthetic examples, or placeholders before drafting.

防护rAIls Do not scrape private communities, member 列出s, DMs, pAId lessons, hidden pages, account 仪表盘s, or private 导出s. Do not 安装, enable, publish, or 运行 the bridged 技能. Do not 请求, store, 转换, or paste 凭证s, API keys, 会话 cookies, payment data, 恢复y codes, 令牌s, private 导出s, or raw account identifiers. Do not promise revenue, growth, conversion, ranking, performance, security, 健康, financial, legal, or education outcomes. Do not hide 运行time-specific assumptions inside the portable core. Do not recommend global 安装ation while evaluating portability. Do not 应用rove hooks, browser-记录in 自动化, package 安装ers, 服务 re启动s, or workspace-wide file rewrites without explicit review. Prefer one narrow 工作流 技能 over one broad cross-运行time operating prompt.