research-capture
Captures research insights, decisions, and learnings during development. Use after completing spikes, making architectural decisions, or discovering important patterns. Prompts for context and rationale, stores with embeddings for later semantic retrieval. Do NOT use for trivial notes - this is for significant findings worth surfacing later.
npx skills add majiayu000/claude-skill-registry --skill pop-research-capture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Research Capture ## Overview Capture and index research insights during development for later semantic retrieval. Creates structured entries with context, rationale, and alternatives considered. **Core principle:** Capture decisions and learnings while context is fresh. **Trigger:** After spikes, architectural decisions, significant discoveries, end of investigation ## Entry Types | Type | Use For | Examples | | ---------- | ------------------------------ | ------------------------------------------------------- | | `decision` | Architectural/design choices | "Use Redis for sessions", "Chose Hono over Express" | | `finding` | Discoveries during development | "Stripe webhook timing issue", "Race condition in auth" | | `learning` | Knowledge gained | "Astro hydration quirks", "CORS preflight gotchas" | | `spike` | Investigation results | "Evaluated 3 auth providers", "Benchmarked DB options" | ## Capture Flow ### Step 1: Determine Entry Type ``` Use AskUserQuestion tool with: - question: "What type of research entry is this?" - header: "Entry Type" - options: 1. label: "Decision" description: "Architectural or design choice made" 2. label: "Finding" description: "Discovery or insig
- Overview
- Entry Types
- Capture Flow
- Step 1: Determine Entry Type
- Step 2: Gather Content
- Step 3: Auto-detect Context
- Step 4: Confirm Tags
- Step 5: Generate and Store
- Step 6: Generate Embedding (if cloud available)
- Storage Structure
- index.json Schema
- Integration Points
- Session Capture Integration
- Dev Workflow Integration
What does the research-capture skill do?
Captures research insights, decisions, and learnings during development. Use after completing spikes, making architectural decisions, or discovering important patterns. Prompts for context and rationale, stores with embeddings for later semantic retrieval. Do NOT use for trivial notes - this is for significant findings worth surfacing later.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill pop-research-capture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.