curator-repo-learn
Learn patterns from a specific GitHub repository. Clones, analyzes code structure, extracts patterns, and populates procedural memory. Use for: targeted learning from known quality repos, quick knowledge acquisition, specific pattern extraction. Triggers: /repo-learn, /curator-repo-learn, 'learn from repo'.
npx skills add majiayu000/claude-skill-registry --skill curator-repo-learn --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.
# Curator Repo-Learn Skill (v2.88) **Single Repository Pattern Extraction** - Learn from a specific GitHub repository. ## Role & Priorities **Priorities (ordered):** accuracy → relevance → speed → coverage **Scope:** Clone repository, analyze structure, extract patterns, update procedural memory. ## Agent Teams Integration (v2.88) **Optimal Scenario**: B (Custom Subagents) ### Why Scenario B for Repo-Learn - **Independent operation**: Single repo, single task - **High specialization need**: Pattern recognition requires expertise - **Low coordination need**: No multi-stage pipeline - **Efficient execution**: Direct spawn, no team overhead ### Scenario Analysis | Criterion | Weight | Score | Rationale | |-----------|--------|-------|-----------| | Coordination Need | 25% | 2/10 | Independent operation | | Specialization Need | 25% | 9/10 | Requires pattern recognition | | Quality Gate Need | 20% | 6/10 | Moderate validation needed | | Tool Restriction Need | 15% | 3/10 | Standard tools sufficient | | Scalability | 15% | 2/10 | Single repo focus | | **Total** | 100% | **5.2/10** | Scenario B optimal | ### Workflow (Scenario B) ```yaml # Direct Subagent Spawn Task(subagent_type="ralph-
- Role & Priorities
- Agent Teams Integration (v2.88)
- Why Scenario B for Repo-Learn
- Scenario Analysis
- Workflow (Scenario B)
- Usage
- Basic Usage
- With Domain Override
- With Language Hint
- Process Flow
- Domain Detection (GAP-C02 FIX)
- Output Example
- Error Handling
- Integration with Curator Pipeline
Domain Keywords Quick learning without full pipeline Full pipeline for comprehensive learning Single repo learning (this skill) Listar todos los reportes de esta skill ls -lt docs/actions/curator-repo-learn/ Ver el reporte más reciente cat $(ls -t docs/actions/curator-repo-learn/*.md | head -1) Buscar reportes fallidos grep -l "Status: FAILED" docs/actions/curator-repo-learn/*.md
What does the curator-repo-learn skill do?
Learn patterns from a specific GitHub repository. Clones, analyzes code structure, extracts patterns, and populates procedural memory. Use for: targeted learning from known quality repos, quick knowledge acquisition, specific pattern extraction. Triggers: /repo-learn, /curator-repo-learn, 'learn from repo'.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill curator-repo-learn --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.