From pocket-space
This skill should be used when the user asks to "go deeper on X", "drill into this segment", "I want more detail on X", "deep dive into X", "expand on this section", "deep research into these segments", "research the top segments", or wants to take a segment from a broad research file and produce a longer, more detailed investigation. Typically follows the analyzer — takes the top-ranked segments and produces standalone deep-dive documents for each.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pocket-space:deep-researcherThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Take a segment and produce a detailed, standalone deep-dive document. Typically follows the analyzer — drilling into the top-ranked options to build thorough, evidence-based cases for each.
Take a segment and produce a detailed, standalone deep-dive document. Typically follows the analyzer — drilling into the top-ranked options to build thorough, evidence-based cases for each.
The deep researcher can work standalone or as part of the research workflow:
Every deep-dive document must hyperlink back to the parent research file and comparison matrix (if they exist).
.md or .xlsx) from the analyzer — if one exists, read the rankings to understand which segments scored highestIf no parent file exists, ask the user if they want to run research-md-maker first to establish the landscape, or proceed directly with the deep dive.
For each selected segment, clarify:
Go deep. Unlike the broad research file, this is thorough:
Structure:
# [Segment Name] — Deep Dive
**Author:** [Name]
**Date:** [YYYY-MM-DD]
**Parent Research:** [Hyperlink to the parent research .md file]
**Comparison Matrix:** [Hyperlink to the comparison matrix .md or .xlsx, if it exists]
## Context
[2-3 sentences. What is this segment, why does it matter, and what question
are we answering. Link back to the parent research file for the full landscape.]
## Background
[Longer treatment than the parent file. History, evolution, how this segment
emerged. Establish the foundation a reader needs to understand what follows.]
## Current State
[What exists today. Key players, market size, adoption levels, maturity.
Include data with Vancouver citations.]
## How It Works
[Mechanics, technical details, or operational model — whatever "how it works"
means for this segment. Diagrams or tables where helpful.]
## Strengths & Opportunities
[Detailed analysis, not just bullet points. Each strength backed by evidence.]
## Weaknesses & Risks
[Honest assessment. What could go wrong. What are the limitations.
Include counterarguments to the strengths above.]
## Case Studies
[2-3 real-world examples of this segment in action.
For each: what happened, what worked, what didn't, what's the takeaway.]
### [Case Study 1: Name]
- **Context:** [Situation]
- **Approach:** [What they did]
- **Outcome:** [Result]
- **Takeaway:** [Lesson for Pocket Space]
### [Case Study 2: Name]
[Same structure]
## Relevance to Pocket Space
[Detailed analysis of how this segment connects to Pocket Space specifically.
Not a one-liner — a genuine assessment of applicability, risks, and next steps
if the team wanted to pursue this direction.]
## Key Takeaways
- [5-8 bullets summarizing the most important findings]
## Open Questions
- [What this deep dive didn't fully answer]
- [What would require further investigation, interviews, or testing]
## References
[Vancouver style — numbered list]
[1] Author. Title. Source. Year. URL.
[2] ...
Deep-dive files live inside the Research/ folder of the topic folder, nested under a segment subfolder.
[Topic_of_Research]/Research/), place the deep dive inside a segment subfolder:
[Topic_of_Research]/
├── [Topic_of_Research].docx ← Added later by research-synthesizer
└── Research/
├── README.md
├── Landscape_Research.md ← Parent research file
├── [Segment_A]/ ← Segment subfolder for this deep dive
│ └── [Segment_A]_Deep_Dive.md ← This file goes here
├── [Segment_B]/
│ └── [Segment_B]_Deep_Dive.md
└── ...
[Department_Folder]/
└── [Topic_of_Research]/
└── Research/
├── README.md
└── [Segment_Name]/
└── [Segment_Name]_Deep_Dive.md
[Segment_Name]_Deep_Dive.mdResearch/README.md to reflect the new file and subfolderThe finished document must include:
Research/ folder).md or .xlsx) exists from the analyzer, hyperlink to it in the header metadataSee also: [Segment_Deep_Dive.md](link) pointing to this new documentUse Vancouver citation style — numbered references in order of first appearance.
Inline: Use bracketed numbers where a claim is made.
Token-gated communities saw 3x higher retention than open-access alternatives [1], with the strongest effects in groups under 150 members [2].Rules:
[Author's analysis]Unlike research-md-maker (which is parsimonious), deep-dive documents are thorough:
npx claudepluginhub fangdav/pocket-space-plugins --plugin pocket-spaceConducts deep research via parallel web searches, multi-source validation, and confidence tracking across 11 types like market, competitive, technical; outputs cited Markdown reports.
Runs deep research on topics via web searches, data collection, source verification, synthesis, and structured reports saved to 02-research/. Use for reports, blogs, or exploring new domains beyond quick answers.
Performs structured fact-based research with configurable depth (quick/standard/deep), parallel data collection, source credibility grading, and markdown report generation.