Skill

research

Install
1
Install the plugin
$
npx claudepluginhub athola/claude-night-market --plugin tome

Want just this skill?

Add to a custom plugin, then install with one command.

Description

Orchestrate a multi-source research session across code, discourse, academic, and TRIZ channels. Classifies the domain, dispatches parallel research agents, synthesizes findings, and generates a formatted report. Use when the user invokes /tome:research or asks to research a topic in depth. Do not use for simple web searches.

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Research Session Orchestrator

Run a full multi-source research session: classify the domain, dispatch parallel agents, synthesize findings, and output a formatted report.

Workflow

Step 1: Classify Domain

Run the domain classifier on the topic:

from tome.scripts.domain_classifier import classify
result = classify(topic)
# result.domain, result.triz_depth, result.channel_weights

If confidence < 0.6, ask the user to confirm or override the domain classification before proceeding.

Step 2: Plan Research

from tome.scripts.research_planner import plan
research_plan = plan(result)
# research_plan.channels, research_plan.weights, research_plan.triz_depth

Step 3: Create Session

from tome.session import SessionManager
mgr = SessionManager(Path.cwd())
session = mgr.create(topic, result.domain, result.triz_depth, research_plan.channels)

Step 4: Dispatch Agents

Launch research agents in parallel using the Agent tool. Use this mapping:

ChannelAgent TypePrompt Includes
codetome:code-searchertopic
discoursetome:discourse-scannertopic, domain, subreddits
academictome:literature-reviewertopic, domain
triztome:triz-analysttopic, domain, triz_depth

Rules:

  • Always dispatch code and discourse agents
  • Dispatch academic agent only if "academic" is in research_plan.channels
  • Dispatch triz agent only if "triz" is in research_plan.channels AND triz_depth != "light"
  • Dispatch all eligible agents in a SINGLE message (parallel, not sequential)

Each agent prompt must include:

  1. The topic string
  2. The domain classification
  3. Any channel-specific context (subreddits for discourse, triz_depth for triz)
  4. Instruction to return findings as JSON

Step 5: Collect and Synthesize

After all agents return:

  1. Parse each agent's findings into Finding objects
  2. Merge using tome.synthesis.merger.merge_findings()
  3. Rank using tome.synthesis.ranker.rank_findings()

Step 6: Generate Output

from tome.output.report import format_report, format_brief, format_transcript

# Default to report format
output = format_report(session)

# Save to docs/research/
output_path = f"docs/research/{session.id}-{slug}.md"

Save the session state:

mgr.save(session)

Step 7: Present Results

Display a brief summary to the user:

  • Number of findings per channel
  • Top 3 findings by relevance
  • Path to saved report

Then offer interactive refinement: "Use /tome:dig \"subtopic\" to explore specific areas."

Error Handling

  • If an agent fails, continue with remaining agents
  • If all agents fail, report the error and suggest manual research approaches
  • If synthesis produces 0 findings, state this clearly rather than generating an empty report
  • Save session state even on partial failure

Output Format Selection

FlagFormatFunction
(default)reportformat_report()
--format briefbriefformat_brief()
--format transcripttranscriptformat_transcript()
Stats
Stars222
Forks22
Last CommitMar 20, 2026
Actions

Similar Skills

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.4k