菜单
构建、说明、迁移、评审或验证 Anybox 插件包及其 .anybox-plugin/plugin.json 清单。适用于 Codex 需要创建或更新插件目录、MCP Server、内置 Skill、插件自有 API Key 或 OAuth Connector、平台 Connector 依赖、外部组件 JSON、Registry 条目、ZIP 或 GitHub Tree 分发、生成 ID，或诊断 Anybox 插件目录与安装问题。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Control approved Windows app windows through the plugin-owned sky API in Anybox Node REPL.
Control the user's Chrome browser through a persistent Node REPL when tasks depend on existing tabs, signed-in sessions, extensions, visible page state, or UI interaction. Prefer purpose-built connectors, APIs, or CLIs for semantic resource operations.
Use for new frontend applications, dashboards, games, creative websites, hero sections, and visually driven UI from scratch, or when the user explicitly asks for a redesign/restyle/modernization. Builds from clean, airy, high-taste, readable image-generated concept design with section-specific references, faithful implementation, and browser testing.
Use when testing, debugging, or making targeted improvements to rendered frontend apps through the Build Web Apps or web dev plugin: local dev servers, UI regressions, interaction bugs, console errors, responsive layout, and visual QA. Check whether the Chrome plugin is available and use it first when it is; otherwise use regular Playwright with the recorded reason.
Build, explain, review, or validate current Anybox/Fanfande-derived plugin packages. Use when the user asks how to structure a plugin folder, write the canonical .anybox-plugin/plugin.json manifest, add plugin MCP servers, bundle plugin skills, define app connectors or connector requirements, create plugin registry manifests, migrate away from plugin.meta.json or zip artifacts, or check whether a plugin package matches the current plugin system.
Prepare, verify, and publish the Anybox Mobile Android app release from the Anybox monorepo using the mobile-v* GitHub Releases flow. Use when the user asks to release, package, publish, update, or document the Anybox mobile/iPad/Android client, create mobile GitHub release assets, bump mobile versionCode/version, or avoid desktop releases interfering with mobile updates.
| name | anybox-plugin |
| description | 构建、说明、迁移、评审或验证 Anybox 插件包及其 .anybox-plugin/plugin.json 清单。适用于 Codex 需要创建或更新插件目录、MCP Server、内置 Skill、插件自有 API Key 或 OAuth Connector、平台 Connector 依赖、外部组件 JSON、Registry 条目、ZIP 或 GitHub Tree 分发、生成 ID，或诊断 Anybox 插件目录与安装问题。 |
使用当前 Anybox 运行时格式。不要把历史 Fanfande 格式或旧的 fanfande-plugin-structure Skill 当作权威规范。
做出重要的插件格式判断前，按以下顺序检查目标仓库中的实时内容：
packages/anyboxagent/src/plugin/plugin.tspackages/anyboxagent/Test/plugin.test.tspackages/anyboxagent/src/connector/connector.tsplugins/Anybox-Plugins/index.json.anybox-plugin/plugin.json 示例plugins/Anybox-Plugins/anybox-plugin-development/docs/anybox-third-party-plugin-development.md运行代码优先于测试，测试优先于说明文档，目标仓库优先于既有假设。如果实时解析器与本 Skill 不一致，遵循解析器并报告规范漂移。除非用户明确要求修改插件格式本身，否则不要为了让某个插件通过而修改解析器。
面对范围很窄的问题时，不要加载无关参考文档。
.anybox-plugin 视为元数据目录，而不是包根目录。<plugin-root>/.anybox-plugin/plugin.json 创建或更新规范清单。scripts、skills、connectors、docs 和 assets 放在 .anybox-plugin 同级。.anybox-plugin/plugin.json。plugin.json 和 .codex-plugin/plugin.json 当作兼容输入。.fanfande-plugin/plugin.json 或 plugin.meta.json。name 生成插件 ID，并让文件夹、manifest 名称和 Registry 路径保持一致。connectors[].id；把 connectorID 和 appID 视为兼容别名。credential 和 runtime；configFields 只能作为额外配置。connectors，不要为新插件使用旧的 apps 字段。commands 和 agents 视为保留兼容字段，不要声称当前运行时会执行它们。critical。评审时把发现分为：
为重要结论指出对应的实时来源。如果没有运行验证，必须明确说明。