research-types-exploratory
Exploratory research type sub-skill. Router-dispatched from research-agent parent on signals like "How does", "How can", "How might", "explore", "discover", "what factors". Loads the Discovery Report pattern (Pattern A) and SPICE framework guidance. Not directly model-invocable.
What this skill does
# Exploratory Research Sub-Skill
Router-dispatched paradigm sub-skill for **Exploratory** research. Not directly model-invocable; the `research-agent` parent loads this sub-skill only when Phase 1 detection classifies the question as Exploratory.
## When This Sub-Skill Loads
The parent router dispatches here when the input question contains signals like:
- "How does X work / arise / unfold"
- "How can / How might"
- "Explore", "Discover", "Investigate the space of"
- "What factors influence / shape"
- Domain-mapping requests where the goal is *understanding*, not choosing
**Disambiguation rule** (from `research-agent/references/research-type-patterns.md`):
"Compare X to understand Y" where understanding Y is the goal → Exploratory (not Comparative). Comparison is a method here, not the purpose.
## Framework Selection
| Framework | Use When |
|---|---|
| **SPICE** | Lived-experience or context-bound exploration ("how do users in setting X experience Y") |
| **None** | Open-ended early-stage exploration; decompose into 3-5 sub-questions instead |
PICO and PECO are **not** typical for Exploratory work — both presuppose a defined intervention or exposure with a measurable outcome, which Exploratory research has not yet established.
## Output Pattern: Discovery Report
Use this pattern verbatim for the Findings section (parent skill's Phase 6 Synthesis output):
```
## Research Type: Exploratory
## Framework: [None / SPICE]
## Domain Boundaries
[What is in scope vs. out of scope for this exploration]
## Emerging Themes
Theme 1: [Name]
- Evidence: [S1], [S3]
- Frequency: [how often this theme appears across sources]
- Connections: [related to Theme 2 via ...]
Theme 2: [Name]
...
## Conceptual Relationships
[How themes connect - describe the emerging model]
## Theoretical Saturation Check
[Are additional sources still revealing new themes, or has saturation been reached?]
## Preliminary Model (Provisional)
[Draft conceptual model from discovered themes - explicitly labeled as provisional]
## Open Questions Generated
[What this exploration reveals we do NOT yet know]
```
## Phase Adaptations
The parent skill's 8-phase flow applies. Exploratory-specific notes:
- **Phase 3 (Scope)**: Default depth = "Standard" (8-15 sources). Surface scans risk premature theme closure.
- **Phase 4 (Source Plan)**: Bias source mix toward Primary + Secondary; Grey literature acceptable for emerging-trend signals but flag with `[Grey literature - signal only]`.
- **Phase 5 (Gather)**: Run ReAct cycles until **theoretical saturation** — when 2+ consecutive sources reveal no new themes, stop. Document saturation explicitly in the Discovery Report.
- **Phase 6 (Synthesis)**: Resist forcing a final model. Provisional models are the deliverable; certainty is out of scope for Exploratory.
- **Phase 7 (Bias)**: Watch especially for **availability bias** — exploration over-weights easy-to-find sources. Counter by deliberately seeking less-indexed sources in Phase 4 plan.
## Integrity Constraints (Exploratory-Specific)
- **No premature theme closure.** If a theme has only 1-2 supporting sources, label it `[EMERGING THEME - needs corroboration]` rather than promoting to a stable theme.
- **No causal claims.** Exploratory research surfaces phenomena; it does not explain them. Causal language belongs in Explanatory pattern.
- **Saturation check is mandatory.** The Discovery Report is incomplete without an explicit saturation statement.
## References
- Parent: `research-agent/SKILL.md` (Phase 1-8 flow, GRADE system, integrity constraints)
- `research-agent/references/research-type-patterns.md` § "Exploratory" - identification matrix, disambiguation rules
- `research-agent/references/systematic-review.md` - escalation path when Standard depth surfaces a question requiring full systematic protocol
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.