research-and-summarize

Name: research-and-summarize
Author: DevelopersGlobal

64stars10forks

How to install research-and-summarize?

developersglobal/ai-agent-skills/research-and-summarize

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill research-and-summarize

Installs into the current project.

Summary

Distill complex topics into layered, actionable summaries. Start with the key insight, layer in detail, end with recommended next action.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	Information overload is the default state. This skill transforms any research task into a structured summary: headline insight first, context second, detail third, action last. Designed for decision-makers who need clarity, not comprehensiveness.
4
5	## When to Use
6
7	- Summarizing technical documentation or papers
8	- Researching a technology choice
9	- Briefing a team on a topic
10	- Distilling a long document for a specific decision
11
12	## Process
13
14	### Step 1: Define the Research Question
15
16	1. State the specific question being answered: "Should we use Kafka or RabbitMQ for our event pipeline?"
17	2. State who the answer is for and what decision it enables.
18	3. This scopes the research — don't gather information beyond what the decision needs.
19
20	Verify: Research question is specific enough to have a clear answer.
21
22	### Step 2: Gather and Evaluate Sources
23
24	4. Identify 3–5 high-quality, authoritative sources.
25	5. For each source, note: recency, authority, potential bias.
26	6. Cross-reference key claims across sources.
27	7. Flag conflicting information — don't silently pick one side.
28
29	Verify: Key claims are supported by at least 2 independent sources.
30
31	### Step 3: Write the Layered Summary
32
33	8. Headline (1 sentence): The single most important insight.
34	9. Key findings (3–5 bullets): Supporting evidence for the headline.
35	10. Context and nuance (1–2 paragraphs): Caveats, tradeoffs, conditions under which the headline doesn't hold.
36	11. What we don't know: Gaps in the available information.
37	12. Recommended action: Given the findings, what should the reader do next?
38
39	Deliver: A structured summary with all 5 sections.
40
41	### Step 4: Cite Sources
42
43	13. Every factual claim is linked to a source.
44	14. Include the date of each source (recency matters in fast-moving fields).
45
46	Verify: Every claim has a citation.
47
48	## Common Rationalizations (and Rebuttals)
49
50	\| Excuse \| Rebuttal \|
51	\|--------\|----------\|
52	\| "The topic is too complex to summarize" \| The goal is to enable a decision, not to be comprehensive. Scope to the decision. \|
53	\| "I'll just share the links" \| Links are not summaries. Distillation is the value. \|
54
55	## Verification
56
57	- [ ] Research question defined before research begins
58	- [ ] Key claims cross-referenced across 2+ sources
59	- [ ] Summary has: headline, findings, context, unknowns, action
60	- [ ] Every factual claim has a citation with date
61
62	## References
63
64	- [think-before-coding skill](../think-before-coding/SKILL.md)
65	- [idea-to-spec skill](../idea-to-spec/SKILL.md)

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

research-and-summarize

64stars10forks

View on GitHub

How to install research-and-summarize?

developersglobal/ai-agent-skills/research-and-summarize

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill research-and-summarize

Installs into the current project.

Summary

Distill complex topics into layered, actionable summaries. Start with the key insight, layer in detail, end with recommended next action.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	Information overload is the default state. This skill transforms any research task into a structured summary: headline insight first, context second, detail third, action last. Designed for decision-makers who need clarity, not comprehensiveness.
4
5	## When to Use
6
7	- Summarizing technical documentation or papers
8	- Researching a technology choice
9	- Briefing a team on a topic
10	- Distilling a long document for a specific decision
11
12	## Process
13
14	### Step 1: Define the Research Question
15
16	1. State the specific question being answered: "Should we use Kafka or RabbitMQ for our event pipeline?"
17	2. State who the answer is for and what decision it enables.
18	3. This scopes the research — don't gather information beyond what the decision needs.
19
20	Verify: Research question is specific enough to have a clear answer.
21
22	### Step 2: Gather and Evaluate Sources
23
24	4. Identify 3–5 high-quality, authoritative sources.
25	5. For each source, note: recency, authority, potential bias.
26	6. Cross-reference key claims across sources.
27	7. Flag conflicting information — don't silently pick one side.
28
29	Verify: Key claims are supported by at least 2 independent sources.
30
31	### Step 3: Write the Layered Summary
32
33	8. Headline (1 sentence): The single most important insight.
34	9. Key findings (3–5 bullets): Supporting evidence for the headline.
35	10. Context and nuance (1–2 paragraphs): Caveats, tradeoffs, conditions under which the headline doesn't hold.
36	11. What we don't know: Gaps in the available information.
37	12. Recommended action: Given the findings, what should the reader do next?
38
39	Deliver: A structured summary with all 5 sections.
40
41	### Step 4: Cite Sources
42
43	13. Every factual claim is linked to a source.
44	14. Include the date of each source (recency matters in fast-moving fields).
45
46	Verify: Every claim has a citation.
47
48	## Common Rationalizations (and Rebuttals)
49
50	\| Excuse \| Rebuttal \|
51	\|--------\|----------\|
52	\| "The topic is too complex to summarize" \| The goal is to enable a decision, not to be comprehensive. Scope to the decision. \|
53	\| "I'll just share the links" \| Links are not summaries. Distillation is the value. \|
54
55	## Verification
56
57	- [ ] Research question defined before research begins
58	- [ ] Key claims cross-referenced across 2+ sources
59	- [ ] Summary has: headline, findings, context, unknowns, action
60	- [ ] Every factual claim has a citation with date
61
62	## References
63
64	- [think-before-coding skill](../think-before-coding/SKILL.md)
65	- [idea-to-spec skill](../idea-to-spec/SKILL.md)

People who liked this also viewed

6 picks

Type