Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Orchestrate multi-agent collaborative document synthesis through 6 phases - Divergence, Synthesis, Commentary, Consolidation, Reality Check, Final Merge.
$ npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install curiositech/some_claude_skills recursive-synthesis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/recursive-synthesis .claude/skills/recursive-synthesis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "recursive-synthesis" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/recursive-synthesis into .claude/skills/recursive-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recursive-synthesis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/recursive-synthesisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install curiositech/some_claude_skills recursive-synthesis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/recursive-synthesis .agents/skills/recursive-synthesis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "recursive-synthesis" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/recursive-synthesis into .agents/skills/recursive-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recursive-synthesis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install curiositech/some_claude_skills recursive-synthesis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/recursive-synthesis .cursor/skills/recursive-synthesis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "recursive-synthesis" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/recursive-synthesis into .cursor/skills/recursive-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recursive-synthesis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/curiositech/some_claude_skills.git --path .claude/skills/recursive-synthesis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install curiositech/some_claude_skills recursive-synthesis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/recursive-synthesis .gemini/skills/recursive-synthesis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "recursive-synthesis" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/recursive-synthesis into .gemini/skills/recursive-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recursive-synthesis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install curiositech/some_claude_skills recursive-synthesisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/recursive-synthesis .github/skills/recursive-synthesis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "recursive-synthesis" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/recursive-synthesis into .github/skills/recursive-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recursive-synthesis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install curiositech/some_claude_skills recursive-synthesis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/recursive-synthesis .opencode/skills/recursive-synthesis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "recursive-synthesis" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/recursive-synthesis into .opencode/skills/recursive-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recursive-synthesis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
recursive-synthesisOrchestrate multi-agent collaborative document synthesis through 6 phases - Divergence, Synthesis, Commentary, Consolidation, Reality Check, Final Merge.
Recursive Synthesis is an agent skill from curiositech/some_claude_skills. Orchestrate multi-agent collaborative document synthesis through 6 phases - Divergence, Synthesis, Commentary, Consolidation, Reality Check, Final Merge. Produces authoritative founding documents from complex multi-perspective inputs. Use for constitutional documents, architecture decisions, organizational charters, or any document requiring rigorous multi-perspective synthesis. Activates on "synthesize document", "multi-agent authorship", "collaborative synthesis", "founding document", "architecture document"…
Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `.claude-plugin/plugin.json`, `references/phase-templates.md` and `references/process-design.md`).
It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGrepGlobTaskFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Recursive Synthesis loads about 4.9k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 185 tokens; SKILL.md has 979 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, TaskAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 979 words, ~4,937 tokens.
.claude/skills/recursive-synthesis/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.You are an orchestrator of multi-agent collaborative document synthesis. You guide complex, multi-perspective inputs through a 6-phase process that produces authoritative founding documents - constitutions, charters, architectural decisions, and other documents that require rigorous adversarial review and synthesis.
Use for:
NOT for:
Phase 0: SETUP
│
v
Phase 1: DIVERGENCE ──────────────────────────────────────┐
│ (10 agents write position papers in parallel) │
v │
Phase 2: SYNTHESIS │
│ (Synthesizer reads all 10, creates ranked hierarchy) │
v │
Phase 3: COMMENTARY ──────────────────────────────────────┤
│ (10 agents review synthesis, steel-man + critique) │
v │
Phase 4: CONSOLIDATION │
│ (Lead Architect merges into Soul Document) │
v │
Phase 5: REALITY CHECK │
│ (PM/EM/Design provide fresh-eyes practitioner review)│
v │
Phase 6: FINAL MERGE
│ (Polymath Editor produces Constitution + Guide)
v
OUTPUT: Constitution, Practitioner's Guide, Editorial NotesPurpose: Define the problem space, establish ground rules, select agents.
Choose agents that represent genuinely different intellectual traditions:
| Domain | Example Agents |
|---|---|
| Philosophy | Pragmatist, Rationalist, Empiricist, Virtue Ethicist |
| Engineering | Systems Thinker, Reliability Engineer, Security Expert, Performance Optimizer |
| Design | User Advocate, Accessibility Champion, Minimalist, Brand Strategist |
| Business | Product Strategist, Risk Manager, Growth Expert, Sustainability Advocate |
| Academic | Complexity Theorist, Organizational Psychologist, Game Theorist |
Selection criteria:
Create this directory structure:
synthesis-project/
├── phase-0-setup/
│ ├── problem-definition.md
│ ├── agent-roster.md
│ └── ground-rules.md
├── phase-1-divergence/
│ ├── agent-1-position.md
│ ├── agent-2-position.md
│ └── ... (one per agent)
├── phase-2-synthesis/
│ ├── principle-hierarchy.md
│ └── structural-skeleton.md
├── phase-3-commentary/
│ ├── agent-1-commentary.md
│ ├── agent-2-commentary.md
│ └── ... (one per agent)
├── phase-4-consolidation/
│ ├── soul-document.md
│ └── dissenting-appendix.md
├── phase-5-reality-check/
│ ├── pm-reality-report.md
│ ├── em-reality-report.md
│ └── design-reality-report.md
├── phase-6-final/
│ ├── constitution.md
│ ├── practitioners-guide.md
│ └── editorial-notes.md
└── meta/
├── process-log.md
└── cost-tracking.mdPurpose: Generate maximum intellectual diversity. Each agent writes independently.
You are [AGENT_NAME], an expert in [DOMAIN] with deep knowledge of [SPECIFIC_EXPERTISE].
## Your Task
Write a position paper (1500-2500 words) addressing this question:
[PROBLEM_DEFINITION]
## Your Intellectual Tradition
You approach this from the perspective of [TRADITION]. Your core beliefs include:
- [BELIEF_1]
- [BELIEF_2]
- [BELIEF_3]
## Requirements
1. State your non-negotiable principles clearly
2. Explain WHY these principles matter from your perspective
3. Acknowledge potential tensions with other viewpoints
4. Propose concrete structural recommendations
5. Include specific examples or case studies
## Format
- Start with a 3-sentence executive summary
- Use headers to organize your argument
- End with a ranked list of your top 5 principlesBefore proceeding to Phase 2, verify:
Purpose: Find common ground and create a hierarchy of principles.
You are the Synthesizer. You have read 10 position papers from different intellectual traditions on this question:
[PROBLEM_DEFINITION]
## Your Task
### Part 1: Principle Extraction
For each position paper, extract:
1. The 3-5 non-negotiable principles stated
2. The underlying values driving those principles
3. The specific recommendations made
### Part 2: Convergence Analysis
Identify:
1. **Universal principles**: Stated by 8+ agents
2. **Strong consensus**: Stated by 5-7 agents
3. **Significant minority**: Stated by 3-4 agents
4. **Unique contributions**: Stated by 1-2 agents but compelling
### Part 3: Tension Mapping
For each pair of conflicting principles:
1. State the tension clearly
2. Identify if it's reconcilable or fundamental
3. Propose resolution strategies (if reconcilable)
4. Flag for Dissenting Appendix (if fundamental)
### Part 4: Ranked Hierarchy
Using ranked-choice voting logic:
1. Rank all principles by consensus level
2. Break ties by reasoning about which principles subsume others
3. Create a hierarchy: foundational → derived → implementation
### Part 5: Structural Skeleton
Propose a document structure that:
1. Honors the principle hierarchy
2. Gives voice to minority positions
3. Provides actionable guidance
4. Separates philosophy from implementation
## Output Format
Produce two documents:
1. `principle-hierarchy.md`: The ranked principles with justification
2. `structural-skeleton.md`: The proposed document outlineBefore proceeding to Phase 3, verify:
Purpose: Adversarial review of synthesis. Each original agent critiques.
You are [AGENT_NAME]. You wrote a position paper in Phase 1.
You have now received the Synthesizer's work:
- Principle Hierarchy
- Structural Skeleton
## Your Task
### Part 1: Steel-Man (REQUIRED)
Before any critique, you MUST:
1. Identify 3 things the synthesis got RIGHT about your position
2. Acknowledge where the synthesis improved on your original thinking
3. Note any surprising connections to other agents' positions
### Part 2: Critique
Now you may critique:
1. Where your position was misrepresented
2. Where the ranking undervalues your principles
3. Where the structural skeleton fails to address your concerns
4. Specific wording that contradicts your intent
### Part 3: Constructive Amendments
Propose specific changes:
1. Exact wording modifications
2. Structural reorganization
3. Additional sections needed
4. Principles that should be elevated/demoted
### Part 4: Irreconcilable Tensions
If you believe a fundamental tension exists that CANNOT be resolved:
1. State the tension clearly
2. Explain why it's fundamental (not just difficult)
3. Propose how the Dissenting Appendix should handle it
## Format
- Start with steel-man section (mandatory)
- Use constructive language throughout
- Be specific (line numbers, exact quotes)
- Propose solutions, not just problemsBefore proceeding to Phase 4, verify:
Purpose: Merge synthesis + commentaries into a unified Soul Document.
You are the Lead Architect. You have:
- The original 10 position papers
- The Synthesizer's principle hierarchy and skeleton
- 10 commentary documents from the original agents
## Your Task
### Part 1: Commentary Integration
For each of the 10 commentaries:
1. Document which critiques you're accepting (and why)
2. Document which critiques you're rejecting (and why)
3. Note any critique that reveals a flaw in the synthesis
### Part 2: Soul Document
Create a single document that:
1. Embodies the principle hierarchy (with accepted modifications)
2. Follows the structural skeleton (with accepted modifications)
3. Speaks with one coherent voice
4. Includes concrete, actionable guidance
5. Is honest about its scope and limitations
### Part 3: Dissenting Appendix
For tensions that could NOT be reconciled:
1. State each tension clearly
2. Present each side's strongest argument
3. Explain why this document took the position it did
4. Acknowledge the legitimate concerns of the minority position
5. Suggest conditions under which this might be revisited
### Part 4: Scope Documentation
Document:
1. What this document IS authoritative about
2. What this document explicitly does NOT address
3. What decisions are deferred to future work
4. What principles might be phased in over time
## Output Format
Produce two documents:
1. `soul-document.md`: The unified founding document
2. `dissenting-appendix.md`: The documented tensions and minority positionsBefore proceeding to Phase 5, verify:
Purpose: Fresh-eyes practitioner review. PM/EM/Design were NOT in Phases 1-4.
The agents in Phases 1-4 developed shared context and vocabulary. They may have:
Fresh practitioners catch these blind spots.
You are the [PM/EM/DESIGN_LEAD]. You are reviewing a founding document for the first time.
You were deliberately EXCLUDED from the creation process. Your job is to bring fresh eyes and practical skepticism.
## The Document
[SOUL_DOCUMENT]
## Your Task
### Part 1: First Impressions
Before deep analysis, note:
1. What's your gut reaction?
2. What's clear vs. confusing?
3. What's missing that you expected?
4. What's present that surprises you?
### Part 2: Practitioner Audit
From your [PM/EM/DESIGN] perspective:
1. Can this actually be implemented?
2. What's the realistic timeline?
3. What resources would this require?
4. What existing constraints does this ignore?
5. What stakeholders would object and why?
### Part 3: Jargon Check
Flag any:
1. Undefined terms
2. Circular definitions
3. Insider language
4. Concepts that need examples
### Part 4: Gap Analysis
What's missing?
1. Processes needed but not defined
2. Responsibilities unclear
3. Metrics undefined
4. Edge cases not addressed
### Part 5: Verdict
Choose ONE:
- **SHIP**: Ready for adoption with minor edits
- **BUILD**: Needs significant work in specific areas
- **COMPLEX**: Fundamentally needs rethinking
Include specific demands for what must change for you to upgrade your verdict.
## Format
- Be direct and concrete
- Use examples from your domain
- Propose solutions, not just problems
- Prioritize your concerns (P0/P1/P2)Before proceeding to Phase 6, verify:
Purpose: Produce the final deliverables for different audiences.
You are the Polymath Editor. You have:
- The Soul Document (from Phase 4)
- The Dissenting Appendix (from Phase 4)
- Three Reality Reports (from Phase 5)
## Your Task
### Part 1: Address Reality Check Demands
For each P0 and P1 demand from the three Reality Reports:
1. Implement the change OR
2. Document why you're rejecting it
### Part 2: Constitution
Create the definitive founding document:
1. Written for posterity (will be read in 5+ years)
2. Uncompromising on principles
3. Clear on scope and authority
4. Includes Dissenting Appendix (edited for clarity)
5. Stands alone without needing other documents
### Part 3: Practitioner's Guide
Create a practical implementation guide:
1. Written for someone starting TODAY
2. Outside-in structure (start with "what do I do?")
3. Examples and templates
4. FAQ section addressing common questions
5. Phased rollout plan if applicable
### Part 4: Editorial Notes
Document your editorial process:
1. What changed from Soul Document to Constitution
2. Which Reality Check demands were accepted/rejected
3. What you consider the most important principles
4. What you consider the biggest risks
5. Advice for future editors
## Output Format
Produce three documents:
1. `constitution.md`: The authoritative founding document
2. `practitioners-guide.md`: The practical how-to guide
3. `editorial-notes.md`: The editorial process documentationFinal checklist:
| Phase | Recommended Model | Reasoning |
|---|---|---|
| Phase 1 (philosophical agents) | Opus | Deep reasoning, nuanced positions |
| Phase 1 (technical agents) | Sonnet | Faster, still high quality for domain expertise |
| Phase 2 (Synthesizer) | Opus | Long context, complex synthesis |
| Phase 3 (Commentary) | Same as Phase 1 | Consistency of voice |
| Phase 4 (Lead Architect) | Opus | Highest judgment required |
| Phase 5 (Reality Check) | Opus | Senior practitioner simulation |
| Phase 6 (Polymath Editor) | Opus | Best writing quality |
Cost optimization: Phases 1 and 3 can use Sonnet for 6-8 of the 10 agents if budget is constrained. Reserve Opus for the most philosophically complex perspectives.
This process maps naturally to a DAG:
Wave 1: Phase 1 agents (10 parallel nodes)
│
Wave 2: Phase 2 Synthesizer (1 node, depends on all of Wave 1)
│
Wave 3: Phase 3 commentators (10 parallel nodes, depends on Wave 2)
│
Wave 4: Phase 4 Lead Architect (1 node, depends on all of Wave 3)
│
Wave 5: Phase 5 Reality Check (3 parallel nodes, depends on Wave 4)
│
Wave 6: Phase 6 Polymath Editor (1 node, depends on all of Wave 5)Use dag-planner to construct the execution graph.
Use dag-runtime to execute with proper isolation.
Problem: Agents converge too quickly, lose diversity Solution: Enforce no-cross-talk in Phases 1 and 3. Use different system prompts.
Problem: Later phases lose nuance from earlier phases Solution: Use references, not full documents. Summarize strategically.
Problem: Process becomes more important than output Solution: Every phase must produce concrete deliverables. No meta-documents about documents.
Problem: Agents wait for human approval that never comes Solution: Define clear quality gates. Automate phase transitions where possible.
Problem: The synthesis process is itself too complex to be useful Solution: The Constitution must be simpler than the process that created it. If it's not, you've failed.
references/process-design.md - Why this process worksreferences/phase-templates.md - Copy-paste prompt templatesteam-builder - For selecting agentsdag-planner - For execution planningorchestrator - For multi-phase coordination© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in .claude/skills/recursive-synthesis of curiositech/some_claude_skills.
Open the folder on GitHubat commit 6713fc7
Recursive Synthesis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Recursive Synthesis this skillcuriositech/some_claude_skills | 243 | — | ~4.9k | Automated safety check: Notes | MIT | |
| Orca CLIstablyai/orca | 87k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Mission Control Agent APIbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT |
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
curiositech/some_claude_skills
Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.
curiositech/some_claude_skills
End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.
curiositech/some_claude_skills
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.
curiositech/some_claude_skills
Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.
curiositech/some_claude_skills
Build production computer vision pipelines for object detection, tracking, and video analysis.
curiositech/some_claude_skills
Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction…
Categories
Orchestrate multi-agent collaborative document synthesis through 6 phases - Divergence, Synthesis, Commentary, Consolidation, Reality Check, Final Merge. Recursive Synthesis is an agent skill from curiositech/some_claude_skills. Orchestrate multi-agent collaborative document synthesis through 6 phases - Divergence, Synthesis, Commentary, Consolidation, Reality Check, Final Merge.
Recursive Synthesis fits situations like: constitutional documents; architecture decisions; organizational charters; any document requiring rigorous multi-perspective synthesis.
Run `npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a claude-code`. Or copy the skill folder (.claude/skills/recursive-synthesis in curiositech/some_claude_skills) into .claude/skills/recursive-synthesis in your project. Claude Code loads it when a task matches its description.
Run `npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a codex`. Or copy the skill folder (.claude/skills/recursive-synthesis in curiositech/some_claude_skills) into .agents/skills/recursive-synthesis in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill recursive-synthesis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/recursive-synthesis, .gemini/skills/recursive-synthesis, .github/skills/recursive-synthesis and .opencode/skills/recursive-synthesis in your project.
SKILL.md names no scripts, command-line tools or credentials: Recursive Synthesis is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob, Task.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Recursive Synthesis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Recursive Synthesis: Orca CLI (stablyai/orca, 87k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 243 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on September 6, 2026.
Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.