[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77NK94MH71PDCTVE596CAEP":3,"skill-same:01M77NK94MH71PDCTVE596CAEP":128},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M77NK94MH71PDCTVE596CAEP","ce-setup",null,"Check RocketClaw's tools and repo config and fix what it finds, scaffold a Compound Pack with `pack:\u003Cid>`, or draft and refresh coding standards and review docs from pull request history. Use when setting up or diagnosing RocketClaw, or when creating or updating CODING_STANDARDS.md or REVIEW.md, including on a schedule.","ucirello\u002Fcompound-engineering-plugin","ucirello","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F138827?v=4","01M77NFWYZ15SBS6EHVHBDDNA6","U Cirello","01M77NFWZJS5P3EKSVVKR8K5G9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ce-setup\ndescription: \"Check RocketClaw's tools and repo config and fix what it finds, scaffold a Compound Pack with `pack:\u003Cid>`, or draft and refresh coding standards and review docs from pull request history. Use when setting up or diagnosing RocketClaw, or when creating or updating CODING_STANDARDS.md or REVIEW.md, including on a schedule.\"\nargument-hint: \"[pack:\u003Cid> | standards] [mode:non-interactive]\"\n---\n\n# RocketClaw Setup\n\n## OpenCode V2 installation prerequisite\n\nDocument this action for the user; do not edit host\u002Fglobal configuration or a consuming project's OpenCode files. Ask the user to merge `\"experimental\": { \"subagent_depth\": 3 }` into `~\u002F.config\u002Fopencode\u002Fopencode.json`. Use `opencode debug paths` or `opencode debug paths config` to locate the actual global configuration directory when different, and update its existing `opencode.json` or `opencode.jsonc`; never create a competing JSON\u002FJSONC file or replace the entire file. Preserve unrelated settings, sibling experimental fields, and any existing integer depth higher than 3. Deep agentic delegation requires depth at least 3. Installing the plugin or shipping package-local `opencode.json` does not merge that configuration into consumers, and higher-precedence configuration must not lower the effective depth below 3.\n\nConfigured peer\u002Fmodel choices, tiers, and effort remain authoritative intent. Execute routes using native `opencode.models` discovery and native subagents\u002Fshell, not another harness dispatcher or acpx. Preserve compatibility examples and provider references as configuration vocabulary, not executable cross-harness routes. Skill-requested delegation satisfies a host user-or-skill permission rule, but never an unconditional prohibition. Delegation permission, model-override permission, and remaining nesting depth are separate: inherit the model when overrides are forbidden, classify actual dispatch errors, and report unavailable required model independence or coverage as incomplete rather than claiming success. Never bypass a denial or depth limit through another harness.\n\nRun JJ from the target workspace's absolute root. For repository-scoped GitHub CLI commands use `(cd \"$workspace_root\" && GIT_DIR=$(jj git root) gh ...)`. Store all temporary data under that root's ignored `.tmp\u002F`. JJ reference: https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fcli-reference\u002F .\n\n## Non-interactive runs\n\nRun non-interactively when the arguments contain `mode:non-interactive`, or when the request makes unattended intent unmistakable, such as a scheduled or CI job, or a caller asking for a run \"headless\", \"unattended\", or \"without questions\". \"Automatically\" alone is not that signal: it says when setup runs, not whether anyone can answer. When the signal is absent or unclear, run interactively. Strip the token before reading the rest of the arguments. A non-interactive run asks nothing and follows `references\u002Fnon-interactive.md`, which replaces every offer, question, and approval in this file and its references.\n\n## Interaction Method\n\nIn an interactive run, ask each question below with the host's blocking question tool, and never silently skip or auto-configure. Read `references\u002Fcommunication.md` from this skill's directory before your first offer. It says how to reach that tool and what each offer, question, and preview must tell the user.\n\n## Pack Scaffold\n\nWhen the invocation names a Compound Pack to add, create, or scaffold (the `pack:\u003Cid>` argument, or the same request in words), read `references\u002Fpack-scaffold.md` from this skill's directory and follow it in place of Phases 1-2: it writes the pack and its config entry only after the user approves, runs the health check itself, and reports into Phase 3 (Summary).\n\n## Review Docs\n\nWhen the invocation asks to draft, refresh, or update coding standards or review docs (the `standards` argument, or the same request in words), read `references\u002Fproject-docs.md` and follow it in place of Phases 1-2, drafting the whole set of files even when the request names one. Report into Phase 3.\n\n## Artifact Root Resolution\n\nEvery RocketClaw skill that reads or writes an artifact tree (`solutions`, `plans`, and others) resolves its root by this rule. Step 2 reports the resolved root.\n\n\u003C!-- ce-docs-root:start -->\n**Resolve the artifact root `\u003Croot>` before composing any artifact path.**\n\n- **Read** `docs_root` from `\u003Crepo-root>\u002F.rocketclaw\u002Fconfig.yaml` only (`\u003Crepo-root>` = `jj workspace root`). Do not read it from `config.local.yaml`. Unset -> `\u003Croot>` is `docs`, exactly as before.\n- **Validate** a set value: a repo-relative directory whose real, symlink-resolved path stays inside the repo and is neither the repo root nor under `.git\u002F`. Otherwise stop with an error naming `docs_root` and the value -- never fall back to `docs`.\n- **Use** `\u003Croot>` as the sole artifact location: create it if absent, compose each path as `\u003Croot>\u002F\u003Csubdir>` with this skill's own subdirectory, and never also read `docs`.\n\u003C!-- ce-docs-root:end -->\n\n## Phase 1: Diagnose\n\n### Step 1: Determine Plugin Version\n\nDetect the installed RocketClaw plugin version by reading the plugin metadata or manifest when the platform exposes it. If the version cannot be determined, skip this step.\n\nIf a version is found, pass it to the check script via `--version`. Otherwise omit the flag.\n\n### Step 2: Run the Health Check\n\nBefore running the script, display:\n\n```text\nRocketClaw -- checking your environment...\n```\n\nRun the bundled check script. Set `SKILL_DIR` to the absolute directory you loaded this `ce-setup` SKILL.md from — the Bash tool's CWD is the user's project, not the skill dir, so a bare `scripts\u002F` path will not resolve:\n\n```bash\nSKILL_DIR=\"\u003Cabsolute path of the directory containing this SKILL.md>\";\nif [ -f \"$SKILL_DIR\u002Fscripts\u002Fcheck-health\" ]; then bash \"$SKILL_DIR\u002Fscripts\u002Fcheck-health\" --version VERSION; else echo \"Bundled health script not found at $SKILL_DIR\u002Fscripts\u002Fcheck-health; run the inline checks from ce-setup instead.\"; fi\n```\n\nUse the same command without `--version VERSION` if Step 1 could not determine a version.\n\nIf the script is unavailable, run the inline equivalent listed in `references\u002Frepo-fixes.md`.\n\nDisplay the diagnostic output to the user. The health report includes the resolved artifact root and which config layer supplied it (per Artifact Root Resolution above); show that line so the operator can confirm where artifacts will be written. Missing `config.yaml` is a reported absence, not a project issue.\n\n### Step 3: Decide Whether Fixes Are Needed\n\nRepo-local fixes the health report names apply only to the checkout that report diagnosed. If Phase 2 will write to a different writable checkout, diagnose that checkout first. Session-level findings such as plugin version and optional tools still come from this session's Phase 1.\n\nAfter the health report, decide Phase 2 from writable-checkout availability:\n\n- If this session has a writable JJ workspace, run Phase 2 locally, including when `project_issues` is 0. Phase 2 always refreshes the example and always offers to create `config.yaml` when that file is missing.\n- If this session has no writable checkout, but the user named a repository and the harness exposes a remote repo-work surface with a writable checkout, run Phase 2 on that surface instead and report the remote repo-local fixes in Phase 3.\n- Otherwise skip Phase 2 and go to Phase 3, saying repo-local writes were skipped because no writable checkout is available.\n\nTwo offers concern this machine rather than the checkout, so they stand whether or not Phase 2 runs. If the report names a legacy Compound Codex tool map, offer to remove it following `references\u002Flegacy-codex-tool-map.md` from this skill's directory. Optional compatibility package-cache maintenance is described in `references\u002Facpx-cache-warm.md`; it is not the active OpenCode peer execution path.\n\nPhase 2 remediates every project issue the report names, each in its own step of `references\u002Frepo-fixes.md`. That includes an out-of-date `config.yaml`, retired config keys, a `ce-work` implementation engine the report marks unavailable or invalid, and malformed dormant `work_engine_preferences` or `work_engine_effort`.\n\n## Phase 2: Fix Repo-Local Issues\n\nRead `references\u002Frepo-fixes.md` from this skill's directory before making any repo-local change. It remediates every project issue the report names and carries Steps 4-10: removing the obsolete `rocketclaw.local.md`, refreshing the example config, refreshing out-of-date config files with their settings kept, offering to create `config.yaml`, repairing invalid `work_engine_preferences` and `docs_root`, the two `.gitignore` offers, and the agent-instructions offers (a knowledge-store mention, the compounding directive, and the chat-register directive for `ce-noslop`), and the offer to draft the project's review docs.\n\nEvery change to a user-owned file is offered and applied only if the user approves.\n\n## Phase 3: Summary\n\n**User-runnable invocation rendering.** In setup summaries, default to `\u002Fce-setup` and `\u002Fce-help`; use `$ce-setup` and `$ce-help` only when the active host is Codex or explicitly documents dollar-prefixed skill invocation. On oh-my-pi (`omp`), keep `\u002Fce-setup` and use `\u002Fskill:ce-help`. Render only the invocation as inline code and output one form only.\n\nWrite the summary that `references\u002Fsummary.md` describes. End it with these two lines, with the rendered invocations filled in:\n\n```text\nRun `\u003Crendered invocation>` anytime to re-check.\nRun `\u003Crendered ce-help invocation>` to ask which skill fits or what comes next.\n```\n","# RocketClaw Setup\n\n## OpenCode V2 installation prerequisite\n\nDocument this action for the user; do not edit host\u002Fglobal configuration or a consuming project's OpenCode files. Ask the user to merge `\"experimental\": { \"subagent_depth\": 3 }` into `~\u002F.config\u002Fopencode\u002Fopencode.json`. Use `opencode debug paths` or `opencode debug paths config` to locate the actual global configuration directory when different, and update its existing `opencode.json` or `opencode.jsonc`; never create a competing JSON\u002FJSONC file or replace the entire file. Preserve unrelated settings, sibling experimental fields, and any existing integer depth higher than 3. Deep agentic delegation requires depth at least 3. Installing the plugin or shipping package-local `opencode.json` does not merge that configuration into consumers, and higher-precedence configuration must not lower the effective depth below 3.\n\nConfigured peer\u002Fmodel choices, tiers, and effort remain authoritative intent. Execute routes using native `opencode.models` discovery and native subagents\u002Fshell, not another harness dispatcher or acpx. Preserve compatibility examples and provider references as configuration vocabulary, not executable cross-harness routes. Skill-requested delegation satisfies a host user-or-skill permission rule, but never an unconditional prohibition. Delegation permission, model-override permission, and remaining nesting depth are separate: inherit the model when overrides are forbidden, classify actual dispatch errors, and report unavailable required model independence or coverage as incomplete rather than claiming success. Never bypass a denial or depth limit through another harness.\n\nRun JJ from the target workspace's absolute root. For repository-scoped GitHub CLI commands use `(cd \"$workspace_root\" && GIT_DIR=$(jj git root) gh ...)`. Store all temporary data under that root's ignored `.tmp\u002F`. JJ reference: https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fcli-reference\u002F .\n\n## Non-interactive runs\n\nRun non-interactively when the arguments contain `mode:non-interactive`, or when the request makes unattended intent unmistakable, such as a scheduled or CI job, or a caller asking for a run \"headless\", \"unattended\", or \"without questions\". \"Automatically\" alone is not that signal: it says when setup runs, not whether anyone can answer. When the signal is absent or unclear, run interactively. Strip the token before reading the rest of the arguments. A non-interactive run asks nothing and follows `references\u002Fnon-interactive.md`, which replaces every offer, question, and approval in this file and its references.\n\n## Interaction Method\n\nIn an interactive run, ask each question below with the host's blocking question tool, and never silently skip or auto-configure. Read `references\u002Fcommunication.md` from this skill's directory before your first offer. It says how to reach that tool and what each offer, question, and preview must tell the user.\n\n## Pack Scaffold\n\nWhen the invocation names a Compound Pack to add, create, or scaffold (the `pack:\u003Cid>` argument, or the same request in words), read `references\u002Fpack-scaffold.md` from this skill's directory and follow it in place of Phases 1-2: it writes the pack and its config entry only after the user approves, runs the health check itself, and reports into Phase 3 (Summary).\n\n## Review Docs\n\nWhen the invocation asks to draft, refresh, or update coding standards or review docs (the `standards` argument, or the same request in words), read `references\u002Fproject-docs.md` and follow it in place of Phases 1-2, drafting the whole set of files even when the request names one. Report into Phase 3.\n\n## Artifact Root Resolution\n\nEvery RocketClaw skill that reads or writes an artifact tree (`solutions`, `plans`, and others) resolves its root by this rule. Step 2 reports the resolved root.\n\n\u003C!-- ce-docs-root:start -->\n**Resolve the artifact root `\u003Croot>` before composing any artifact path.**\n\n- **Read** `docs_root` from `\u003Crepo-root>\u002F.rocketclaw\u002Fconfig.yaml` only (`\u003Crepo-root>` = `jj workspace root`). Do not read it from `config.local.yaml`. Unset -> `\u003Croot>` is `docs`, exactly as before.\n- **Validate** a set value: a repo-relative directory whose real, symlink-resolved path stays inside the repo and is neither the repo root nor under `.git\u002F`. Otherwise stop with an error naming `docs_root` and the value -- never fall back to `docs`.\n- **Use** `\u003Croot>` as the sole artifact location: create it if absent, compose each path as `\u003Croot>\u002F\u003Csubdir>` with this skill's own subdirectory, and never also read `docs`.\n\u003C!-- ce-docs-root:end -->\n\n## Phase 1: Diagnose\n\n### Step 1: Determine Plugin Version\n\nDetect the installed RocketClaw plugin version by reading the plugin metadata or manifest when the platform exposes it. If the version cannot be determined, skip this step.\n\nIf a version is found, pass it to the check script via `--version`. Otherwise omit the flag.\n\n### Step 2: Run the Health Check\n\nBefore running the script, display:\n\n```text\nRocketClaw -- checking your environment...\n```\n\nRun the bundled check script. Set `SKILL_DIR` to the absolute directory you loaded this `ce-setup` SKILL.md from — the Bash tool's CWD is the user's project, not the skill dir, so a bare `scripts\u002F` path will not resolve:\n\n```bash\nSKILL_DIR=\"\u003Cabsolute path of the directory containing this SKILL.md>\";\nif [ -f \"$SKILL_DIR\u002Fscripts\u002Fcheck-health\" ]; then bash \"$SKILL_DIR\u002Fscripts\u002Fcheck-health\" --version VERSION; else echo \"Bundled health script not found at $SKILL_DIR\u002Fscripts\u002Fcheck-health; run the inline checks from ce-setup instead.\"; fi\n```\n\nUse the same command without `--version VERSION` if Step 1 could not determine a version.\n\nIf the script is unavailable, run the inline equivalent listed in `references\u002Frepo-fixes.md`.\n\nDisplay the diagnostic output to the user. The health report includes the resolved artifact root and which config layer supplied it (per Artifact Root Resolution above); show that line so the operator can confirm where artifacts will be written. Missing `config.yaml` is a reported absence, not a project issue.\n\n### Step 3: Decide Whether Fixes Are Needed\n\nRepo-local fixes the health report names apply only to the checkout that report diagnosed. If Phase 2 will write to a different writable checkout, diagnose that checkout first. Session-level findings such as plugin version and optional tools still come from this session's Phase 1.\n\nAfter the health report, decide Phase 2 from writable-checkout availability:\n\n- If this session has a writable JJ workspace, run Phase 2 locally, including when `project_issues` is 0. Phase 2 always refreshes the example and always offers to create `config.yaml` when that file is missing.\n- If this session has no writable checkout, but the user named a repository and the harness exposes a remote repo-work surface with a writable checkout, run Phase 2 on that surface instead and report the remote repo-local fixes in Phase 3.\n- Otherwise skip Phase 2 and go to Phase 3, saying repo-local writes were skipped because no writable checkout is available.\n\nTwo offers concern this machine rather than the checkout, so they stand whether or not Phase 2 runs. If the report names a legacy Compound Codex tool map, offer to remove it following `references\u002Flegacy-codex-tool-map.md` from this skill's directory. Optional compatibility package-cache maintenance is described in `references\u002Facpx-cache-warm.md`; it is not the active OpenCode peer execution path.\n\nPhase 2 remediates every project issue the report names, each in its own step of `references\u002Frepo-fixes.md`. That includes an out-of-date `config.yaml`, retired config keys, a `ce-work` implementation engine the report marks unavailable or invalid, and malformed dormant `work_engine_preferences` or `work_engine_effort`.\n\n## Phase 2: Fix Repo-Local Issues\n\nRead `references\u002Frepo-fixes.md` from this skill's directory before making any repo-local change. It remediates every project issue the report names and carries Steps 4-10: removing the obsolete `rocketclaw.local.md`, refreshing the example config, refreshing out-of-date config files with their settings kept, offering to create `config.yaml`, repairing invalid `work_engine_preferences` and `docs_root`, the two `.gitignore` offers, and the agent-instructions offers (a knowledge-store mention, the compounding directive, and the chat-register directive for `ce-noslop`), and the offer to draft the project's review docs.\n\nEvery change to a user-owned file is offered and applied only if the user approves.\n\n## Phase 3: Summary\n\n**User-runnable invocation rendering.** In setup summaries, default to `\u002Fce-setup` and `\u002Fce-help`; use `$ce-setup` and `$ce-help` only when the active host is Codex or explicitly documents dollar-prefixed skill invocation. On oh-my-pi (`omp`), keep `\u002Fce-setup` and use `\u002Fskill:ce-help`. Render only the invocation as inline code and output one form only.\n\nWrite the summary that `references\u002Fsummary.md` describes. End it with these two lines, with the rendered invocations filled in:\n\n```text\nRun `\u003Crendered invocation>` anytime to re-check.\nRun `\u003Crendered ce-help invocation>` to ask which skill fits or what comes next.\n```\n",{"name":5,"description":7,"argument-hint":24},"[pack:\u003Cid> | standards] [mode:non-interactive]","main","03ecf78d3885acd7cbd6ff9f37928d306cc7ba0e","skills\u002Fce-setup","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin","https:\u002F\u002Fgithub.com\u002Fucirello","Gopher. Mars aficionado.","2026-11-14 06:10:50",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ucirello\u002Fcompound-engineering-plugin --skill ce-setup",{"tool":38,"command":39},"bunx","bunx skills add ucirello\u002Fcompound-engineering-plugin --skill ce-setup",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ucirello\u002Fcompound-engineering-plugin --skill ce-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002FSKILL.md",true,[46,52,56,60,66,70,74,78,82,86,90,94,98,102,106,110,116,120,124],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Fcompounding-directive.md","ASSET","资产文件",1886,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Fassets\u002Fcompounding-directive.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fnoslop-directive.md",493,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Fassets\u002Fnoslop-directive.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Fpack-rule-template.md",816,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Fassets\u002Fpack-rule-template.md",{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Facpx-cache-warm.md","REFERENCE","参考文档",1576,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Facpx-cache-warm.md",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcommunication.md",1467,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fcommunication.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fconfig-refresh.md",4865,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fconfig-refresh.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fconfig-template-lines.txt",21346,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fconfig-template-lines.txt",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fconfig-template.yaml",14935,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fconfig-template.yaml",{"path":83,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Flegacy-codex-tool-map.md",1110,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Flegacy-codex-tool-map.md",{"path":87,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fnon-interactive.md",5508,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fnon-interactive.md",{"path":91,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fpack-scaffold.md",4493,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fpack-scaffold.md",{"path":95,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fproject-docs.md",10035,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fproject-docs.md",{"path":99,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Frepo-fixes.md",13575,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Frepo-fixes.md",{"path":103,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fretired-config-keys.yaml",2532,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fretired-config-keys.yaml",{"path":107,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fsummary.md",1642,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Freferences\u002Fsummary.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fcheck-health","SCRIPT","脚本",39647,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Fscripts\u002Fcheck-health",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fcheck-ignore.py",1519,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Fscripts\u002Fcheck-ignore.py",{"path":121,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fconfig-refresh.py",40994,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Fscripts\u002Fconfig-refresh.py",{"path":125,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":126,"sourceHtmlUrl":127},"scripts\u002Fpacks-resolve.py",31938,"https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-setup\u002Fscripts\u002Fpacks-resolve.py",[129,136,143,150,157,164],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M78VM0YXEHCKHF8YT1P2WFHF","ce-retro","Look back over an agent session in this repo, the current one by default or any scope the user names across harnesses, and find what in the repo's environment keeps costing agents effort or leading them into mistakes, keeping only fixes the evidence shows are worth it. Lands the approved environment fixes and hands the rest to their owners. Use for a retro, postmortem, or papercut sweep of how agents worked in this repo. Use ce-compound to keep the lesson of one solved problem, and ce-debug for a bug in product code.","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-retro\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":19},"01M77NMFCKBMKN3C8EACVGP8TG","release-notes","Draft release notes from merged pull requests since the last tag. Use when preparing a release.","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Fskill-eval-cell\u002Ffixtures\u002Freview-roster-skill-prose\u002Fskills\u002Frelease-notes\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":19},"01M77NMEKMA0BXHC4230FV7S39","skill-one","Sample skill","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":19},"01M77NMCCVPH1F4P94W3CCAP5T","disabled-skill","A skill with model invocation disabled","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fdisabled-skill\u002FSKILL.md",[],[],{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":19},"01M77NMACM3ACB6PX92GMHFF3P","claude-only-skill","A skill restricted to Claude Code only","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fclaude-only-skill\u002FSKILL.md",[],[],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":19},"01M77NM9ACPBEWHX6Z3QT1PRMS","agent-only-skill","An agent-only skill not intended for direct user invocation","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fagent-only-skill\u002FSKILL.md",[],[]]