[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EZZBPHK9T4HGAEMRYFQP9C":3,"skill-same:01M7EZZBPHK9T4HGAEMRYFQP9C":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7EZZBPHK9T4HGAEMRYFQP9C","ecc-guide",null,"Answer questions about Everything Claude Code by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fecc-guide\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ecc-guide\ndescription: Answer questions about Everything Claude Code by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.\nmetadata:\n  origin: community\n---\n\n# ECC Guide\n\nUse this skill when a user needs help understanding, navigating, installing, or choosing parts of Everything Claude Code.\n\n## When To Use\n\nUse this skill when the user:\n\n- asks what ECC includes\n- wants help finding a skill, command, agent, hook, rule, or install profile\n- is new to the repository and needs a guided path\n- asks \"how do I do X with ECC?\"\n- asks which ECC components fit a project\n- needs a lightweight explanation of how commands, skills, agents, hooks, and rules relate\n- is confused by install paths, duplicate installs, reset\u002Funinstall, or selective install options\n\n## Core Principle\n\nAnswer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale.\n\nWhen the ECC repository is available, inspect the relevant files before giving a concrete answer:\n\n```bash\nnode scripts\u002Fci\u002Fcatalog.js --json\nfind skills -maxdepth 2 -name SKILL.md | sort\nfind commands -maxdepth 1 -name '*.md' | sort\nfind agents -maxdepth 1 -name '*.md' | sort\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --list-components --json\n```\n\nUse the smallest set of reads needed for the user's question.\n\n## Repository Map\n\n- `README.md`: install paths, uninstall\u002Freset guidance, public positioning, FAQs\n- `AGENTS.md`: contributor guidance and project structure\n- `agent.yaml`: exported gitagent surface and command list\n- `commands\u002F`: maintained slash-command compatibility shims\n- `skills\u002F*\u002FSKILL.md`: reusable workflows and domain playbooks\n- `agents\u002F*.md`: delegated subagent role prompts\n- `rules\u002F`: language and harness rules\n- `hooks\u002FREADME.md`, `hooks\u002Fhooks.json`, `scripts\u002Fhooks\u002F`: hook behavior and safety gates\n- `manifests\u002Finstall-*.json`: selective install modules, components, profiles, and target support\n- `docs\u002F`: harness guides, architecture notes, translated docs, release docs\n\n## Response Style\n\nLead with the answer, then give the next action. Most users do not need a full catalog dump.\n\nGood first response shape:\n\n1. what to use\n2. why it fits\n3. exact file or command to inspect\n4. one next command or question\n\nAvoid:\n\n- listing every skill or command by default\n- repeating large README sections\n- recommending retired command shims when a skill-first path exists\n- claiming a component exists without checking the filesystem\n- replacing install guidance with manual copy commands when the managed installer supports the target\n\n## Common Tasks\n\n### New User Onboarding\n\nGive a short menu:\n\n- install or reset ECC\n- pick skills for a project\n- understand commands vs skills\n- inspect hooks and safety behavior\n- run a harness audit\n- find a specific workflow\n\nPoint to `README.md` for install\u002Freset and `\u002Fproject-init` for project-specific onboarding.\n\n### Feature Discovery\n\nFor \"what should I use for X?\":\n\n1. Search `skills\u002F`, `commands\u002F`, and `agents\u002F`.\n2. Prefer skills as the primary workflow surface.\n3. Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior.\n4. Mention agents when delegation is useful.\n\nUseful searches:\n\n```bash\nrg -n \"\u003Cquery>\" skills commands agents docs\nfind skills -maxdepth 2 -name SKILL.md | sort\n```\n\n### Install Guidance\n\nUse managed install paths:\n\n```bash\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --profile minimal --target claude --json\nnode scripts\u002Finstall-apply.js --profile minimal --target claude --dry-run\n```\n\nFor specific skill installs:\n\n```bash\nnode scripts\u002Finstall-plan.js --skills \u003Cskill-id> --target claude --json\nnode scripts\u002Finstall-apply.js --skills \u003Cskill-id> --target claude --dry-run\n```\n\nWarn users not to stack plugin installs and full manual\u002Fprofile installs unless they intentionally want duplicate surfaces.\n\n### Project Onboarding\n\nUse `\u002Fproject-init` when the user wants ECC configured for a target repo. The expected sequence is:\n\n1. detect the stack from project files\n2. resolve a dry-run install plan\n3. inspect existing `CLAUDE.md` and settings files\n4. ask before applying changes\n5. keep generated guidance minimal and repo-specific\n\n### Troubleshooting\n\nAsk for the target harness and install path first, then inspect:\n\n- plugin install metadata\n- `.claude\u002F`, `.cursor\u002F`, `.codex\u002F`, `.gemini\u002F`, `.opencode\u002F`, `.codebuddy\u002F`, `.joycode\u002F`, or `.qwen\u002F`\n- `hooks\u002Fhooks.json`\n- install-state files\n- relevant command\u002Fskill files\n\nFor repo health, suggest:\n\n```bash\nnpm run harness:audit -- --format text\nnpm run observability:ready\nnpm test\n```\n\n## Output Templates\n\n### Short Recommendation\n\n```text\nUse \u003Cskill-or-command>. It fits because \u003Creason>.\n\nCanonical file: \u003Cpath>\nVerify with: \u003Ccommand>\nNext: \u003Cone concrete action>\n```\n\n### Search Results\n\n```text\nBest matches:\n- \u003Cpath>: \u003Cwhy it matters>\n- \u003Cpath>: \u003Cwhy it matters>\n\nRecommendation: \u003Cwhich one to use first and why>\n```\n\n### Install Plan Summary\n\n```text\nDetected: \u003Cstack evidence>\nTarget: \u003Charness>\nPlan: \u003Cprofile\u002Fmodules\u002Fskills>\nDry run: \u003Ccommand>\nWould change: \u003Cpaths>\nNeeds approval before apply: \u003Cyes\u002Fno>\n```\n\n## Related Surfaces\n\n- `\u002Fproject-init`: stack-aware onboarding plan for a target repo\n- `\u002Fharness-audit`: deterministic readiness scorecard\n- `\u002Fskill-health`: skill quality review\n- `\u002Fskill-create`: generate a new skill from local git history\n- `\u002Fsecurity-scan`: inspect Claude\u002FOpenCode configuration security\n","# ECC Guide\n\nUse this skill when a user needs help understanding, navigating, installing, or choosing parts of Everything Claude Code.\n\n## When To Use\n\nUse this skill when the user:\n\n- asks what ECC includes\n- wants help finding a skill, command, agent, hook, rule, or install profile\n- is new to the repository and needs a guided path\n- asks \"how do I do X with ECC?\"\n- asks which ECC components fit a project\n- needs a lightweight explanation of how commands, skills, agents, hooks, and rules relate\n- is confused by install paths, duplicate installs, reset\u002Funinstall, or selective install options\n\n## Core Principle\n\nAnswer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale.\n\nWhen the ECC repository is available, inspect the relevant files before giving a concrete answer:\n\n```bash\nnode scripts\u002Fci\u002Fcatalog.js --json\nfind skills -maxdepth 2 -name SKILL.md | sort\nfind commands -maxdepth 1 -name '*.md' | sort\nfind agents -maxdepth 1 -name '*.md' | sort\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --list-components --json\n```\n\nUse the smallest set of reads needed for the user's question.\n\n## Repository Map\n\n- `README.md`: install paths, uninstall\u002Freset guidance, public positioning, FAQs\n- `AGENTS.md`: contributor guidance and project structure\n- `agent.yaml`: exported gitagent surface and command list\n- `commands\u002F`: maintained slash-command compatibility shims\n- `skills\u002F*\u002FSKILL.md`: reusable workflows and domain playbooks\n- `agents\u002F*.md`: delegated subagent role prompts\n- `rules\u002F`: language and harness rules\n- `hooks\u002FREADME.md`, `hooks\u002Fhooks.json`, `scripts\u002Fhooks\u002F`: hook behavior and safety gates\n- `manifests\u002Finstall-*.json`: selective install modules, components, profiles, and target support\n- `docs\u002F`: harness guides, architecture notes, translated docs, release docs\n\n## Response Style\n\nLead with the answer, then give the next action. Most users do not need a full catalog dump.\n\nGood first response shape:\n\n1. what to use\n2. why it fits\n3. exact file or command to inspect\n4. one next command or question\n\nAvoid:\n\n- listing every skill or command by default\n- repeating large README sections\n- recommending retired command shims when a skill-first path exists\n- claiming a component exists without checking the filesystem\n- replacing install guidance with manual copy commands when the managed installer supports the target\n\n## Common Tasks\n\n### New User Onboarding\n\nGive a short menu:\n\n- install or reset ECC\n- pick skills for a project\n- understand commands vs skills\n- inspect hooks and safety behavior\n- run a harness audit\n- find a specific workflow\n\nPoint to `README.md` for install\u002Freset and `\u002Fproject-init` for project-specific onboarding.\n\n### Feature Discovery\n\nFor \"what should I use for X?\":\n\n1. Search `skills\u002F`, `commands\u002F`, and `agents\u002F`.\n2. Prefer skills as the primary workflow surface.\n3. Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior.\n4. Mention agents when delegation is useful.\n\nUseful searches:\n\n```bash\nrg -n \"\u003Cquery>\" skills commands agents docs\nfind skills -maxdepth 2 -name SKILL.md | sort\n```\n\n### Install Guidance\n\nUse managed install paths:\n\n```bash\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --profile minimal --target claude --json\nnode scripts\u002Finstall-apply.js --profile minimal --target claude --dry-run\n```\n\nFor specific skill installs:\n\n```bash\nnode scripts\u002Finstall-plan.js --skills \u003Cskill-id> --target claude --json\nnode scripts\u002Finstall-apply.js --skills \u003Cskill-id> --target claude --dry-run\n```\n\nWarn users not to stack plugin installs and full manual\u002Fprofile installs unless they intentionally want duplicate surfaces.\n\n### Project Onboarding\n\nUse `\u002Fproject-init` when the user wants ECC configured for a target repo. The expected sequence is:\n\n1. detect the stack from project files\n2. resolve a dry-run install plan\n3. inspect existing `CLAUDE.md` and settings files\n4. ask before applying changes\n5. keep generated guidance minimal and repo-specific\n\n### Troubleshooting\n\nAsk for the target harness and install path first, then inspect:\n\n- plugin install metadata\n- `.claude\u002F`, `.cursor\u002F`, `.codex\u002F`, `.gemini\u002F`, `.opencode\u002F`, `.codebuddy\u002F`, `.joycode\u002F`, or `.qwen\u002F`\n- `hooks\u002Fhooks.json`\n- install-state files\n- relevant command\u002Fskill files\n\nFor repo health, suggest:\n\n```bash\nnpm run harness:audit -- --format text\nnpm run observability:ready\nnpm test\n```\n\n## Output Templates\n\n### Short Recommendation\n\n```text\nUse \u003Cskill-or-command>. It fits because \u003Creason>.\n\nCanonical file: \u003Cpath>\nVerify with: \u003Ccommand>\nNext: \u003Cone concrete action>\n```\n\n### Search Results\n\n```text\nBest matches:\n- \u003Cpath>: \u003Cwhy it matters>\n- \u003Cpath>: \u003Cwhy it matters>\n\nRecommendation: \u003Cwhich one to use first and why>\n```\n\n### Install Plan Summary\n\n```text\nDetected: \u003Cstack evidence>\nTarget: \u003Charness>\nPlan: \u003Cprofile\u002Fmodules\u002Fskills>\nDry run: \u003Ccommand>\nWould change: \u003Cpaths>\nNeeds approval before apply: \u003Cyes\u002Fno>\n```\n\n## Related Surfaces\n\n- `\u002Fproject-init`: stack-aware onboarding plan for a target repo\n- `\u002Fharness-audit`: deterministic readiness scorecard\n- `\u002Fskill-health`: skill quality review\n- `\u002Fskill-create`: generate a new skill from local git history\n- `\u002Fsecurity-scan`: inspect Claude\u002FOpenCode configuration security\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fecc\u002Fecc-guide","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ecc-guide",{"tool":38,"command":39},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ecc-guide",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ecc-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fecc-guide\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]