consolidate-research
Consolidate and synthesize research outputs from multiple AI models or sources into a unified, pattern-aware, provenance-enriched report with quality metrics. Use when the user has research outputs to consolidate, wants to synthesize multiple reports, asks to "consolidate", "synthesize", or "merge" research findings, or needs to reconcile conflicting information from different sources. Works with outputs from Claude, Gemini, GPT-5.2, or any combination of AI/human sources. Supports manifest-driven (from create-research-brief) and standalone operation.
What this skill does
# Consolidate Research
Synthesize research outputs from multiple sources into a unified, confidence-tiered, pattern-aware report with provenance tracking and quality metrics. Works standalone or manifest-driven from `create-research-brief`.
**Shared references**: `consolidation-manifest-schema.md` (schema), `pattern-registry.md` (patterns + defaults)
## Workflow Overview
```
1. RECEIVE INPUTS ─── Manifest detection, source identification
2. NORMALIZE INPUTS ── Model-specific extraction → common claim format
3. TRIAGE CLAIMS ───── Atomic decomposition, dependency graphs, provenance
4. RECONCILE ───────── Provenance-weighted disagreement, citation dedup
5. SYNTHESIZE ──────── Cross-domain synthesis, structural artifact merging
6. GENERATE OUTPUT ─── Pattern-specific template, quality metrics, freshness
7. SELF-REVIEW ─────── 7 mandatory checks before finalizing
```
---
## Step 1: Receive & Validate Inputs
### Manifest Detection
```
Input contains YAML block with `consolidation_manifest:` label?
│
├─ YES (manifest-driven)
│ ├─ Parse manifest fields: research_id, pattern, models, coverage_matrix
│ ├─ Extract consolidation config: mode, verification_priorities
│ ├─ Load pattern-specific output template from Pattern Registry
│ ├─ Note research chain context (upstream_id, inherited_constraints)
│ └─ Use model identifiers from manifest — do NOT guess sources
│
└─ NO (standalone mode)
├─ Ask for or infer: topic, sources, consolidation mode
├─ Derive pattern from content using Pattern Registry decision tree
├─ Use pattern defaults from Quick Reference table
└─ Confirm inferred pattern + mode with user before proceeding
```
### Source Identification Heuristics
When manifest is absent and source is unlabeled, apply capability-aware signals:
| Signal | Likely Source | Strength |
|--------|--------------|----------|
| Deep reasoning chains, cross-domain analogies, self-corrections, hedged nuance | Claude Opus 4.6 | primary_researcher |
| Structured tables with dense citations, systematic catalogs, source appendix | Gemini 3.1 Pro Deep Research | structured_cataloger |
| Site-specific citations, temporal progression ("as of [date]"), intervention markers | GPT-5.2 Deep Research | targeted_investigator |
| Quick facts, recent dates, sentiment language, short-form responses | GPT-5.2 Chat | recency_validator |
| Proprietary data, specific methodologies, organizational context | Human analyst | domain_expert |
If uncertain after heuristic check, ask user to confirm. When manifest is present, always use `manifest.models[].model_id`.
### Validation
```
Research outputs provided?
├─ NO → Ask: "Please share the research outputs to consolidate."
└─ YES → Sources identifiable?
├─ NO → Ask: "Which source produced each output?"
└─ YES → ≥2 sources?
├─ NO → Warn: single-source consolidation has limited value.
│ Offer: proceed as structured review, or add sources.
└─ YES → Proceed to Step 2.
```
---
## Step 2: Normalize Inputs
Convert heterogeneous model outputs into a common claim format before triaging.
### Extraction Patterns by Source
| Source | Extract | Tag |
|--------|---------|-----|
| **Claude Opus 4.6** | Reasoning chains (analytical steps, not just conclusions) | `type: reasoning_chain` |
| | Conclusions linked to their supporting chains | `type: factual/causal` |
| | Web search findings with source URLs | `channel: web_search` |
| | Cross-domain insights and analogies | `type: cross_domain_synthesis` |
| | Self-review corrections (higher-confidence refinements) | `type: factual` |
| **Gemini 3.1 Pro** | Tables — preserve structure, do not flatten | `type: structural_artifact` |
| | Prose claims with inline citation mapping | `type: factual/causal` |
| | Source appendix — map citations to claims, compute quality scores | provenance metadata |
| | Comparison matrices with per-cell provenance | `type: structural_artifact` |
| | file_search-grounded claims | `channel: internal_document` |
| **GPT-5.2 Deep** | Assertions with temporal markers ("as of [date]") | `provenance.temporal_marker` |
| | Site-specific findings with source domain | `channel: site_restricted` |
| | Intervention-adjusted findings (higher targeted confidence) | boosted weight |
| | Timeline/progression narratives | `type: structural_artifact` |
| **GPT-5.2 Chat** | Quick facts with recency dates | `channel: quick_validation` |
| | Sentiment signals | `type: recommendation` |
| | *All Chat claims default to lower provenance weight* | validation role |
### Normalized Claim Format
```yaml
claim: {id: "C-{seq}", text: "...", type: factual|causal|quantitative|recommendation|unique|reasoning_chain|structural_artifact,
source_model: claude-opus-4-6|gemini-3.1-pro|gpt-5.2-deep|gpt-5.2-chat|human,
provenance: {channel: web_search|file_search|site_restricted|quick_validation|internal_document,
site_restrictions: [], context_documents: [], citation_quality: 0-5, temporal_marker: "YYYY-MM-DD"|null},
depends_on: [claim IDs]}
```
### Citation Quality Scale
| Score | Source Type | Examples |
|-------|------------|---------|
| 5 | Primary | SEC filings, peer-reviewed, official stats, vendor docs |
| 4 | High-quality secondary | Gartner, Forrester, named-source journalism |
| 3 | General secondary | News, press releases, industry publications |
| 2 | Tertiary | Wikipedia, blogs, aggregators |
| 1 | Unsourced assertion | No citation trail |
| 0 | Unverifiable | Contradicts known facts or cites non-existent sources |
---
## Step 3: Triage Claims
Decompose normalized claims into an atomic claims matrix with dependency tracking.
### Claim Types
| Type | Handling |
|------|----------|
| **Factual assertions** | Cross-validate; trace to primary sources |
| **Causal claims** | Map reasoning chains; note mechanism divergence |
| **Quantitative data** | Flag discrepancies >10%; verify primary source agreement |
| **Recommendations** | Tag as interpretation; link to supporting facts |
| **Unique insights** | Preserve with provenance flag; do not discard |
| **Reasoning chains** | Preserve structure; validate logical steps; compare across sources |
| **Structural artifacts** | Preserve format (tables, matrices, timelines); merge in Step 5 |
### Claims Matrix
Rows = claims, columns = sources. `(qN)` = citation quality. Flag same-primary-source convergence separately.
```
│ Claude │ Gemini │ GPT-5.2D│ GPT-5.2C│ Status
─────────────┼────────┼────────┼─────────┼─────────┤
Claim A │ ✓ (q4) │ ✓ (q5) │ ✓ (q3) │ │ Convergent (diff sources)
Claim B │ ✓ (q4) │ ✓ (q4) │ │ │ Convergent (same primary?)
Claim C │ ✓ (q3) │ │ │ │ Unique
Claim D │ ✓ (q4) │ differ │ differ │ │ Contested
```
### Claim Dependency Graphs
`Claim A (factual) ──supports──► Claim B (causal) ──supports──► Claim C (recommendation)`
**Rules**: Recommendation confidence CANNOT exceed supporting facts. If a fact drops tiers, propagate to ALL dependents. Document chains in output.
---
## Step 4: Reconcile
### Provenance-Weighted Disagreement Protocol
Execute in order — stop at first resolution:
| Step | Test | Resolution |
|------|------|-----------|
| 1 | **Coexist?** Different scope/timeframe/definition? | Preserve both with clarifying context |
| 2 | **Provenance?** Higher channel? (`site_restricted` > `web_search` > `quick_validation`; `internal_document` > `web_search` for proprietary) | Favor higher provenance; note alternative |
| 3 | **Citation dedup?** Same primary source(s)? | Treat as SINGLE-SOURCE (Tier 2 cap), not independent |
| 4 | **Specificity?** One more specific or better sourced? | Favor specificity; note alternative |
| 5 | **Majority?** Most sources agree? | Lead with majority; preserve dissent |
| 6 | **All diverge** | Flag "unresolved." Agentic mode: web search. Else: present all views |
### Confidence Tier Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.