[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4PD30RG3MHMQG2BSFGXRB":3,"skill-same:01M6C4PD30RG3MHMQG2BSFGXRB":122},{"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":34,"publishedAt":63,"linkOnly":64,"markdownContent":65,"markdownBody":66,"frontMatter":67,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":6,"ownerHtmlUrl":79,"ownerBlogUrl":80,"ownerDescription":81,"updatedAt":82,"install":83,"resources":95},"01M6C4PD30RG3MHMQG2BSFGXRB","harness-progress",null,"Generate a Progress Tracker HTML for non-engineer vibecoders to glance at session progress (cc:WIP \u002F cc:TODO \u002F cc:完了 counts, percentage, elapsed\u002Festimated minutes, cost so far\u002Festimate, drift alerts). Uses Plans.md as source of truth, renders a single-file HTML with auto-regeneration support. Use when user asks for progress overview, session status snapshot, dashboard, or says: progress tracker, 進捗確認, 進捗ボード, dashboard. Do NOT load for: actual implementation, code review, release work.","Chachamaru127\u002Fclaude-code-harness","Chachamaru127","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96473544?v=4","01M6C4N084DDDEK9SJPGFG9H9M","Chachamaru","01M6C4N0CCNFST9P8C7EJNVH42",3205,"MIT","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fcodex\u002F.codex\u002Fskills\u002Fharness-progress\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62],"progress","harness","harness progress","use","when","progress tracker","alerts","drift","glance","todo","engineer","cost","alert","auto","single-file","code review","overview","session","work","生成","Bash","open","file","code","generate","support","dashboard","review","2026-11-10 10:12:30",false,"---\nname: harness-progress\ndescription: \"Generate a Progress Tracker HTML for non-engineer vibecoders to glance at session progress (cc:WIP \u002F cc:TODO \u002F cc:完了 counts, percentage, elapsed\u002Festimated minutes, cost so far\u002Festimate, drift alerts). Uses Plans.md as source of truth, renders a single-file HTML with auto-regeneration support. Use when user asks for progress overview, session status snapshot, dashboard, or says: progress tracker, 進捗確認, 進捗ボード, dashboard. Do NOT load for: actual implementation, code review, release work.\"\ndescription-en: \"Generate a Progress Tracker HTML for non-engineer vibecoders to glance at session progress (cc:WIP \u002F cc:TODO \u002F cc:完了 counts, percentage, elapsed\u002Festimated minutes, cost so far\u002Festimate, drift alerts). Uses Plans.md as source of truth, renders a single-file HTML with auto-regeneration support. Use when user asks for progress overview, session status snapshot, dashboard, or says: progress tracker, 進捗確認, 進捗ボード, dashboard. Do NOT load for: actual implementation, code review, release work.\"\ndescription-ja: \"進捗 Tracker HTML を生成する。Plans.md を SoT として cc:WIP \u002F cc:TODO \u002F cc:完了 件数・%、経過分数・コスト・drift alert を 1 枚 HTML で表示。PostToolUse hook で 60 秒に 1 回自動再生成。Use when: 進捗確認, 進捗ボード, dashboard。Do NOT load for: 実装作業, code review, release。\"\nallowed-tools: [\"Read\", \"Write\", \"Bash\"]\nargument-hint: \"[--out \u003Cpath>] [--no-open]\"\nuser-invocable: true\n---\n\n# Harness Progress Tracker\n\nPhase 65.4 (Progress Tracker) — 3rd surface of the cognitive-load HTML triplet.\nPlan Brief \u002F Acceptance Demo に続く 3 つ目の HTML surface で、**進行中セッションの全体像を 1 枚の紙で把握** できるようにする。\n\n## Quick Reference\n\n| 入力 | 動作 |\n|---|---|\n| `\u002Fharness-progress` | 現プロジェクトの進捗 snapshot HTML を生成し開く |\n| `\u002Fharness-progress --no-open` | 生成のみ (browser 開かない、PostToolUse hook 用) |\n| `\u002Fharness-progress --out \u003Cpath>` | 出力先指定 (default: `out\u002Fprogress-snapshot.html`) |\n\n## Mission\n\n> \"今のセッションは何件のタスクをどこまで終わらせて、いつ終わる見込みで、いくら使ったか\" を、\n> エンジニアじゃない vibecoder が **3 秒でブラウザで把握** できる HTML 1 枚を生成する。\n\n**やる**:\n- Plans.md の cc:TODO \u002F cc:WIP \u002F cc:完了 件数を集計\n- progress_pct (完了率) を計算 (cc:完了 ÷ 総タスク × 100)\n- 経過分数 \u002F 推定総分数 \u002F コスト so-far \u002F コスト estimate を表示\n- drift alert を表示 (Phase 65.4.3 以降で populate)\n\n完了率は Plans.md のマーカーから算出した値であり、受け入れ検証の合格率ではない。説明では計測値と推定値を分ける。\nstate 欠損時の表示用既定値を実測の 0 と主張せず、元の計測が未取得ならその限界を報告する。ボード生成だけでタスクを完了にしない。\n\n**やらない** (本 cycle):\n- WebSocket \u002F SSE による live update (静的 HTML、再生成で更新)\n- 過去 session の history 比較 (Phase 65.4.4 で別軸)\n- 他 project の cross-project view (Phase 65.3 と独立)\n\n## Schema: progress-snapshot.v1\n\n詳細仕様: [schemas\u002Fprogress-snapshot.v1.schema.json](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Fprogress-snapshot.v1.schema.json)\n\n```yaml\nschema:        progress-snapshot.v1\nproject:       \u003Cbasename of git repo>\ncurrent_task:  \u003Ccc:WIP の最初の項目 1 行サマリ、なければ空文字>\nprogress_pct:  \u003C0-100 の整数、cc:完了 ÷ 総タスク × 100 の四捨五入>\ntodo_tasks:    [{number, title}]    ← cc:TODO のみ\nwip_tasks:     [{number, title}]    ← cc:WIP のみ\ndone_tasks:    [{number, title, commit}]   ← cc:完了 [hash] のみ、hash は 7 chars\nelapsed_minutes:          \u003Cint, state file から>\nestimated_total_minutes:  \u003Cint, state file から>\ncost_so_far_usd:          \u003Cfloat, state file から>\ncost_estimate_usd:        \u003Cfloat, state file から>\nalerts:                    []   ← Phase 65.4.3 以降で populate\ngenerated_at:             \u003CISO8601 UTC>\nwriting_lint_pending:     [{id, pattern, approve_command, pending_count}]  ← optional\u002Fadditive (Phase 136.2)\ndeferred_ops_pending:     [{id, command, approve_command, pending_count}]  ← optional\u002Fadditive (Phase 140.2)\n```\n\n### writing_lint_pending (Phase 136.2)\n\n`scripts\u002Fwriting-rule-list.sh --status pending --json` の出力をそのまま snapshot に\n組み込む optional フィールド。pending proposal が 0 件のときは配列が空になり、\n`progress.html.template` の該当セクションは何も展開せず非表示になる (render-html.sh\nの `{{#section}}` は配列が空だと block を 0 回展開するため)。\n\n表示するのは **コピペ用のコマンド文字列** (`scripts\u002Fwriting-rule-approve.sh --id \u003Cid>`)\nであって押せるボタンではない。承認は人間が CLI で `writing-rule-approve.sh` を実行する\n一択の経路のまま (Phase 135.4。自動昇格経路は無い)。\n\n## Execution Flow\n\n### Step 0: PROJECT_NAME を取得\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\" 2>\u002Fdev\u002Fnull || echo \"current\")\"\n```\n\n### Step 1: snapshot を組み立て\n\n```bash\nSNAPSHOT_JSON=\"$(mktemp \u002Ftmp\u002Fprogress-snapshot-XXXX.json)\"\nbash scripts\u002Fprogress-snapshot.sh \\\n  --plans Plans.md \\\n  --project \"$PROJECT_NAME\" \\\n  > \"$SNAPSHOT_JSON\"\n```\n\n`scripts\u002Fprogress-snapshot.sh` (Phase 65.4.1 で実装) は Plans.md を parse し\n`progress-snapshot.v1` schema 準拠の JSON を出力する。内部で\n`scripts\u002Fwriting-rule-list.sh --status pending --json` も呼び、`writing_lint_pending`\nを additive に組み込む (Phase 136.2。writing-rule-list.sh が無い\u002F失敗する場合は空配列)。\n同様に `.claude\u002Fstate\u002Fdeferred-ops.jsonl` の `status: pending` 行を `deferred_ops_pending`\nとして組み込む (Phase 140.2。ファイルが無い\u002F壊れた行は読み飛ばして空配列)。表示するのは\nコピペ用の `bin\u002Fharness deferred approve \u003Cid>` 文字列で、押せるボタンではない。\n\n### Step 2: HTML をレンダリング\n\n```bash\nOUT_PATH=\"${OUT_PATH:-out\u002Fprogress-snapshot.html}\"\nmkdir -p \"$(dirname \"$OUT_PATH\")\"\n\nbash scripts\u002Frender-html.sh \\\n  --template progress \\\n  --data \"$SNAPSHOT_JSON\" \\\n  --out \"$OUT_PATH\"\n```\n\n### Step 3: ブラウザで開く\n\n`--no-open` flag が**ない**場合のみ実行 (PostToolUse hook からの背景再生成では skip):\n\n```bash\nbash scripts\u002Fplan-brief-open.sh --path \"$OUT_PATH\"\n```\n\n## Cross-project search (default OFF)\n\nPhase 65.4.4 で `--cross-project-group \u003Cname>` flag が追加される。本 cycle (65.4.1) では default OFF、現プロジェクトのみ集計する。\n\n## Failure modes\n\n| 状態 | 動作 |\n|---|---|\n| Plans.md が無い | `progress-snapshot.sh` が exit 1 (clear error message) |\n| Plans.md にタスクが 1 件もない | `progress_pct: 0`, 空配列 で snapshot 生成 (HTML は「タスクなし」表示) |\n| state file (経過分数等) が無い | `elapsed_minutes: 0`, `cost_so_far_usd: 0` で fallback (warning なし) |\n| `git` 不在 \u002F git repo 外 | `project: \"current\"` で fallback |\n\n## Related\n\n- `harness-plan-brief` (Phase 65.1.x) — 1st surface (実装前の説明会)\n- `harness-accept` (Phase 65.2.x) — 2nd surface (検収判断)\n- `harness-progress` (本 skill, Phase 65.4.x) — 3rd surface (進捗ダッシュボード)\n- 65.4.2 (PostToolUse auto-regen)、65.4.3 (drift alert 5 種)、65.4.4 (過去判断 lookup) で機能拡張\n","# Harness Progress Tracker\n\nPhase 65.4 (Progress Tracker) — 3rd surface of the cognitive-load HTML triplet.\nPlan Brief \u002F Acceptance Demo に続く 3 つ目の HTML surface で、**進行中セッションの全体像を 1 枚の紙で把握** できるようにする。\n\n## Quick Reference\n\n| 入力 | 動作 |\n|---|---|\n| `\u002Fharness-progress` | 現プロジェクトの進捗 snapshot HTML を生成し開く |\n| `\u002Fharness-progress --no-open` | 生成のみ (browser 開かない、PostToolUse hook 用) |\n| `\u002Fharness-progress --out \u003Cpath>` | 出力先指定 (default: `out\u002Fprogress-snapshot.html`) |\n\n## Mission\n\n> \"今のセッションは何件のタスクをどこまで終わらせて、いつ終わる見込みで、いくら使ったか\" を、\n> エンジニアじゃない vibecoder が **3 秒でブラウザで把握** できる HTML 1 枚を生成する。\n\n**やる**:\n- Plans.md の cc:TODO \u002F cc:WIP \u002F cc:完了 件数を集計\n- progress_pct (完了率) を計算 (cc:完了 ÷ 総タスク × 100)\n- 経過分数 \u002F 推定総分数 \u002F コスト so-far \u002F コスト estimate を表示\n- drift alert を表示 (Phase 65.4.3 以降で populate)\n\n完了率は Plans.md のマーカーから算出した値であり、受け入れ検証の合格率ではない。説明では計測値と推定値を分ける。\nstate 欠損時の表示用既定値を実測の 0 と主張せず、元の計測が未取得ならその限界を報告する。ボード生成だけでタスクを完了にしない。\n\n**やらない** (本 cycle):\n- WebSocket \u002F SSE による live update (静的 HTML、再生成で更新)\n- 過去 session の history 比較 (Phase 65.4.4 で別軸)\n- 他 project の cross-project view (Phase 65.3 と独立)\n\n## Schema: progress-snapshot.v1\n\n詳細仕様: [schemas\u002Fprogress-snapshot.v1.schema.json](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Fprogress-snapshot.v1.schema.json)\n\n```yaml\nschema:        progress-snapshot.v1\nproject:       \u003Cbasename of git repo>\ncurrent_task:  \u003Ccc:WIP の最初の項目 1 行サマリ、なければ空文字>\nprogress_pct:  \u003C0-100 の整数、cc:完了 ÷ 総タスク × 100 の四捨五入>\ntodo_tasks:    [{number, title}]    ← cc:TODO のみ\nwip_tasks:     [{number, title}]    ← cc:WIP のみ\ndone_tasks:    [{number, title, commit}]   ← cc:完了 [hash] のみ、hash は 7 chars\nelapsed_minutes:          \u003Cint, state file から>\nestimated_total_minutes:  \u003Cint, state file から>\ncost_so_far_usd:          \u003Cfloat, state file から>\ncost_estimate_usd:        \u003Cfloat, state file から>\nalerts:                    []   ← Phase 65.4.3 以降で populate\ngenerated_at:             \u003CISO8601 UTC>\nwriting_lint_pending:     [{id, pattern, approve_command, pending_count}]  ← optional\u002Fadditive (Phase 136.2)\ndeferred_ops_pending:     [{id, command, approve_command, pending_count}]  ← optional\u002Fadditive (Phase 140.2)\n```\n\n### writing_lint_pending (Phase 136.2)\n\n`scripts\u002Fwriting-rule-list.sh --status pending --json` の出力をそのまま snapshot に\n組み込む optional フィールド。pending proposal が 0 件のときは配列が空になり、\n`progress.html.template` の該当セクションは何も展開せず非表示になる (render-html.sh\nの `{{#section}}` は配列が空だと block を 0 回展開するため)。\n\n表示するのは **コピペ用のコマンド文字列** (`scripts\u002Fwriting-rule-approve.sh --id \u003Cid>`)\nであって押せるボタンではない。承認は人間が CLI で `writing-rule-approve.sh` を実行する\n一択の経路のまま (Phase 135.4。自動昇格経路は無い)。\n\n## Execution Flow\n\n### Step 0: PROJECT_NAME を取得\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\" 2>\u002Fdev\u002Fnull || echo \"current\")\"\n```\n\n### Step 1: snapshot を組み立て\n\n```bash\nSNAPSHOT_JSON=\"$(mktemp \u002Ftmp\u002Fprogress-snapshot-XXXX.json)\"\nbash scripts\u002Fprogress-snapshot.sh \\\n  --plans Plans.md \\\n  --project \"$PROJECT_NAME\" \\\n  > \"$SNAPSHOT_JSON\"\n```\n\n`scripts\u002Fprogress-snapshot.sh` (Phase 65.4.1 で実装) は Plans.md を parse し\n`progress-snapshot.v1` schema 準拠の JSON を出力する。内部で\n`scripts\u002Fwriting-rule-list.sh --status pending --json` も呼び、`writing_lint_pending`\nを additive に組み込む (Phase 136.2。writing-rule-list.sh が無い\u002F失敗する場合は空配列)。\n同様に `.claude\u002Fstate\u002Fdeferred-ops.jsonl` の `status: pending` 行を `deferred_ops_pending`\nとして組み込む (Phase 140.2。ファイルが無い\u002F壊れた行は読み飛ばして空配列)。表示するのは\nコピペ用の `bin\u002Fharness deferred approve \u003Cid>` 文字列で、押せるボタンではない。\n\n### Step 2: HTML をレンダリング\n\n```bash\nOUT_PATH=\"${OUT_PATH:-out\u002Fprogress-snapshot.html}\"\nmkdir -p \"$(dirname \"$OUT_PATH\")\"\n\nbash scripts\u002Frender-html.sh \\\n  --template progress \\\n  --data \"$SNAPSHOT_JSON\" \\\n  --out \"$OUT_PATH\"\n```\n\n### Step 3: ブラウザで開く\n\n`--no-open` flag が**ない**場合のみ実行 (PostToolUse hook からの背景再生成では skip):\n\n```bash\nbash scripts\u002Fplan-brief-open.sh --path \"$OUT_PATH\"\n```\n\n## Cross-project search (default OFF)\n\nPhase 65.4.4 で `--cross-project-group \u003Cname>` flag が追加される。本 cycle (65.4.1) では default OFF、現プロジェクトのみ集計する。\n\n## Failure modes\n\n| 状態 | 動作 |\n|---|---|\n| Plans.md が無い | `progress-snapshot.sh` が exit 1 (clear error message) |\n| Plans.md にタスクが 1 件もない | `progress_pct: 0`, 空配列 で snapshot 生成 (HTML は「タスクなし」表示) |\n| state file (経過分数等) が無い | `elapsed_minutes: 0`, `cost_so_far_usd: 0` で fallback (warning なし) |\n| `git` 不在 \u002F git repo 外 | `project: \"current\"` で fallback |\n\n## Related\n\n- `harness-plan-brief` (Phase 65.1.x) — 1st surface (実装前の説明会)\n- `harness-accept` (Phase 65.2.x) — 2nd surface (検収判断)\n- `harness-progress` (本 skill, Phase 65.4.x) — 3rd surface (進捗ダッシュボード)\n- 65.4.2 (PostToolUse auto-regen)、65.4.3 (drift alert 5 種)、65.4.4 (過去判断 lookup) で機能拡張\n",{"name":5,"description":7,"allowed-tools":68,"argument-hint":71,"description-en":7,"description-ja":72,"user-invocable":73},[69,70,55],"Read","Write","[--out \u003Cpath>] [--no-open]","進捗 Tracker HTML を生成する。Plans.md を SoT として cc:WIP \u002F cc:TODO \u002F cc:完了 件数・%、経過分数・コスト・drift alert を 1 枚 HTML で表示。PostToolUse hook で 60 秒に 1 回自動再生成。Use when: 進捗確認, 進捗ボード, dashboard。Do NOT load for: 実装作業, code review, release。",true,"main","c2304c325d4432f51d632e0586d886767b0f41ea","codex\u002F.codex\u002Fskills\u002Fharness-progress",304,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness","https:\u002F\u002Fgithub.com\u002FChachamaru127","https:\u002F\u002Fcanai.jp\u002F","Going all-in on the AI business from April 2025\r\nOSS release: 3k Stars\r\nAI adoption starting with \"I want\"\r\nAX Support | Tokenomics | AISDR |","2026-11-10 18:53:50",{"source":8,"skillName":5,"commands":84,"prompt":94,"zipAvailable":73},[85,88,91],{"tool":86,"command":87},"npx","npx skills add Chachamaru127\u002Fclaude-code-harness --skill harness-progress",{"tool":89,"command":90},"bunx","bunx skills add Chachamaru127\u002Fclaude-code-harness --skill harness-progress",{"tool":92,"command":93},"pnpm","pnpm dlx skills add Chachamaru127\u002Fclaude-code-harness --skill harness-progress","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fcodex\u002F.codex\u002Fskills\u002Fharness-progress\u002FSKILL.md",[96,102,106,110,114,118],{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"manifest.json","REFERENCE","参考文档",109,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FPlatform\u002FOfficial-DotNet\u002Fskills\u002Fcsharp-expert\u002Fmanifest.json",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fdotnet-skills-marketplace.md",6242,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FPlatform\u002FOfficial-DotNet\u002Fskills\u002Fcsharp-expert\u002Freferences\u002Fdotnet-skills-marketplace.md",{"path":107,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":108,"sourceHtmlUrl":109},"schemas\u002Forchestration-ledger.v1.schema.json",2187,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fcodex\u002F.codex\u002Fskills\u002Fharness-progress\u002Fschemas\u002Forchestration-ledger.v1.schema.json",{"path":111,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":112,"sourceHtmlUrl":113},"schemas\u002Forchestration-scorecard.v1.schema.json",3140,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fcodex\u002F.codex\u002Fskills\u002Fharness-progress\u002Fschemas\u002Forchestration-scorecard.v1.schema.json",{"path":115,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":116,"sourceHtmlUrl":117},"schemas\u002Forchestration-totals.v1.schema.json",2541,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fcodex\u002F.codex\u002Fskills\u002Fharness-progress\u002Fschemas\u002Forchestration-totals.v1.schema.json",{"path":119,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":120,"sourceHtmlUrl":121},"schemas\u002Fprogress-snapshot.v1.schema.json",6091,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fcodex\u002F.codex\u002Fskills\u002Fharness-progress\u002Fschemas\u002Fprogress-snapshot.v1.schema.json",[123,139,147,163,191,216],{"skillNo":124,"name":125,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":131,"publishedAt":63},"01M6C4VZCJB9EN3KZXGNARAF6P","escape-skill","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-escape\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[132,133,134,135,136,137,138],"escape skill","escape","Tools","false","true","path","quoted",{"skillNo":140,"name":141,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":63},"01M6C4VYAJW332S5R2MM3RNE0G","zz-review-empty","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-empty\u002FSKILL.md",[],[62,145,146,135,136],"zz review empty","empty",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":63},"01M6C4VWW4GNAZ2680GY04S3EW","session-send","This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fsession-send\u002FSKILL.md",[153],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[52,155,156,157,158,55,159,160,161,162,39],"session send","send","handoff","session handoff","user","message","notify","requests",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":63},"01M6C4VSMYH6XQGR087HQ9Y7HT","memory","Manage SSOT, memory, and cross-tool memory search. Guardian of decisions.md and patterns.md. Use when user mentions memory, SSOT, decisions.md, patterns.md, merging, migration, SSOT promotion, sync memory, save learnings, memory search, harness-mem, past decisions, or record this. Do NOT load for: implementation work, reviews, ad-hoc notes, or in-session logging.","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fmemory\u002FSKILL.md",[169],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[165,171,172,173,36,174,175,176,55,177,178,53,179,180,181,182,159,52,38,183,184,185,186,187,188,136,189,190,39],"MCP","sync","notes","search","memory search","guardian","migrate","tool","decisions","read","write","edit","migration","manage","do","learnings","promotion","reviews","load","for",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":63},"01M6C4VQ3507BV9XRX4BDSES6J","maintenance","File cleanup and archiving. Tidies up bloated Plans.md, session-log.md, old logs, and state files. Trigger: \u002Fmaintenance, cleanup, archive, organize, split session-log. Do NOT load for: implementation, review, release, new feature development.","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fmaintenance\u002FSKILL.md",[],[193,62,198,199,200,201,202,57,203,55,204,205,180,181,182,206,52,207,208,209,185,210,211,212,213,214,136,189,190,215],"development","cleanup","run","release","state","logs","archive","grep","new feature","up","log","files","feature","plans","trigger","整理","split","new",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":230,"publishedAt":63},"01M6C4VK473YJ872RNMBYK7P4R","japanese-writing-drafter","Detect when the operator corrects the agent's Japanese phrasing mid-conversation (rewrites a sentence, calls out a style problem, says 'this wording is bad, say it like X instead') and draft a pending writing-rule proposal into ~\u002F.claude\u002Fwriting-lint\u002Fproposals.jsonl for later human review. This skill is the ONLY writer of proposals.jsonl — it never edits rules.jsonl and never sets status to anything but pending. Promotion to rules.jsonl only happens via the human-run scripts\u002Fwriting-rule-approve.sh. Use when user mentions writing-rule proposal, 表現を直して, 文体を直して, その言い方はNG, writing lint 提案, 指摘をルール化して. Do NOT load for: approving or rejecting proposals (use scripts\u002Fwriting-rule-approve.sh), listing pending proposals (use scripts\u002Fwriting-rule-list.sh), or scanning text against the existing dictionary (the writinglint engine \u002F PostToolUse hook does that).","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fjapanese-writing-drafter\u002FSKILL.md",[222,223,226,227],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":228,"categoryName":229,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[231,232,233,62,234,200,235,236,55,237,238,239,240,180,241,242,38,243,244,245,246,247,248,249,250,251,252,253,254,255,39,256],"writing","japanese writing drafter","japanese","status","lint","operator","提案","text","engine","Rules","list","proposals","never","only","scanning","say","human review","later","conversation","writer","human","scripts","problem","proposal","jsonl","listing"]