Track skills consolidation into existing leaf-pack structure

[LeoLin990405]

Goal

Consolidate overlapping skills repositories into claude-code-skills without importing whole source repos as new top-level folders.

Migration Rule

Use claude-code-skills as the destination tree and migrate at the leaf skill-pack level.

Do not:

• mirror whole source repositories into new top-level directories
• duplicate existing canonical leaf packs
• preserve old source layouts if they break destination conventions

Confirmed Mapping

• claude-lenny-skills -> product-management/lenny-*
• claude-design-skills -> design/*
• claude-office-skills -> documents/doc-coauthoring, documents/docx
• claude-utility-skills -> ai-collaboration/anthropic-docs, development/mcp-builder, development/skill-creator, development/webapp-testing, research/history-note-processor, system/internal-comms
• claude-obsidian-skills -> productivity/json-canvas, productivity/obsidian-bases, productivity/obsidian-markdown
• github-repo-design-skill -> development/github-repo-design
• claude-ccb-skills -> ai-collaboration/ccb-unified, with research/* backfill only if still unique after dedupe
• claude-skills and ai-coding-skills -> use only as umbrella sources to backfill missing leaf packs after dedupe

Proposed Import Order

1. claude-lenny-skills
2. claude-obsidian-skills
3. claude-office-skills
4. github-repo-design-skill
5. claude-design-skills
6. claude-utility-skills
7. claude-ccb-skills
8. claude-skills
9. ai-coding-skills

Risks To Control

• duplicate canonical content across umbrella repos
• broken path references after moving assets and scripts
• noisy or brittle imports from submodules, workflows, fonts, generated files, and install scripts

Next Step

Create the first migration PR against claude-code-skills using one narrow source repo, preferably claude-lenny-skills or claude-obsidian-skills, and validate the migration pattern before scaling up.

[LeoLin990405]

Progress update:

Completed the first batch of source-repo consolidation where the destination tree was already fully mirrored in claude-code-skills.

Handled source repos:

• claude-lenny-skills -> redirected README.md and root SKILL.md, then archived
• claude-obsidian-skills -> redirected README.md and root SKILL.md, then archived
• claude-office-skills -> redirected README.md and root SKILL.md, then archived

Why these were handled without a content-copy PR:

• destination leaf packs already existed in the monorepo
• source and destination tree SHAs matched
• copying content again would only create duplication

Next recommended candidates need real structure review before action:

• claude-design-skills
• claude-utility-skills
• claude-ccb-skills
• github-repo-design-skill
• claude-skills
• ai-coding-skills

[LeoLin990405]

Progress update, second wave:

Completed additional source-repo consolidation steps:

• claude-design-skills -> redirected README.md and root SKILL.md, then archived
• claude-utility-skills -> redirected README.md and root SKILL.md, then archived

Important nuance:

• claude-design-skills was safe to archive because its source packs were already represented across both design/ and development/ in the monorepo, not only under design/
• claude-utility-skills had one tree-SHA mismatch in skill-creator/scripts/, but the only source-only delta was a tracked __pycache__/ directory; the canonical script files already matched

Explicit non-action:

• github-repo-design-skill is still the live upstream for the development/github-repo-design submodule entry in claude-code-skills
• do not archive it until the monorepo vendors that content and removes the submodule linkage

Remaining higher-complexity candidates:

• claude-ccb-skills
• claude-skills
• ai-coding-skills

[LeoLin990405]

Progress update, third wave:

Completed structure review for the remaining higher-complexity source repos.

Confirmed non-actions:

• claude-ccb-skills is not safely archivable yet
• ai-coding-skills is not safely archivable yet
• claude-skills is an umbrella source repo and is not directly archivable yet

Why claude-ccb-skills is blocked:

• claude-skills/ccb/skills is still a full embedded copy of claude-ccb-skills/skills
• claude-code-skills only has the rewritten ai-collaboration/ccb-unified entry, not a full leaf-pack mirror
• path-compatibility review found 14 source leaf skills, but only ask, all-plan, and stem-modeling have clear absorbed destinations
• provider-specific entries plus pend, ping, and ccb-launcher do not exist as independent destination leaf paths

Why ai-coding-skills is blocked:

• path review found 23 source leaf skills
• most of them do not exist in claude-code-skills as same-name or equivalent leaf destinations
• representative gaps include agent-safety, coding-prompts, openai-codex, openai-agents-sdk, mcp-ecosystem, cursor-mastery, copilot-mastery, aider-mastery, cline-mastery, crewai, autogen-mastra, and ai-code-review
• a few themes are only partially adjacent, not migrated 1:1, such as mcp-server-dev ~ development/mcp-builder and ai-testing ~ development/webapp-testing

Why claude-skills is blocked:

• it contains duplicated embedded subtrees for previously reviewed repos (lenny, obsidian, office, utility, ccb)
• it also still contains special-source areas tied to live upstreams (github-repo-design, r-analytics)
• treat it as an umbrella source for selective backfill only, not a retirement candidate yet

Recommended next step:

• if you want to retire claude-ccb-skills, first add thin compatibility leaf skills in claude-code-skills for cask, dask, dskask, gask, iask, kask, oask, qask, pend, ping, and ccb-launcher
• keep ai-coding-skills as an independent toolkit until there is a real leaf-pack migration plan instead of theme-level overlap

[LeoLin990405]

Progress update, fourth wave:

Created a draft PR to backfill legacy CCB skill names in the monorepo:

• PR: Add legacy CCB compatibility skill shims #2

Important refinement:

• this became a 13-shim compatibility PR, not 11
• reason: install.sh symlinks each top-level skill directory into ~/.claude/skills/<name>
• preserving behavior only inside ai-collaboration/ccb-unified is not enough to preserve the installed legacy leaf names

Compatibility shims added in the PR:

• ask
• all-plan
• cask
• dask
• dskask
• gask
• iask
• kask
• oask
• qask
• pend
• ping
• ccb-launcher

Strategy update:

• ai-coding-skills is no longer an active consolidation target for this phase
• treat it as an independent retained repo unless there is a real leaf-pack migration plan

Further claude-skills decomposition confirmed these explicit duplicate or upstream-bound areas:

• github-repo-design/modules matches github-repo-design-skill/modules
• r-analytics core content matches r-analytics-skill
• ccb/skills matches claude-ccb-skills/skills
• design/skills contains a confirmed duplicated subset already mirrored into claude-design-skills and then into claude-code-skills
• design, r-analytics, ccb, and github-repo-design still point at active independent upstream repos

Current working rule:

• keep claude-ccb-skills alive until compatibility shims are reviewed and merged, then reassess retirement
• keep ai-coding-skills independent
• continue treating claude-skills as an umbrella source for selective decomposition only

[LeoLin990405]

Progress update, fifth wave:

Compatibility PR status:

• reviewed PR Add legacy CCB compatibility skill shims #2 with no blocking issues found
• marked ready
• merged PR Add legacy CCB compatibility skill shims #2: Add legacy CCB compatibility skill shims #2

Result:

• claude-code-skills now provides these legacy CCB entrypoints as installable leaf skills:
  • ask
  • all-plan
  • cask
  • dask
  • dskask
  • gask
  • iask
  • kask
  • oask
  • qask
  • pend
  • ping
  • ccb-launcher
• canonical orchestration remains ai-collaboration/ccb-unified
• research/stem-modeling remains the canonical installed leaf for stem-modeling

Follow-through action:

• updated the root README.md and root SKILL.md in claude-ccb-skills to redirect to claude-code-skills
• archived claude-ccb-skills

Updated working state:

• claude-ccb-skills is now retired as an active source repo
• ai-coding-skills remains independently retained
• claude-skills remains an umbrella source for selective decomposition only

[LeoLin990405]

Additional claude-skills decomposition finding:

The remaining claude-skills/design/skills items that were still ambiguous are:

• design-frontend
• design-generative
• design-system
• design-visual

Follow-up checks found:

• no matching paths in claude-code-skills
• no matching paths in claude-design-skills

Current conclusion:

• these four appear to be umbrella-only workflow wrappers that exist inside claude-skills itself
• they should not be classified as already migrated duplicates
• they also should not be treated as covered by claude-design-skills

Implication:

• claude-skills/design is mixed-content: partly duplicated source material, partly umbrella-only wrappers

[LeoLin990405]

Consolidation update:

• claude-skills is still not archivable. Final classification is now clear:
  • github-repo-design -> special-upstream duplicate of github-repo-design-skill
  • r-analytics -> special-upstream duplicate of r-analytics-skill
  • ccb / design / obsidian / office / utility -> mixed content (duplicated skill subtrees plus umbrella-only templates, orchestration, workflows, or wrapper skills)
  • lenny -> umbrella-only alternate PM taxonomy (pm-*), not a direct duplicate of claude-lenny-skills
• Practical implication: claude-skills cannot be retired until the mixed and umbrella-only parts are explicitly re-homed.
• Fork review also completed for repo-governance purposes:
  • Auto-claude-code-research-in-sleep -> recommend archive as a historical snapshot unless we still need the 2026-03-16 fork state
  • MiroFish -> recommend archive after confirming the fork-only Claude Code CI workflow is no longer needed

Canonical execution record remains in Knowledge-Hub.

[LeoLin990405]

Consolidation update:

• Auto-claude-code-research-in-sleep has now been archived as a historical snapshot.
• MiroFish has also now been archived.
  • rationale: the fork-only delta was a single claude-review.yml workflow, and recent Actions run history was empty, so there was no visible evidence of active use.
• claude-skills is still not retireable, but the mixed subtrees are now more precisely bounded:
  • obsidian/skills == archived standalone source repo copy; obsidian/templates is umbrella-only
  • office/skills == archived standalone source repo copy; office/templates and office/workflows are umbrella-only
  • utility/skills == archived standalone source repo copy; utility/templates is umbrella-only
  • ccb/skills == archived standalone source repo copy; ccb/templates and ccb/orchestration are umbrella-only

Practical implication: if claude-skills is ever retired, the next safe migration unit is not the whole subtree. It is the umbrella-only outer layer around already-classified */skills copies.

[LeoLin990405]

Consolidation update:

• github-repo-design-skill is still not retireable.
  • claude-code-skills/.gitmodules still points development/github-repo-design at LeoLin990405/github-repo-design-skill
  • the path is still a live submodule gitlink, not a vendored directory
  • practical implication: retirement requires full vendoring into claude-code-skills, submodule removal, and only then redirect/archive
• claude-skills should now be treated as an outer-layer migration problem, not a */skills duplication problem.
  • next safe units are ccb/orchestration, ccb/templates, office/workflows, office/templates, obsidian/templates, utility/templates
• New submodule-governance debt was also surfaced:
  • .gitmodules still points research/aris at Auto-claude-code-research-in-sleep
  • that source repo is now archived, so claude-code-skills has at least one archived-source submodule dependency to clean up later

Account-wide repo cleanup is no longer primarily about archiving more repos. The remaining work is structural: umbrella-only migration and submodule retirement.

[LeoLin990405]

Execution update:

A new draft PR is now open to turn the current governance decisions into actual repo changes:

• PR refactor: vendor repo-design and migrate legacy outer-layer assets #3: refactor: vendor repo-design and migrate legacy outer-layer assets #3

What it does:

• vendors development/github-repo-design and removes its self-owned submodule entry
• removes archived-source research/aris from .gitmodules and the README catalog
• migrates the first clearly-bounded umbrella-only outer-layer assets from claude-skills
  • ccb/orchestration + ccb/templates -> ai-collaboration/ccb-unified/{references,templates}
  • office/templates + office/workflows -> documents/doc-coauthoring/{templates,workflows}
• updates skill docs so the migrated assets are discoverable in their new locations

Practical impact:

• github-repo-design-skill retirement is now in executable PR form rather than only a plan
• research/aris archived-source submodule debt is actively being removed
• claude-skills migration has moved from classification to the first real outer-layer extraction

[LeoLin990405]

Execution update:

• PR refactor: vendor repo-design and migrate legacy outer-layer assets #3 has now been merged:
  • refactor: vendor repo-design and migrate legacy outer-layer assets #3
• The merge completed all of the following in claude-code-skills:
  • vendored development/github-repo-design
  • removed research/aris from .gitmodules and the README catalog
  • migrated the first two outer-layer batches from claude-skills
    • ccb/orchestration + ccb/templates
    • office/templates + office/workflows
    • obsidian/templates
    • utility/templates
  • added stale symlink pruning to install.sh so removed in-repo skills do not linger in ~/.claude/skills
• Follow-on retirement is also complete:
  • github-repo-design-skill root docs were redirected to the monorepo path
  • github-repo-design-skill has now been archived

Practical implication:

• github-repo-design-skill is no longer a governance blocker
• the remaining structural work is now centered on claude-skills itself, not on that standalone source repo

[LeoLin990405]

Progress update on the umbrella-repo unwind:

• PR feat: restore toolkit routers and template assets #4 is now merged: feat: restore toolkit routers and template assets #4
• Restored toolkit-level router SKILL.md entry points at:
  • design/
  • documents/
  • productivity/
  • development/
  • product-management/
• Migrated missing canonical template assets:
  • design/templates/{design-brief,design-review-checklist,style-guide}.md
  • product-management/templates/{prd-template,okr-template,user-interview-script,competitive-analysis,decision-doc-template,financial-model-spec,launch-checklist,metrics-dashboard,one-on-one-template,retro-template}.md
• Restored ai-collaboration/all-plan/references/flow.md
• Updated root README to surface the toolkit routers

Current blocker summary for retiring claude-skills itself:

1. r-analytics is still substantively unique
2. lenny still has unique workflow-wrapper / content boundaries
3. ccb still has legacy-wrapper / reference boundaries beyond compatibility shims
4. root docs and .github in claude-skills still present it as the live monorepo

So the next phase is no longer outer-layer template migration. It is deciding canonical ownership for r-analytics, lenny, and ccb, then cleaning the root surface of claude-skills once those boundaries are resolved.

[LeoLin990405]

Progress update:

• PR feat: add compatibility wrappers for PM and CCB #5 is now merged: feat: add compatibility wrappers for PM and CCB #5
• Added ai-collaboration/SKILL.md as the canonical coordination-toolkit router
• Added legacy pm-* compatibility wrappers under product-management/:
  • pm-discovery
  • pm-strategy
  • pm-execution
  • pm-growth
  • pm-analytics
  • pm-communication
  • pm-team
  • pm-leadership
  • pm-playbooks

This was the last major compatibility gap for retiring the old umbrella repo.

Follow-up action completed outside claude-code-skills:

• LeoLin990405/claude-skills root docs and toolkit entry docs were rewritten as canonical redirects
• LeoLin990405/claude-skills is now archived

Resulting canonical ownership is now clear:

1. claude-code-skills = active monorepo canonical surface
2. r-analytics-skill = standalone canonical R analytics repo
3. claude-skills = historical umbrella snapshot only

Any further work from here is optional structural cleanup, not required for retiring claude-skills.

[LeoLin990405]

补一条治理收口结论，供后续继续 vendoring / 精简 compatibility surface 时复用：

• 当前 .gitmodules 里剩余 10 个 submodule，只有 3 个是 self-owned：productivity/obsidian-cli、development/r-analytics、documents/mineru
• 其中 r-analytics-skill 已确认继续保留为独立 canonical repo，不作为下一步 vendoring 目标
• 剩余 7 个都是 external submodule，当前默认保持 submodule 形态即可
• 账号里额外复核了 Hivemind、udacity-masters-ai-subtitles、awesome-llms、awesome-ai-orchestration、xiaotie 这 5 个边界较模糊的 active repo；它们最近 push 都在 2026-03，且定位清晰，没有出现“已被替代”或“只剩占位内容”的证据
• 结论：账号级 archive 主线到这里已经基本收口。后续更适合继续做 claude-code-skills 内部的 self-owned submodule 边界治理，而不是继续批量归档 active repo。

[LeoLin990405]

继续补一条收口记录：

• PR feat: vendor obsidian-cli skill #6 已合并：productivity/obsidian-cli 已从 self-owned submodule 改成 vendored 目录
• .gitmodules 已移除 productivity/obsidian-cli
• repo README 里的 submodule 计数已从 10 降到 9
• obsidian-cli-skill 已完成 redirect commit（8049243）并归档
• 当前 self-owned submodule 只剩 2 个：development/r-analytics、documents/mineru
• 当前判断：r-analytics-skill 继续独立 canonical；下一步如果继续做 submodule 治理，更值得重新评估的是 mineru-skill，不是再扩大 archive 范围。