scout-repos
Fetch .claude/ configs from curated repos in sources.yml, compare against dotforge template, report novel patterns.
npx skills add majiayu000/claude-skill-registry --skill scout-repos --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Scout Repos Review curated public repos for Claude Code configuration patterns worth adopting. ## Step 0: Discover tools WebFetch and WebSearch are deferred tools — they may not be loaded yet. Run `ToolSearch("WebFetch WebSearch")` to ensure both tools are available before proceeding. ## Step 1: Load sources Read `$DOTFORGE_DIR/practices/sources.yml`. Build a list of repos with their focus areas. ## Step 2: Fetch each repo's config For each source, use `gh` CLI to fetch their Claude Code configuration files: ```bash # Fetch CLAUDE.md gh api repos/{owner}/{repo}/contents/CLAUDE.md --jq '.content' | base64 -d 2>/dev/null # Fetch .claude/ directory listing gh api repos/{owner}/{repo}/contents/.claude --jq '.[].name' 2>/dev/null # Fetch specific files gh api repos/{owner}/{repo}/contents/.claude/settings.json --jq '.content' | base64 -d 2>/dev/null gh api repos/{owner}/{repo}/contents/.claude/rules --jq '.[].name' 2>/dev/null ``` If `gh` fails (rate limit, private repo), try WebFetch on the raw GitHub URL: ``` https://raw.githubusercontent.com/{owner}/{repo}/main/CLAUDE.md https://raw.githubusercontent.com/{owner}/{repo}/main/.claude/settings.json ``` If both fail, skip the repo and
- Step 0: Discover tools
- Step 1: Load sources
- Step 2: Fetch each repo's config
- Step 3: Analyze patterns
- Hooks
- Settings
- Rules
- Agents
- Commands/Skills
- Step 4: Compare against dotforge
- Step 5: Report
- Constraints
Fetch CLAUDE.md
gh api repos/{owner}/{repo}/contents/CLAUDE.md --jq '.content' | base64 -d 2>/dev/null
Fetch .claude/ directory listing
gh api repos/{owner}/{repo}/contents/.claude --jq '.[].name' 2>/dev/null
Fetch specific files
gh api repos/{owner}/{repo}/contents/.claude/settings.json --jq '.content' | base64 -d 2>/dev/null
gh api repos/{owner}/{repo}/contents/.claude/rules --jq '.[].name' 2>/dev/nullWhat does the scout-repos skill do?
Fetch .claude/ configs from curated repos in sources.yml, compare against dotforge template, report novel patterns.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill scout-repos --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.