research-a-topic

research-a-topic is a skill for Claude Code, Codex from akiotanaka847/qaio-desktop. It costs 49 tokens per session (1,336 once invoked), scanned A, original, MIT.

A research tool that gathers information about a topic into a structured brief and cites the sources it used. It is meant to support marketing decisions and later writing.

In plain words
What is it for?
Use it to understand a market or category, investigate a topic, find evidence for a campaign, or prepare material for blog posts and content plans.
Why use it?
It reduces the time spent searching, sorting, and checking information before deciding what to say or do.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to understand a market or category, investigate a topic, find evidence for a campaign, or prepare material for blog posts and content plans.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akiotanaka847/qaio-desktop/research-a-topic
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add akiotanaka847/qaio-desktop --skill research-a-topic
Clone the repo
git clone --depth 1 https://github.com/akiotanaka847/qaio-desktop

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for research-a-topic

README.md
[![agentmods](https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/research-a-topic/github.svg)](https://agentmods.dev/skills/akiotanaka847/qaio-desktop/research-a-topic)
Your own site
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/research-a-topic"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/research-a-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.

agentmods 80×15 button for research-a-topic

Your own site · 80×15
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/research-a-topic"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/research-a-topic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,336 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01336
Opus 5 $0.00024 $0.00668
Sonnet 5 $0.00010 $0.00267
Haiku 4.5 $0.00005 $0.00134

Measured 10d ago against content hash c333ff53c970, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

research-a-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 10d 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.

store/agents/marketing/.agents/skills/research-a-topic/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Research A Topic

Source template: Gumloop "AI Research Agent with Automated Report Generation". Adapted for hand-off to other four marketing agents, not 20-page investor memos.

When to use

  • "research {topic}" / "I need a brief on {topic}" / "what's state of {topic}".
  • "summarize what's happening in {category}".
  • Called implicitly by other skills (plan-a-campaign, watch-my-competitors, profile-my-customer) when they hit an evidence gap that needs a dedicated research run.

Connections I need

I run external work through Composio. Before this skill runs I check that the categories below are linked. Missing -> I name the category, ask you to connect it from the Integrations tab, stop.

  • Web search (Exa or Perplexity) - the engine that finds and ranks sources. Required - no useful fallback, I need a search index to start from.
  • Web scrape (Firecrawl) - optional, fetches full text cleanly. If not connected I fall back to basic HTTP fetch on each source URL, rougher but enough to pull quotes from static pages.

If web search isn't connected I stop. The scrape fallback keeps me going on its own.

Information I need

I read your marketing context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.

  • Your positioning - Required. Why I need it: a brief that doesn't filter for your ideal customer and category is just generic internet research. If missing I ask: "Want me to draft your positioning first? It's one skill, takes about five minutes."
  • The research question - Required. Why I need it: scope creep makes briefs useless. If missing I ask: "What's the one question this brief should answer, and what decision does it unblock?"
  • Depth - Optional, default standard. If missing I ask: "How deep should I go, a fifteen-minute scan, an hour-long dive, or a deep run? If you don't have a preference I keep going with standard depth."

Read the full file on GitHub · 91 lines

Changes

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.

  1. 10d ago First seen · 91 lines · 49 tokens per session scan A c333ff53c970

Subscribe to this mod's changes

research-a-topic is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 1,336 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.

Related

Other skills, from other repositories

magazine-web-ppt

For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.

nexu-io/open-design · 67 tokens

html-ppt-zhangzara-coral

OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.

nexu-io/open-design · 55 tokens

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad…

coreyhaines31/marketingskills · 175 tokens

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives…

coreyhaines31/marketingskills · 220 tokens

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership…

coreyhaines31/marketingskills · 92 tokens

offers

When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,'…

coreyhaines31/marketingskills · 233 tokens