analysis-orchestration
/analysis-orchestration
Dobiera model AI do kodowania i przetwarzania wsadowego dokumentów, porównując możliwości i koszty w drugim etapie analizy.
- Autor
- linxule ↗
- Repozytorium
- interpretive-orchestration ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 06.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/estimate-costs.js
Co robi i kiedy
Dobiera model AI do kodowania i przetwarzania wsadowego dokumentów, porównując możliwości i koszty w drugim etapie analizy.
Wyzwalacze z opisu
Oryginalny opis (EN)
This skill should be used when users ask about which AI model to use for coding, mentions 'cost', 'batch', 'API', 'configure analysis', wants to process multiple documents, or needs to understand model capabilities and costs for Stage 2.
Jak działa
- When to Use
- Capabilities
- Model Selection Guide
- Cost Estimation
- Batch Processing Strategy
- Decision Trees
- Integration with Interpretive Orchestration
- Related
Podgląd SKILL.md
---
name: analysis-orchestration
description: "This skill should be used when users ask about which AI model to use for coding, mentions 'cost', 'batch', 'API', 'configure analysis', wants to process multiple documents, or needs to understand model capabilities and costs for Stage 2."
---
> Script paths: `${CLAUDE_PLUGIN_ROOT}` below is this plugin's root folder, two levels above this skill's own folder. Claude Code fills it in. If you see it unfilled, still starting with a dollar sign (as in Codex, Copilot CLI or Kimi Code), put that folder's absolute path in its place before you run a command.
# analysis-orchestration
Model selection, cost estimation, and batch processing setup for AI-assisted coding. Helps researchers configure their analysis approach with awareness of tradeoffs.
## When to Use
Use this skill when:
- User asks about which AI model to use for coding
- User mentions "cost", "batch", "API", or "configure analysis"
- User wants to process multiple documents
- User needs to understand model capabilities and costs
- Starting Stage 2 and needing to plan the approach
## Capabilities
1. **Model Selection Guidance** - Help choose between models based on task needs
2. **Cost Estimation** - Estimate API costs before processing
3. **Batch Strategy** - Plan efficient document processing
4. **API Configuration** - Set up for programmatic coding (future)
## Model Selection Guide
### For Document Coding (Stage 2)
| Model | Best For | Cost | Quality |
|-------|----------|------|---------|
| Claude Opus | Complex interpretive coding, nuanced themes | $$$ | Highest |
| Claude Sonnet | Balanced quality and cost for systematic coding | $$ | High |
| Claude Haiku | Initial passes, high volume, simple categorization | $ | Good |
### Recommendation by Task
**Deep Interpretive Coding (@dialogical-coder)**
- Use: Opus or Sonnet
- Why: Requires nuanced understanding, theoretical sensitivity
- Pattern: Process 5-10 documents per session with reflection
**Initial Categorization**
- Use: Sonnet or Haiku
- Why: Applying established codes is less interpretively demanding
- Pattern: Batch process with human review
**Pattern Characterization**
- Use: Opus
- Why: Requires integration across documents, theoretical abstraction
## Cost Estimation
### Rough Estimates (2025 pricing)
| Documents | Model | Estimated Cost |
|-----------|-------|----------------|
| 10 interviews (~50 pages) | Opus | $15-25 |
| 10 interviews (~50 pages) | Sonnet | $5-10 |
| 50 documents | Opus | $75-125 |
| 50 documents | Sonnet | $25-50 |
**Variables:**
- Document length (tokens)
- Coding depth (passes per document)
- Output verbosity (full reasoning vs brief)
### Scripts
#### estimate-costs.js
Estimates API costs based on document characteristics.
```bash
node "${CLAUDE_PLUGIN_ROOT}/skills/analysis-orchestration/scripts/estimate-costs.js" \
--documents 25 \
--avg-pages 5 \
--model sonnet \
--passes 2
```
**Returns:** Estimated cost range and token counts.
## Batch Processing Strategy
### Small Corpus (10-30 documents)
- Process individually with full dialogical coding
- High engagement, rich reasoning
- Best for: Interpretive research, theory building
### Medium Corpus (30-100 documents)
- Batch in groups of 10
- First pass: categorization
- Second pass: deep coding on interesting cases
- Best for: Mixed-methods, systematic reviews
### Large Corpus (100+ documents)
- Strategic sampling for deep coding
- Batch categorization with random quality checks
- Best for: Large-scale studies, triangulation
## Decision Trees
### Which Model Should I Use?
```
Is this initial exploratory coding?
├── Yes → Consider Haiku for volume, validate with Sonnet
└── No, this is interpretive coding
├── Budget constrained?
│ ├── Yes → Sonnet (good balance)
│ └── No → Opus (best quality)
└── Need to process >50 documents?
├── Yes → Two-pass: Haiku then Sonnet on subset
└── No → Single-pass with Sonnet or Opus
```
### How Many Documents Per Session?
```
Using @dialogical-coder (4-stage process)?
├── Yes → 5-10 documents per session (reflection breaks)
└── No, systematic application?
├── Complex coding scheme → 10-15 documents
└── Simple categorization → 20-30 documents
```
## Integration with Interpretive Orchestration
### Stage 1
- No AI models needed (manual coding)
- Focus on human theoretical sensitivity
### Stage 2 Phase 1 (Parallel Streams)
- Stream A (theoretical): Sonnet for literature analysis
- Stream B (empirical): Start with Sonnet, elevate complex cases to Opus
### Stage 2 Phase 2 (Synthesis)
- Opus recommended for integration work
- Cross-stream synthesis requires nuanced reasoning
### Stage 2 Phase 3 (Pattern Characterization)
- Opus for pattern identification
- Sonnet for validation passes
## Related
- **Commands:** `/qual-configure-analysis` triggers this skill
- **Agents:** @research-configurator provides interactive guidance
- **Skills:** `coding-workflow/` for batch processing execution
Pliki w paczce (2)
- SKILL.md 5 KB
- scripts/estimate-costs.js 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · linxule/interpretive-orchestration | 100 | MIT |
| linxule/interpretive-orchestration | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ffd8e6d30afd (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100coding-workflow
Prowadzi etap 2 kodowania dokumentów: systematyczne przetwarzanie, śledzenie postępu kodowania i generowanie dokumentacji audytowej. - 100workflow-orchestration
Uruchamia kilka analiz workflow naraz w jednym przebiegu, czyli pełny przegląd analityczny. - 100cc-cost-analysis
Analizuje koszty użycia Claude Code z danych OpenTelemetry: wydatki na użytkownika, drogie sesje, rozdęcie kontekstu oraz podział kosztów modeli i tokenów, ze strukturą analizy, gotowymi zapytaniami i wzorami kosztu. - 100coding-workflow
Prowadzi drugi etap kodowania materiałów badawczych: sesje wsadowe, śledzenie postępu i dokumentację audytu. - 100grok
Dobiera i porównuje modele xAI Grok pod kątem możliwości, kosztów, kontekstu i cyklu życia. - 100token-cost-analyzer
Analizuje i optymalizuje koszty API LLM: zużycie tokenów, audyt kosztów i prompty pod kątem wydatków na AI.