research-ideation

research-ideation is a skill for Claude Code from gioviat/research-toolkit. It costs 55 tokens per session (483 once invoked), scanned A, original, MIT.

A research-idea development guide for creating and comparing specific, testable research questions. Research questions are focused questions that can be answered with evidence rather than broad topics.

In plain words
What is it for?
Use it to generate several candidate questions, connect them to observations or gaps in existing papers, assess why they might be true, and rank their strengths and weaknesses.
Why use it?
It reduces the risk of choosing an interesting-sounding idea without checking whether it is testable, relevant, or supported by prior work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the research-toolkit plugin — 7 skills, 5 agents, 1 hook shipped together

Good fit Use it to generate several candidate questions, connect them to observations or gaps in existing papers, assess why they might be true, and rank their strengths and weaknesses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gioviat/research-toolkit/research-ideation
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 gioviat/research-toolkit --skill research-ideation
Clone the repo
git clone --depth 1 https://github.com/gioviat/research-toolkit

Made for: Claude Code.

Or install research-toolkit, the plugin that ships this one along with the rest of its 7 skills, 5 agents, 1 hook.

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-ideation

README.md
[![agentmods](https://agentmods.dev/badge/skills/gioviat/research-toolkit/research-ideation.svg)](https://agentmods.dev/skills/gioviat/research-toolkit/research-ideation)
Your own site
<a href="https://agentmods.dev/skills/gioviat/research-toolkit/research-ideation"><img src="https://agentmods.dev/badge/skills/gioviat/research-toolkit/research-ideation.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 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.00055 $0.00483
Opus 5 $0.00028 $0.00242
Sonnet 5 $0.00011 $0.00097
Haiku 4.5 $0.00006 $0.00048

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

Security

Grade A, and why

research-ideation 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 8d 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.

skills/research-ideation/SKILL.md · 26 lines

What it actually says

Research ideation

Where ideas come from

Start from something concrete: an anomaly in your own results, a gap recorded in papers/related-work/, an assumption every existing method makes that might not be necessary, or a mismatch between theory and observed behavior. Not from "what's trendy".

Procedure

  1. Generate at least 3–5 candidate questions before evaluating any of them. Evaluating the first idea before alternatives exist anchors the session on it.
  2. For each candidate, fill in every field below. A field that cannot be filled is itself a verdict on the candidate.
  3. Rank the candidates and state plainly which are weak and why. Your own ideas get no false balance: if one candidate is clearly better, say so; if all are weak, say that.

Required fields per candidate

  • Question: falsifiable and specific. Not "can X help Y" but "does X improve metric M by an amount that matters under condition C".
  • Why it might be true, and why now: the mechanism or observation suggesting it, and what changed (new data, tool, or result) that makes it tractable today.
  • Closest prior work: found by actually searching (literature-review skill or literature-scout agent), never asserted from memory. State exactly how the candidate differs. "Nobody has done this" without a recorded search is not a novelty claim.
  • Cheapest decisive experiment: the smallest experiment whose outcome would change your belief in the question. If the cheapest informative experiment is expensive, that is a cost of the idea — record it.
  • Kill criterion: the result that would make you drop the idea, stated before running anything.
  • If true / if false: what changes in either case. If nothing changes when false, the question may not be worth asking.

Output

One doc per surviving candidate at ideas/<slug>.md with the fields above, plus the ranking rationale across candidates. Have the skeptical-reviewer agent review the doc before any implementation starts.

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. 8d ago First seen · 26 lines · 55 tokens per session scan A 26f70d65cd3b

Subscribe to this mod's changes

research-ideation is a skill published in the GitHub repository gioviat/research-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 483 once invoked, about $0.0003 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens