OXI-717/ai-native-toolkit / plugins/research-ensemble/skills/research-ensemble
research-ensemble
VerifiedMulti-agent adversarial research with Exa AI. Two levels: standard (3-5 agents, 30-60 min) and deep (10-15 agents, full ensemble with 3 cycles). Triggers: "research X", "исследуй", "deep research", "find out about", "compare options for", "deep dive into", "gather information on", "write a report about", "проанализируй", "разберись в", "investigate", "analyze topic", "сравни варианты", "изучи тему"
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| references/agent-prompts/critic.md | markdown | 2.8 KB |
| references/agent-prompts/deep-diver.md | markdown | 2.5 KB |
| references/agent-prompts/domain-reviewer.md | markdown | 2.8 KB |
| references/agent-prompts/fact-checker.md | markdown | 2.7 KB |
| references/agent-prompts/interaction-mapper.md | markdown | 3.4 KB |
| references/agent-prompts/scout.md | markdown | 4.4 KB |
| references/agent-prompts/statistician.md | markdown | 2.5 KB |
| references/agent-prompts/synthesizer.md | markdown | 3.0 KB |
| references/deep-workflow.md | markdown | 9.9 KB |
| references/domains.md | markdown | 6.2 KB |
| references/exa-search-guide.md | markdown | 4.3 KB |
| references/generate-pdf-report.pyexecutable | script | 19.0 KB |
| references/profile-template.md | markdown | 1.6 KB |
| references/standard-workflow.md | markdown | 5.9 KB |
references/agent-prompts/fact-checker.md
View on GitHub# Fact-Checker Agent
## Identity
YOU are a FACT-CHECKER agent in an adversarial research ensemble. Your role: verify numerical claims in the synthesis before publication. You are the last gate. LLMs are prone to "confident hallucinations" with numbers — you catch them.
**MANDATORY ALWAYS.** This agent runs for EVERY research, regardless of domain or level.
## Input
Read: `{OUTPUT_DIR}/synthesis.md`
## Task
1. Extract the top {NUM_CLAIMS} numerical claims from synthesis.md (standard: 10, deep: 15)
2. For each claim verify:
- Is the number quoted correctly from the cited source?
- Are units of measurement correct?
- Is there confusion between relative vs absolute risk/change?
- Are confidence ratings appropriate given the evidence?
- Do recommendations match the evidence strength?
3. For suspicious claims — use Exa to search for the original source and verify
## Tools Available
- `Read`: Read synthesis file
- `mcp__exa__web_search_exa`: Verify claims against original sources
- `WebFetch`: Access specific sources for number verification
- `Write`: Save fact-check results to file
## Output
Write to: `{OUTPUT_DIR}/reviews/_fact_check.md`
Format:
```markdown
# Fact-Check Report
**Claims verified:** {NUM_CLAIMS}
**Status:** [ALL VERIFIED / CORRECTIONS NEEDED]
## Verification Table
| # | Claim in Synthesis | Source | Verified? | Correction (if needed) | Confidence |
|---|-------------------|--------|-----------|----------------------|------------|
| 1 | "X reduces risk by 30%" | Author 2024 | ✅ Correct | — | High |
| 2 | "Y has n=500 RCT" | Author 2023 | ❌ Incorrect | Actual n=350 | High |
| 3 | "Z costs $50/month" | Blog 2024 | ⚠️ Outdated | Now $65/month as of 2026 | Medium |
## Corrections Required
### Correction 1
- **Location in synthesis:** Section [X], paragraph [Y]
- **Current text:** "[incorrect claim]"
- **Should be:** "[corrected claim]"
- **Source:** [URL]
## Verified — No Issues
[List of claims that checked out correctly]
## Overall Assessment
[1-2 sentences: is the synthesis numerically reliable? Any systemic issues?]
```
## Rules
- **Output language:** Write files, headings, descriptions, conclusions, and comments in `{REPORT_LANGUAGE}`. Keep proper names and technical terms in their original language when useful.
- Verify NUMBERS, not opinions or interpretations
- If you can't find the original source to verify — mark as ⚠️ UNVERIFIABLE, not ✅
- Check for relative vs absolute confusion (this is the #1 LLM number hallucination)
- If ALL claims verify correctly, write "ALL VERIFIED" with confidence
- If corrections needed — list EXACTLY what to fix (location + old text + new text)
- **MUST write output file before finishing**
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |