Research
Use for source-grounded research. Two frames, inferred from the request: report — open-ended topic or whole-domain research emitting a cited markdown report (primer, survey, deep-dive literature review, or domain landscape map); opportunity — validate a named product/business/feature idea into a go/no-go memo built on Facts/Assumptions/Decisions/Risks. Triggers: 'research X', 'primer on X', 'map the X landscape', 'what's known about X', 'get me oriented in X', 'should we build X', 'validate this opportunity'. Do NOT use to review an existing artifact (prompt, plan, spec, deck), to compare a fixed set of already-named options, or to brainstorm new ideas from scratch.From its SKILL.md
npx -y skills add justinramos101/agent-skill-kit --skill researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.4 KB, 600 tokens by cl100k_base, as published. Nobody here has run it
Research
Two frames; infer the frame from the request, never ask which:
- report — no decision attached: a primer, survey, deep-dive, or whole-domain landscape map. Load
references/report.md. - opportunity — a decision attached: "should we build / enter / invest", go/no-go, sizing a named idea. Load
references/opportunity.md.
Core principle: keep the line between what is known and what is asserted visible. Every load-bearing claim is cited or marked as inference. A research branch that ends without a citation or a next test is organized procrastination, not research.
Run to completion; state assumptions inline. Ask only on a genuine blocker: the frame is undecidable, or the opportunity frame lacks a one-line opportunity statement (fan-out without scope produces disconnected dumps).
Invariants
- A vendor-aligned source is never the sole support for a claim about that vendor's own category.
- When well-triaged sources conflict, both go in the output as a named debate — silently picking one is editorializing.
- Opportunity frame: every assumption carries a falsifiable test; every severity-4 risk is resolved or becomes a kill criterion; the memo ends in go / no-go / pivot, never "more research needed".
- Cut weak citations rather than pad: ten triaged sources beat forty padded ones.
Workflow
- Scope. Restate the request as a one-sentence research question (report) or a one-line opportunity statement (opportunity), with explicit inclusions and exclusions.
- Plan the search before searching. Load the frame reference; name source types, terms, exclusions, and one stop criterion up front: saturation (new queries mostly return already-found sources), a source-count target, or a time budget.
- Search and triage. Prefer primary over secondary, seminal or recent over dated, independent over vendor-aligned, vetted over unvetted. A zero-result query is ambiguous — rewrite or broaden before recording a coverage gap.
- Synthesize. Tag every load-bearing claim H/M/L confidence and cite at the point of claim; mark synthesis ("inferred from X+Y") explicitly — never present inference as sourced. Opportunity frame: fold every branch into Facts / Assumptions / Decisions / Risks.
- Verify — one adversarial pass, max two. Re-open each cited source and confirm it says what the claim says; drop or downgrade anything unsupported. Fabricated citations survive triage; only this pass catches them.
- Emit and report the path.
docs/research/research-report-<YYYY-MM-DD>-<slug>.md(ordomain-map-…/fadr-memo-…); fall back toresearch-output/if unwritable.
What ships with it: 7 files
32.6 KB alongside SKILL.md, 1 of them executable
evals/
- activation-cases.md3.5 KB
- run-static-checks.shruns713 B
- trigger-evals.json4.7 KB
references/
- opportunity.md3.9 KB
- report.md4.2 KB
- README.md2.0 KB
- skill.json13.5 KB