跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 configure-ecc

Configure Ecc

在当前吊带内运行对话式ECC设置向导:盘点安装,收集范围(用户/项目/局部)和Claude Code中的钩子模式(off/minmal/standard/strict),使用Codex的本地插件生命周期,或者在./.kimi-code下安装工程表面,然后预览,应用,并验证. 在安装,更新,再配置,或修复ECC安装,改变钩子配置,或在安装范围之间移动ECC时使用.

12448 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

在当前带内运行对话式ECC设置向导:将安装、收集范围(用户/项目/局部)和钩子模式(关闭/最小/标准/限制)记录在克洛德码中,使用Codex的本地插件生命周期,或在./.kimi-code下安装工程表面,然后进行预览、应用和验证

何时用

安装、更新、再配置或修理ECC安装、改变钩子配置或安装范围之间移动ECC

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Configure Everything Claude Code、Route by the current harness、Claude Code: run the full conversational wizard、1. Inventory without changing anything、2. Collect exactly two choices、3. Preview and confirm once。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/setup.js、scripts/lib/terminal-welcome.js、scripts/lib/terminal-welcome、scripts/welcome.js,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.

Configure Everything Claude CodeRoute by the current harnessClaude Code: run the full conversational wizard1. Inventory without changing anything2. Collect exactly two choices3. Preview and confirm once4. Apply the explicit choices5. Verify, then render the welcomeCodex: use the native plugin lifecycleKimi: install the project surface

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
configure-ecc
description
Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 4
  • scripts/setup.js
  • scripts/lib/terminal-welcome.js
  • scripts/lib/terminal-welcome
  • scripts/welcome.js

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「configure-ecc」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c38746603bfdc852-%E9%85%8D%E7%BD%AE-Ecc.html
请存为 .cursor/skills/configure-ecc/SKILL.md 或 .claude/skills/configure-ecc/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/affaan-m/ecc 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/affaan-m/ecc' --list

npx skills add 'https://github.com/affaan-m/ecc' --skill 'configure-ecc'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: configure-ecc description: "Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes." metadata: origin: ECC --- # Configure Everything Claude Code Run a conversational wizard inside the current harness. Inventory first, collect only supported choices, preview, confirm once, apply non-interactively, verify, and show the welcome only after success. Never clone ECC into a temporary directory or copy plugin components by hand. For a human-operated terminal, the canonical entry points are `ecc setup` and `npx ecc-universal setup`. Inside a harness, use the explicit non-interactive commands below instead. ## Route by the current harness - In Claude Code, use the full scope-and-hook wizard below. - In Codex, use Codex's native plugin lifecycle. Do not offer Claude scopes or map ECC's four Claude hook profiles onto Codex. - In Kimi, install the project surface under `./.kimi-code`. Kimi does not provide ECC's Claude lifecycle-hook profiles. - If the harness is uncertain, state the detected evidence and ask which harness to configure before running a mutating command. This skill is a post-install reconfiguration path. It cannot intercept or replace a provider's built-in first-install UI. ## Claude Code: run the full conversational wizard ### 1. Inventory without changing anything Run both commands and summarize the installed ECC scope, enabled state, and marketplace source: ```bash claude plugin list --json claude plugin marketplace list --json ``` Treat a single existing `ecc@ecc` installation as a reconfiguration. Do not interpret Claude's provider-owned "Open home page" control as installation evidence. Stop and report the recovery returned by setup for multiple ECC scopes, a legacy/manual install, malformed settings, or a marketplace collision; never guess which state to delete. ### 2. Collect exactly two choices Ask exactly one scope question and require one value: - `user | project | local` - `user` is global for this user. - `project` is shared through repository settings. - `local` is private to the current project. Visually mark only the selected scope as selected or installing. If the user chooses a different scope from a single existing install, describe it as a scope migration and include `--move-scope` in the commands below. Ask exactly one hook-mode question and require one value: - `off | minimal | standard | strict` - `off` keeps skills and commands but disables ECC hook automation. - `minimal` enables the lightest lifecycle and safety automation. - `standard` balances quality and safety automation. - `strict` enables the strongest checks and reminders. Hook preference is personal Claude plugin configuration; it does not follow the selected install scope. ### 3. Preview and confirm once Prefer the plugin-bundled setup script. Substitute the two selected values and include `--move-scope` only for a scope migration: ```bash node "$CLAUDE_PLUGIN_ROOT/scripts/setup.js" --mode claude-plugin \ --scope --hooks [--move-scope] --dry-run --json ``` If `$CLAUDE_PLUGIN_ROOT` is unavailable, use the published npm package: ```bash npx --yes --package ecc-universal ecc setup --mode claude-plugin \ --scope --hooks [--move-scope] --dry-run --json ``` Show exactly one confirmation summary containing the planned action, one scope, one hook mode, marketplace action, and any source-to-destination migration. Ask one yes/no question. Do not run a bare interactive `ecc setup` through a harness shell tool because that shell is commonly non-TTY. ### 4. Apply the explicit choices After confirmation, rerun the same route without `--dry-run`. Keep every choice explicit and request JSON so success can be checked deterministically: ```bash node "$CLAUDE_PLUGIN_ROOT/scripts/setup.js" --mode claude-plugin \ --scope --hooks [--move-scope] --yes --json ``` Fallback: ```bash npx --yes --package ecc-universal ecc setup --mode claude-plugin \ --scope --hooks [--move-scope] --yes --json ``` ### 5. Verify, then render the welcome Require a zero exit status and a setup result whose `scope` and `hooks` equal the selected values. Then independently run: ```bash claude plugin list --json ``` Continue only when exactly one enabled `ecc@ecc` entry exists at the selected scope. When `$CLAUDE_PLUGIN_ROOT` is available, pass the successful setup `action` (`installed`, `updated`, `migrated`, `resumed`, or `already-migrated`) to the bundled renderer: Before invoking it, require the provider-reported version to match `ECC_VERSION_PATTERN` from `scripts/lib/terminal-welcome.js`. Reject unexpected version text instead of interpolating it into a shell command. ```bash node -e 'const { renderTerminalWelcome } = require(process.env.CLAUDE_PLUGIN_ROOT + "/scripts/lib/terminal-welcome"); process.stdout.write(renderTerminalWelcome({ action: process.argv[1], version: process.argv[2], color: process.stdout.isTTY }));' "" "" ``` Render the welcome exactly once. On failure, dry-run, cancellation, a scope or hook mismatch, or unverifiable state, do not render it; report the error and recovery instead. After verified changes, tell the user to run `/reload-plugins` or restart Claude Code. ## Codex: use the native plugin lifecycle Inventory with `codex plugin marketplace list --json` and `codex plugin list --available --json`. Codex's native plugin command has no Claude-style `user | project | local` selector. Codex native plugins do support provider-specific hooks, but Codex requires explicit trust for them. Let Codex show that trust decision; do not ask the Claude four-profile hook question or claim those profiles map to Codex. If the ECC marketplace is missing, add it. Otherwise refresh its snapshot: ```bash codex plugin marketplace add affaan-m/ECC codex plugin marketplace upgrade ecc --json ``` Ask for one confirmation, then install or idempotently refresh the installed cache and verify it: ```bash codex plugin add ecc@ecc --json codex plugin list --json ``` Continue only when the JSON reports ECC installed and provides its `installedPath`. Then render the verified bundle's welcome: Use only the exact absolute `installedPath` returned by Codex JSON. Reject control characters and require the installed version to match `ECC_VERSION_PATTERN`. Invoke `node` directly with this argument array; this is a tool API invocation, not a shell command: ```text ["/scripts/welcome.js", "--action", "configured", "--version", ""] ``` If the current harness cannot invoke an executable with a separate argument array, skip the welcome. Never construct a shell command from Codex JSON values. Never claim that Claude's `off | minimal | standard | strict` profiles were applied to Codex. ## Kimi: install the project surface State the capability summary before confirmation: destination `./.kimi-code`; `hooks=unsupported` for ECC lifecycle hooks. Do not ask the Claude scope or hook-mode questions. Preview first: ```bash npx --yes --package ecc-universal ecc install --profile core --target kimi --dry-run ``` Show one confirmation for that project destination, then apply the identical command without `--dry-run`. Verify with: ```bash npx --yes --package ecc-universal ecc doctor --target kimi ``` Only after doctor succeeds and the installed instructions and skills remain inside `./.kimi-code`, render: ```bash npx --yes --package ecc-universal ecc welcome --action configured ``` Do not claim that Kimi installed or configured ECC lifecycle hooks.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…