research
/research
Gather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior. Each finding cites a source; unsourced claims are flagged, never written as fact. Triggers when a spec decision hinges on a library/API/best practice the agent is unsure of, when the user says "research this", "what's the best lib for…", "check current best practice", or invokes /ck:research. Defers the §R write to the spec skill.
- Author
- juliusbrussee ↗
- Repository
- cavekit ↗
- Licence
- MIT
- Last repository change
- 15.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 15.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Gather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior. Each finding cites a source; unsourced claims are flagged, never written as fact. Triggers when a spec decision hinges on a library/API/best practice the agent is unsure of, when the user says "research this", "what's the best lib for…", "check current best practice", or invokes /ck:research. Defers the §R write to the spec skill.
Triggers from the description
Original author description
Gather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior. Each finding cites a source; unsourced claims are flagged, never written as fact. Triggers when a spec decision hinges on a library/API/best practice the agent is unsure of, when the user says "research this", "what's the best lib for…", "check current best practice", or invokes /ck:research. Defers the §R write to the spec skill.
How it works
- WHEN TO RESEARCH
- FOUR STEPS
- SOURCE DISCIPLINE
- WHEN TO STOP
- BOUNDARIES
SKILL.md preview
--- name: research description: | Gather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior. Each finding cites a source; unsourced claims are flagged, never written as fact. Triggers when a spec decision hinges on a library/API/best practice the agent is unsure of, when the user says "research this", "what's the best lib for…", "check current best practice", or invokes /ck:research. Defers the §R write to the spec skill. --- # research — external knowledge → §R **Every finding cites a source. No source → flag it `?`, never write a guess as fact.** "Process without library context gives you well-organized hallucinations." Build invents a plausible-but-wrong API & §B fills with avoidable bugs. Research is the external oracle: pull the real fact once, log it caveman, never re-derive. ## WHEN TO RESEARCH - A §C/§I/§V decision hinges on a lib, API, version, or pattern you are unsure of. - You are about to assume how an external dependency behaves. - The idea touches a domain with real prior art (auth, payments, crypto, rate-limit). - `/grill` parked a `?` that the outside world must answer. Skip when the build touches only code you already wrote. Research scales to the unknown, ⊥ to habit. ## FOUR STEPS ### 1. SCOPE Turn the unknown into 1-3 concrete questions. Vague "research auth" → "JWT lib for Node ESM, maintained?" + "refresh-token rotation: current best practice?". A scoped question gets a citable answer; a vague one gets an essay. ### 2. GATHER Use web search / docs tools. Prefer primary sources: official docs, the repo, the RFC, the paper. Two independent sources beat one confident blog. For a big sweep, spawn a sub-agent so the raw pages never touch this context — it returns only the distilled finding + source. ### 3. DISTILL Crush each answer to one caveman line + its source. Drop the prose. The §R row is the memory; the tab you read is not. > R3|refresh token|rotate on use, revoke family on reuse-detect|datatracker.ietf.org/doc/html/rfc6819#section-5.2.2.3 ### 4. HAND OFF Emit the §R rows & hand to the **spec** skill to append. If a finding changes a constraint or interface, note the §C/§I edit for spec too. Research proposes; spec writes. ## SOURCE DISCIPLINE - Cite a URL, repo, RFC, or paper per row. Verbatim identifiers/versions. - Could not verify → write the row but flag `?` in the finding & say so. An unverified claim labeled honestly is fine; one disguised as fact is a future §B. - Conflicting sources → log both, let the user pick. ⊥ silently average them. ## WHEN TO STOP Done when every scoped question has a sourced §R row (or an honest `?`), and no build decision still rests on an unchecked assumption. ⊥ research past the questions you scoped — that is just burning the attention budget. ## BOUNDARIES - ⊥ write SPEC.md. Hand §R rows to spec. - ⊥ write a finding as fact without a source. - ⊥ dump raw pages into context or §R. Distill or it does not land. - ⊥ research what you can read in the repo. Local truth > web guess.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · juliusbrussee/cavekit | 90 | MIT |
| Insilico-org/plsi | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
| udecode/plate | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| taishi-i/awesome-japanese-nlp-resources | 100 | CC0-1.0 |
| niekcandaele/claude-helpers | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2058415aeb45 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86best-practice-research
Use when a technical decision depends on current official documentation, upstream source, standards, release notes, or comparative best-practice evidence. - 84research-topic
Research external documentation and best practices. Use when user says "look up the docs for this library", "research best practices for implementing caching", "how do other projects handle authentication", "check the official documentation for this API", "compare our… - 100research-context
Use when a decision needs current external/web info (library best-practices, version behavior, migration guidance) rather than local sources — runs grounded web research and returns a cited brief. - 100research-methodology
Systematic gathering of accurate, version-specific documentation. TRIGGER when: researching a new API, library, or best practice before implementation. SKIP: turning findings into a plan (use planning-methodology); writing proposal.md (use spec-research). - 100external-research
Search external documentation, web resources, and best practices. Use when gathering information about open-source libraries, AWS services, industry patterns, or external tools. - 100research-and-ingest
Find authoritative sources on the web (or via documentation MCP servers like Context7/DeepWiki), download or snapshot them when allowed, normalize them into clean Markdown, and stage them for the library-wiki. Use whenever a new library/spec/API/standard is being added, a wiki…