nx/skills/research-synthesis/SKILL.md
Use when researching unfamiliar topics, comparing technology approaches, or building comprehensive understanding from multiple sources
npx skillsauth add hellblazer/nexus research-synthesisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Delegates to the deep-research-synthesizer agent.
Default: haiku. Escalate via model parameter on the Agent tool:
| Task Shape | Model | When | |-----------|-------|------| | Single-topic lookup, ≤3 sources | haiku (default) | Quick research | | Multi-source synthesis, >5 sources, or cross-project | sonnet | Comprehensive research |
Before dispatching the deep-research-synthesizer agent, seed T1 scratch with link targets so the auto-linker can create catalog links when the agent stores findings:
RDR-\d+) or a known document, resolve it: mcp__plugin_nx_nexus-catalog__search(query="RDR-NNN or document title")rdr-planning-contextmcp__plugin_nx_nexus__scratch(action="put", content='{"targets": [{"tumbler": "<resolved-tumbler>", "link_type": "cites"}], "source_agent": "deep-research-synthesizer"}', tags="link-context")
Use the Agent tool to invoke deep-research-synthesizer:
## Relay: deep-research-synthesizer
**Task**: [what needs to be done]
**Bead**: [ID] or 'none'
### Input Artifacts
- Files: [relevant files]
### Deliverable
Research synthesis across multiple sources
### Quality Criteria
- [ ] All relevant sources consulted
- [ ] Key findings synthesized (not just listed)
- [ ] Recommendations provided with supporting evidence
For full relay structure and optional fields, see RELAY_TEMPLATE.md.
The agent uses mcp__plugin_nx_sequential-thinking__sequentialthinking:
query(question=..., author=..., content_type=...) over search() + manual scopingmcp__plugin_nx_nexus__store_put (RDR-080 — direct call, no agent spawn)development
Use when critiquing / auditing / reviewing a change set against decision history — tries the review plan library first (catalog lookup → decision-evolution traversal → extract → compare), falls through to /nx:query if nothing matches
documentation
Use when doing design / architecture / planning work that walks from prose (RDRs, docs, knowledge) into the modules implementing a concept
development
Use when surveying the plan library's runtime metrics to propose plans for promotion to a higher scope — advisory-only; dispatches the plan-promote-propose meta-seed (no lifecycle ops — those ship in RDR-079)
business
Use when inspecting plan runtime metrics or enumerating dimension-registry usage — dispatches plan_match with dimensions={verb:plan-inspect}; strategy:default reports per-plan metrics, strategy:dimensions reports registry usage counts