بنقرة واحدة
scout
Search GitHub for new Claude Code skills, agents, patterns and create a PR with findings
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Search GitHub for new Claude Code skills, agents, patterns and create a PR with findings
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Full PCB verification loop using local kicad-cli (DRC + 3D render + gerbers)
Create a new Claude Code skill for this project. Use when you need to add a new skill, improve an existing skill, or convert a workflow into a reusable skill.
Verifies that every PCB pad-to-net assignment matches the manufacturer datasheet pin specifications. Use when changing board.py/routing.py/footprints.py, after GPIO remapping, before releases, or when adding new components. Automated guard against wiring errors like unconnected VBUS, wrong pin assignments, or missing GND connections.
Design intent adversary — cross-checks GPIO, nets, power chains, signal paths across firmware/schematic/PCB/datasheet sources to find lost connections and inconsistencies
Analyze a DFM report and fix all issues in the PCB generation scripts
Run DFM guard tests and add new regression tests after fixing PCB issues
| name | scout |
| model | claude-opus-4-7 |
| description | Search GitHub for new Claude Code skills, agents, patterns and create a PR with findings |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Write, Edit, Grep, Glob, WebFetch, WebSearch |
Search GitHub for new Claude Code patterns (agents, skills, hooks) relevant to this project. Evaluate, integrate useful findings, and create a PR.
cd /Users/pierrejonnycau/Documents/WORKS/esp32-emu-turbo
BRANCH="scout/$(date +%Y%m%d-%H%M%S)"
git checkout -b "$BRANCH"
First, read the state file to know what we've already seen:
cat .claude/scout-state.json
Then run 2-3 search queries based on search_rotation_index (advance by 2-3 each run):
Query rotation (10 queries, cycle through):
| Index | Query |
|---|---|
| 0 | gh search repos ".claude/agents" --sort updated --limit 10 --json fullName,description,updatedAt |
| 1 | gh search repos ".claude/skills" --sort updated --limit 10 --json fullName,description,updatedAt |
| 2 | gh search repos "claude code hooks" --sort updated --limit 10 --json fullName,description,updatedAt |
| 3 | gh search repos "CLAUDE.md agents skills" --sort updated --limit 10 --json fullName,description,updatedAt |
| 4 | gh search code "subagent_type" --language markdown --limit 10 --json repository,path |
| 5 | gh search code "claude/agents" filename:CLAUDE.md --limit 10 --json repository,path |
| 6 | WebSearch: "claude code agent skills best practices 2026" |
| 7 | WebSearch: "claude code .claude/agents hooks examples" |
| 8 | WebSearch: "anthropic claude code multi-agent architecture" |
| 9 | WebSearch: "claude code hardware embedded PCB agents" |
For each new repo (not in seen_repos):
# Check if .claude/ directory exists
gh api repos/{owner}/{repo}/contents/.claude 2>/dev/null | head -20
# If it exists, explore the structure
gh api repos/{owner}/{repo}/contents/.claude/agents 2>/dev/null
gh api repos/{owner}/{repo}/contents/.claude/skills 2>/dev/null
# Read interesting files
gh api repos/{owner}/{repo}/contents/.claude/agents/{file} --jq '.content' | base64 -d
gh api repos/{owner}/{repo}/contents/CLAUDE.md --jq '.content' | base64 -d | head -100
For each finding, score on 4 criteria (0-1 each):
| Criterion | 0 | 0.5 | 1.0 |
|---|---|---|---|
| Applicable | Web-only pattern | Generic dev pattern | Hardware/embedded specific |
| Novel | We already have this | Slight improvement | New capability |
| Quality | Undocumented snippet | Has README | Full skill with tests |
| Compatible | Requires different arch | Needs adaptation | Drop-in compatible |
relevance = (applicable + novel + quality + compatible) / 4
Threshold: integrate if relevance > 0.5
For each relevant finding, in order of relevance:
Identify what to create/update:
.claude/skills/{name}/SKILL.md.claude/settings.json (add to existing hooks array).claude/agents/{name}.mdCLAUDE.md (add section)Adapt to project conventions:
Commit each integration separately:
git add <files>
git commit -m "Scout: integrate <pattern-name> from <source-repo>"
git push -u origin "$BRANCH"
gh pr create --title "Scout: <summary>" --body "$(cat <<'EOF'
## Scout Report
### Findings
| Source | Pattern | Relevance | Action |
|--------|---------|-----------|--------|
| owner/repo | pattern-name | 0.75 | Integrated |
| owner/repo2 | pattern-name2 | 0.45 | Skipped (low relevance) |
### Integrated Changes
- **<file>**: <description> (from <source>)
### Search Queries Used
- `query` → N results, M new repos
🤖 Generated by Scout agent
EOF
)"
Update state file only (stay on main):
git checkout main
git branch -d "$BRANCH"
Edit .claude/scout-state.json: update last_run, add new repos to seen_repos, advance search_rotation_index.
git add .claude/scout-state.json
git commit -m "Scout: update state (no new patterns found)"
git push origin main
.claude/scout-state.json tracks progress across runs:
{
"last_run": "2026-03-02T02:00:00Z",
"seen_repos": ["owner/repo1", "owner/repo2"],
"integrated_patterns": ["pattern-name-1"],
"search_rotation_index": 0
}
search_rotation_index: advances by 2-3 each run, wraps around at 10seen_repos: repos already evaluated (skip on future runs)integrated_patterns: patterns already integrated (avoid duplicates).claude/scout-state.json — State persistence across runs.claude/agents/ — Agent definitions (targets for improvements).claude/skills/ — Skill definitions (targets for new skills).claude/settings.json — Hooks configurationCLAUDE.md — Project documentation