research-types-descriptive
Descriptive research type sub-skill. Router-dispatched from research-agent parent on signals like "What is", "What are", "Map", "Document", "Inventory", "Survey the field". Loads the Landscape Map pattern (Pattern B). Not directly model-invocable.
What this skill does
# Descriptive Research Sub-Skill
Router-dispatched paradigm sub-skill for **Descriptive** research. Not directly model-invocable; the `research-agent` parent loads this sub-skill only when Phase 1 detection classifies the question as Descriptive.
## When This Sub-Skill Loads
The parent router dispatches here when the input question contains signals like:
- "What is the current state of X"
- "What exists in the X landscape"
- "Map / Document / Inventory / Survey / Catalogue"
- "List the available X"
- Field-survey or technology-landscape requests where the goal is to *describe what exists*
**Disambiguation rule** (from `research-agent/references/research-type-patterns.md`):
"What is the current adoption of X" (mapping a fact) → Descriptive. "Was X adoption successful" (judging merit) → Evaluative.
## Framework Selection
| Framework | Use When |
|---|---|
| **SPICE** | Context-specific landscape ("what is the state of testing tools in mobile-first teams") |
| **None** | Open-domain inventory or survey; no perspective filter needed |
PICO/PECO are not used for Descriptive work — there is no intervention or exposure being evaluated; the goal is enumeration.
## Output Pattern: Landscape Map
Use this pattern verbatim for the Findings section (parent skill's Phase 6 Synthesis output):
```
## Research Type: Descriptive
## Framework: [None / SPICE]
## Domain Boundaries
[Clear definition of what is and is not in scope]
## Entity Inventory
| Entity | Type | Key Properties | Source |
|--------|------|----------------|--------|
| ... | ... | ... | [S1] |
## Relationship Map
[Describe connections between entities - who uses what, what depends on what]
## State of the Field (as of [date])
- Mature / established: [...]
- Emerging: [...]
- Deprecated / declining: [...]
## Gaps in Documentation
[What exists but is undocumented, or documented inconsistently]
```
## Phase Adaptations
The parent skill's 8-phase flow applies. Descriptive-specific notes:
- **Phase 3 (Scope)**: Date range MUST be stated explicitly — "current state" is meaningless without a temporal anchor. Use "as of YYYY-MM-DD".
- **Phase 4 (Source Plan)**: Prioritize Primary sources (official docs, vendor pages, registries, standards). Secondary sources acceptable for cross-validation; Grey literature only for community-state signals (e.g., adoption surveys).
- **Phase 5 (Gather)**: Drive toward **inventory completeness**, not depth per item. Each entity gets a row; deep analysis belongs to Evaluative or Comparative follow-ups.
- **Phase 6 (Synthesis)**: The Entity Inventory is the deliverable. Avoid editorializing on what is "best" — that crosses into Evaluative.
- **Phase 7 (Bias)**: Watch for **selection bias** in entity inclusion (only well-known entities make the inventory). Counter by including a "long tail" or "lesser-known" section.
## Integrity Constraints (Descriptive-Specific)
- **No ranking or judgement.** Descriptive output describes what exists, not what is good. Comparative language ("X is better than Y") belongs in Comparative pattern.
- **Temporal anchor mandatory.** Every Descriptive output states "as of [date]" prominently. Field state changes; an undated landscape is misleading.
- **Inventory completeness over depth.** A Descriptive output that deeply covers 3 entities and ignores 12 others is mis-scoped — escalate to Evaluative or Comparative if depth is the user's goal.
## References
- Parent: `research-agent/SKILL.md` (Phase 1-8 flow, GRADE system, integrity constraints)
- `research-agent/references/research-type-patterns.md` § "Descriptive" - identification matrix, disambiguation rules
- `research-agent/references/api-research.md` - applies when the inventory includes APIs/SDKs (Descriptive landscape of an API surface)
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.