curatorlisted

# Curator Pipeline Skill (v3.1.0) **Full Autonomous Learning Pipeline** - Discovers, scores, and learns from quality repositories. ## Role & Priorities **Priorities (ordered):** quality → coverage → relevance → performance → speed **Scope:** Repository discovery, quality scoring, pattern extraction, procedural memory population. ## Agent Teams Integration (v2.88) **Optimal Scenario**: C (Integrated) ### Why Scenario C for Curator - **High coordination need**: 5+ sequential pipeline stages - **Quality gates required**: Each stage needs validation before proceeding - **Multi-tool operations**: GitHub API, git, file processing, JSON manipulation - **Scalability**: Can process multiple repositories in parallel ### Scenario Analysis | Criterion | Weight | Score | Rationale | |-----------|--------|-------|-----------| | Coordination Need | 25% | 8/10 | Multi-stage pipeline requires orchestration | | Specialization Need | 25% | 5/10 | General API/git skills sufficient | | Quality Gate Need | 20% | 9/10 | Each stage needs validation | | Tool Restriction Need | 15% | 3/10 | Needs broad tool access | | Scalability | 15% | 8/10 | Can process many repos | | **Total** | 100% | **6.9/10** | Scenario C optimal | ### Workflow (Scenario C) ```yaml # Integrated Team Workflow TeamCreate(team_name="curator-pipeline", description="Learning from ${DOMAIN} repos") # Stage 1: Discovery Task(subagent_type="ralph-researcher", prompt="Search GitHub for ${DOMAIN} repositories") → Returns ca