skill-portfolio-repo-placement-scan

Maps authored Claude Code skills to target repos with ADD, UPDATE, and CROSS-LINK recommendations.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/wan-huiyan/claude-ecosystem-hygiene --skill skill-portfolio-repo-placement-scan-wan-huiyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-portfolio-repo-placement-scan
Source: https://github.com/wan-huiyan/claude-ecosystem-hygiene/tree/main/plugins/skill-portfolio-repo-placement-scan
Command: npx skills add https://github.com/wan-huiyan/claude-ecosystem-hygiene --skill skill-portfolio-repo-placement-scan-wan-huiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? When you maintain dozens of authored Claude Code skills across several themed repos, skills end up misplaced, duplicated across repos, or stale relative to their local copies. This Skill scans your skill portfolio and produces a per-repo placement report so you know exactly what to add, update, or cross-link without mutating anything. ## Core Features & Use Cases - Function-level inclusion bars: Defines a per-repo inclusion test based on each repo's purpose rather than naive keyword matching, so curated bundles and liberal lesson collections get appropriately different recommendations. - Portfolio deduplication: Detects skills already homed as standalone repos or inside sibling target repos and downgrades them to CROSS-LINK instead of creating drifting copies. - Update divergence detection: Compares version and last_verified frontmatter between repo copies and local copies, reporting the direction of drift. - Use Case: You have 40 skills in ~/.claude/skills and three GitHub repos (a lesson collection, a workflow bundle, a marketplace). Run the scan to get a report showing which skills belong in each repo, which repo copies are behind your local versions, and which skills should only be cross-linked. ## Quick Start Scan my authored skills in ~/.claude/skills and tell me which ones to add, update, or cross-link in each of my target skill repos.

Frequently Asked Questions about skill-portfolio-repo-placement-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which repo each of my Claude Code skills belongs in?

Run a placement scan that defines a function-level inclusion bar for each target repo, then matches skills against that bar rather than keywords. The output is a per-repo ADD, UPDATE, and CROSS-LINK report with reasoning for each recommendation.

How to find skills duplicated across multiple GitHub repos?

Build a portfolio map from gh repo list and each target repo's current contents, then flag any skill already homed as its own repo or inside a sibling repo. Those are downgraded to CROSS-LINK recommendations instead of ADD to prevent drifting copies.

How do I detect stale skill copies in my plugin repos?

Compare the version and last_verified frontmatter fields plus body size between the repo copy and the most-developed local copy of each skill. The scan reports each real divergence with its direction, since the installed copy is often just stale install-lag.

Does the placement scan modify my repositories?

No, the scan only produces a recommendation report and never mutates any repo. It explicitly states that nothing was changed and that PRs await your confirmation as a separate step.

When should I not use a skill placement scan?

Do not use it for standardizing READMEs, finding dormant unused skills, searching skills by capability, scoring a single skill's structural quality, or creating a brand-new skill. Those tasks belong to dedicated tools like ecosystem-audit, find-skills, or skill-creator.