research-detail
Scannednpx machina-cli add skill bigph00t/claude-research-team/research-detail --openclawResearch Detail Skill
Retrieve full details, sources, and context for a specific research finding or memory observation.
When to Use
Use this skill when:
- A research injection mentions
[/research-detail <id>] - You need more context about a previously injected finding
- You want to see the full sources for a research result
- You need the complete content instead of just the summary
Usage
Get details for a finding by ID:
curl -s http://localhost:3200/api/findings/<id> | jq
For observations from claude-mem (memory), the ID will be numeric:
curl -s http://localhost:3200/api/knowledge/<id> | jq
Arguments
Pass the finding ID as the argument:
/research-detail abc123- Get details for finding abc123/research-detail 1847- Get details for observation #1847
Response Format
The API returns detailed information including:
query- Original research querysummary- Short summaryfullContent- Complete research contentkeyPoints- Bullet point findings (if available)sources- Array of sources with URLs and snippetsconfidence- Quality/confidence scoredepth- Research depth (quick/medium/deep)createdAt- When the research was performed
Examples
-
Get research details after injection: When you see:
(confidence: 87%) [/research-detail abc123 for sources]Run:curl -s http://localhost:3200/api/findings/abc123 | jq -
Get memory observation details: When you see:
[Memory] observation #1847Run:curl -s http://localhost:3200/api/knowledge/1847 | jq -
Quick check if finding exists:
curl -s http://localhost:3200/api/findings/abc123 | jq '.sources | length'
Related Skills
/research <query>- Perform new research/research-status- Check research service status and recent activity
Source
git clone https://github.com/bigph00t/claude-research-team/blob/main/skills/research-detail/SKILL.mdView on GitHub Overview
Research Detail retrieves full information for a specific finding or memory observation by ID. It lets you pull the original content, sources, and context when a [\/research-detail ID] tag is present, or when you need complete material beyond the summary.
How This Skill Works
Pass the target ID to the appropriate API endpoint to fetch the record. For findings, use /api/findings/<id>, and for memory observations, use /api/knowledge/<id>. The response returns query, summary, fullContent, sources, and metadata such as confidence and depth.
When to Use It
- When a research injection includes [/research-detail <id>], to retrieve full content.
- When you need more context about a previously injected finding.
- When you want the complete sources for a research result.
- When the summary is insufficient and you need full content.
- When validating the depth or confidence of a finding by inspecting sources and fullContent.
Quick Start
- Step 1: Identify the ID from the injected result (e.g., abc123 or 1847).
- Step 2: Run the API call: curl -s http://localhost:3200/api/findings/<id> | jq or /knowledge/<id> | jq.
- Step 3: Review query, fullContent, sources, and metadata in the JSON response.
Best Practices
- Verify the ID matches the injected reference before calling.
- Check the depth and confidence values to gauge reliability.
- Review all sources in the API response for cross-verification.
- Preserve the original query and fullContent for audit trails.
- Prefer fullContent over summary when making decisions.
Example Use Cases
- You see: [/research-detail abc123] and fetch full details.
- Memory observation #1847: retrieve with /knowledge/1847.
- Pull full sources for abc123 to expand notes.
- Validate a finding by comparing fullContent to the summary.
- Cross-check a topic across multiple sources retrieved via /research-detail.
