Borrowing it
Nothing to install: this file belongs to Chrisissorry/lazyslides. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Chrisissorry/lazyslides/develop/.claude/skills/research-topic/SKILL.mdgit clone --depth 1 https://github.com/Chrisissorry/lazyslidesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/chrisissorry/lazyslides/research-topic)<a href="https://agentmods.dev/skills/chrisissorry/lazyslides/research-topic"><img src="https://agentmods.dev/badge/skills/chrisissorry/lazyslides/research-topic/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chrisissorry/lazyslides/research-topic"><img src="https://agentmods.dev/badge/skills/chrisissorry/lazyslides/research-topic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00578 |
| Opus 5 | $0.00016 | $0.00289 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
research-topic scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Research Topic
You are helping the user research a topic to build a data-driven presentation.
Step 1: Gather Research Parameters
Ask the user for:
- Topic — what is the presentation about?
- Angle — what perspective or thesis? (e.g., "why companies should adopt X")
- Audience — who will watch this? (affects depth and jargon level)
- Depth — quick overview (5-10 data points) or deep dive (20+)?
Step 2: Research
Search the web for:
- Statistics — recent numbers, percentages, growth rates
- Quotes — expert opinions, notable statements
- Comparisons — before/after, competitor analysis, benchmarks
- Timelines — key events, milestones, evolution
- Case studies — real-world examples with outcomes
Prioritize recent sources (last 2 years). Always capture the source name, URL, and date.
Step 3: Organize Findings
Structure findings into categories:
## Key Statistics
- [stat] — Source (Year)
## Notable Quotes
- "[quote]" — Author, Title (Source)
## Comparisons
- [comparison point] — Source
## Timeline / Milestones
- [date]: [event] — Source
## Case Studies
- [company/example]: [outcome] — Source
Step 4: Save Research
Save the organized findings as research.md in the target presentation folder:
presentations/{name}/research.md
Step 5: Suggest Template Mapping
For each finding, suggest which LazySlides template would best present it:
| Finding | Suggested Template | Rationale |
|---|---|---|
| Key statistic | metrics |
Numeric data with colored cards |
| Quote | quote |
Attribution and styling |
| Comparison | comparison |
Side-by-side table |
| Timeline | timeline |
Chronological events |
| Case study | split or content |
Narrative with supporting image |
Step 6: Next Steps
Offer the user:
/create-outlineto structure a full presentation from this research/add-slideto add individual data points to an existing deck
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 84 lines · 33 tokens per session scan A a5536e70c545
research-topic is a skill published in the GitHub repository Chrisissorry/lazyslides (5 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 578 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…