Agent skill

Research Ideation

by EvoScientist in EvoScientist/EvoSkills

End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update…

Apache-2.0Auto-check passedAgent Workflows

Install Research Ideation

skills CLI
$ npx skills add EvoScientist/EvoSkills --skill research-ideation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install EvoScientist/EvoSkills research-ideation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/EvoScientist/EvoSkills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/research-ideation .claude/skills/research-ideation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
research-ideation
GitHub stars
476
Used in
2 other repos
Token cost
~3.9k tokens
SKILL.md length
1,647 words
Files
12 (incl. references, assets)
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update…

  • Works in 9 steps: Load Prior Knowledge from evo-memory → Define a Long-Term Research Goal → Literature Grounding (via paper-navigator) → …
  • : user wants to find a research direction
  • SKILL.md covers When to Use, When NOT to Use, Step 0: Load Prior Knowledge… and Step 1: Define a Long-Term…, plus 12 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Research Ideation is an agent skill from EvoScientist/EvoSkills. End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update evo-memory (IDE) → user selects direction → expand into manuscript-quality proposal. Use when: user wants to find a research direction, brainstorm ideas, evaluate idea novelty, design a novel solution, rank/compare research ideas, or generate a research proposal. Do NOT use for finding/searching/reading papers (use…

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files and assets (for example `assets/direction-summary-template.md`, `assets/idea-candidate-template.md` and `assets/paper-summary-template.md`).

It sits in Agent Workflows, covering Brainstorming. The repository describes itself as: 🧬 Extend EvoScientist with Installable Skill & Knowledge Packs. The licence is Apache-2.0.

When your agent uses it

  • : user wants to find a research direction
  • Brainstorm ideas
  • Evaluate idea novelty
  • Design a novel solution

Example prompts

  • “/research-ideation”

Requirements

  • Pre-approved tools (allowed-tools): write_file, edit_file, read_file, think_tool, execute

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Load Prior Knowledge from evo-memory
  2. Define a Long-Term Research Goal
  3. Literature Grounding (via paper-navigator)
  4. Generate Ideas
  5. Refine Ideas
  6. ELO Tournament → Present Top-3
  7. Update evo-memory
  8. Expand into Proposal
  9. Validate and Iterate

What it can do on your machine

Read from SKILL.md and the folder at commit 9a9f8cf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • write_file
    • edit_file
    • read_file
    • think_tool
    • execute

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Research Ideation loads about 3.9k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 158 tokens; SKILL.md has 1,647 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~158
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from EvoScientist/EvoSkills at commit 9a9f8cf, republished under its Apache-2.0 licence (© EvoScientist). 1,647 words, ~3,930 tokens.

Download SKILL.mdSave it as .claude/skills/research-ideation/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
research-ideation
description
End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update evo-memory (IDE) → user selects direction → expand into manuscript-quality proposal. Use when: user wants to find a research direction, brainstorm ideas, evaluate idea novelty, design a novel solution, rank/compare research ideas, or generate a research proposal. Do NOT use for finding/searching/reading papers (use paper-navigator), literature survey reports (use research-survey), or planning a paper (use paper-planning).
allowed-tools
write_file, edit_file, read_file, think_tool, execute
metadata.author
EvoScientist
metadata.version
2.1.2
metadata.tags
core, research, ideation, tournament, proposal

Research Ideation

From research goal to ranked ideas and a detailed proposal.

Step 0: Load evo-memory (M_I)
    ↓
Step 1: Define Goal
    ↓
Step 2: Literature Grounding (MUST use paper-navigator scripts)
    ↓
Step 3: Generate Ideas (3 directions × 3 personas)
    ↓
Step 4: Refine Ideas (3 tracks × N iterations)
    ↓
Step 5: ELO Tournament → Present Top-3 to User
    ↓
Step 6: Update evo-memory (IDE)
    ↓
User Selects
    ↓
Step 7: Expand into Proposal
    ↓
Step 8: Validate and Iterate

When to Use

  • User wants to find a research direction or brainstorm research ideas
  • User wants to evaluate whether an idea is novel or worth pursuing
  • User wants to rank or compare multiple research ideas
  • User wants to generate a research proposal from an idea

When NOT to Use

  • Finding/reading papers → use paper-navigator
  • Literature survey report → use research-survey
  • Planning a paper (story design, experiment plan) → use paper-planning

Step 0: Load Prior Knowledge from evo-memory

Before any ideation begins, load Ideation Memory (M_I) from prior research cycles:

  1. Read M_I at /memory/ideation-memory.md (refer to evo-memory skill)
  2. Select the top-2 entries (k_I=2) most relevant to the user's current goal by comparing each entry's Summary and Retrieval Tags against the goal
  3. Feasible directions from prior cycles → use as seeds in Step 3 (incorporate as candidate research directions alongside new ones; Step 3 still selects exactly 3 directions)
  4. Unsuccessful directions marked as fundamental failures → use during idea pruning in Step 4 (prune any idea that matches a fundamental failure pattern)
  5. If M_I doesn't exist yet (first cycle), skip this step

This step prevents repeating known dead ends and builds on prior successes across research cycles.

Step 1: Define a Long-Term Research Goal

Start with a goal that has both scientific and practical value. Ambitious enough for multiple papers, concrete enough to guide daily decisions.

Ask: "What is the ultimate form of this research direction? What would the world look like if this problem were fully solved?"

Step 2: Literature Grounding (via paper-navigator)

Invoke paper-navigator (Workflow 9: Ideation Support) to collect 30-50 relevant papers. Do NOT skip this step or substitute with general knowledge — ideas must be grounded in real papers.

CRITICAL: All paper discovery in this step MUST use the paper-navigator skill and its scripts (scholar_search, citation_traverse, arxiv_monitor, recommend, etc.). Using WebSearch, WebFetch, or any generic web search tool for finding papers is PROHIBITED. Generic web search returns blog posts, news articles, and low-quality results — only paper-navigator provides access to Semantic Scholar, arXiv, citation graph traversal, and academic recommendations needed for rigorous literature grounding.

Build Challenge-Insight Tree

From the collected papers, construct a challenge-insight tree — a many-to-many mapping between technical challenges and the insights/techniques that address them:

  • Extract challenges: From each paper, what technical problem does it solve?
  • Extract insights: What technique or key idea does it use?
  • Map connections: Which insights address which challenges?

How this drives ideation:

  • Challenges with few insights → unsolved problem (candidate for Step 3)
  • Insights not yet applied to a challenge → cross-domain transfer opportunity (candidate for Step 4)
  • Challenges with many insights → well-studied, avoid unless you have a fundamentally new angle

Also generate a condensed literature review synthesis as context for idea generation (for full surveys use research-survey).

See references/literature-tree.md for construction methodology.

Execution rule: Do NOT generate ideas without real paper grounding. The tree must reference actual papers with titles, authors, and findings. Paper search MUST go through paper-navigator — never use WebSearch/WebFetch as a shortcut.

Step 3: Generate Ideas

Generate 3 initial research ideas from 3 distinct research directions, grounded in the literature.

Three Personas
PersonaFocus
InnovatorNovelty & creativity — groundbreaking, high-risk/high-reward
PragmatistFeasibility — realistic, clearly executable
CriticScientific value — advances understanding, rigorous
Process
  1. Analyze literature + challenge-insight tree → identify 3 fundamentally different research directions
  2. Generate one idea per direction using Innovator persona
  3. Each idea must follow one of two methodological paths:
    • Path 1 (Focused Contribution): Single new component; clean hypothesis
    • Path 2 (System Contribution): Tight causal interaction between components; emergent capability
Idea Format
# Research Idea: [Concise Title]

## Core Idea
[One paragraph: the proposal + which research direction it addresses]

## Validation Plan
[Concrete experiment outline: datasets, baselines, metrics]

Step 4: Refine Ideas

Run 3 parallel refinement tracks — one per initial idea. Each track uses all 3 personas.

For each track:
  For N=3 iterations:
    1. Evaluate current best idea (novelty, feasibility, impact, alignment)
    2. All 3 personas generate refined versions based on evaluation
    3. Pick the best refinement as seed for next iteration
  Track champion = the refinement picked in the final iteration
5 Evolution Strategies
  1. Enhancement through Grounding: Strengthen with literature citations
  2. Improving Coherence: Fix logical flaws in the mechanism
  3. Inspiration and Combination: Combine with a different concept from literature
  4. Simplification: Strip down to a clean, testable hypothesis
  5. Literature-Driven Pivot: Abandon the mechanism; propose a new approach from literature

Critical rule: If evaluation says the approach is a dead-end, the persona MUST pivot — refinement is not restricted to patching.

Logical Cohesion Principles
  • Too many variables → Focus via Subtraction: isolate the most promising variable
  • Disconnected components → Justify via Strong Correlation: build explicit causal links

Step 5: ELO Tournament → Present Top-3

Rank the 3 track champions through pairwise comparison, then present all three, ranked, to the user for selection. The tournament orders the champions and records why; it does not eliminate any — each champion is a different research direction, and the user chooses between directions.

Four Dimensions
DimensionWhat It Measures
NoveltyHow different from existing published work?
FeasibilityCan this be implemented within reasonable resources?
RelevanceDoes this address an important problem aligned with the goal?
ClarityIs the idea well-defined enough to start immediately?
Tournament
  • Starting Elo: 1500 | K-factor: 32
  • Round-robin: every champion meets the other two once (3 matches)
  • Per match: score both ideas on the four dimensions → higher composite wins → update Elo
  • Sort by final Elo. If ratings are equal, or each champion won exactly one match, order by mean composite score instead, then by track order
  • See references/elo-ranking-guide.md for rubric and formula
Present Top-3 to User

After the tournament, present the top-3 ideas with both a comparison table and the full refined idea for each. This ensures the user sees the concrete, actionable version of each idea — not just a summary.

Part 1: Comparison Table
## Top-3 Research Ideas (ranked by ELO)

| Rank | Title | Core Mechanism | Novelty | Feasibility | Relevance | Clarity | ELO |
|------|-------|---------------|---------|-------------|-----------|---------|-----|
| 1 | ... | ... | 9 | 7 | 8 | 8 | 1531 |
| 2 | ... | ... | 7 | 9 | 8 | 7 | 1500 |
| 3 | ... | ... | 8 | 6 | 9 | 7 | 1469 |

Each dimension column is the idea's mean score across its two matches.

Part 2: Full Refined Ideas

For each of the top-3, present the refined idea using the same structured format as Step 3, plus a refinement summary:

# Refined Idea [Rank]: [Concise Title]

## Core Idea
[One paragraph: the refined proposal — this should reflect ALL changes from Step 4 refinement,
not the original Step 3 version]

## Validation Plan
[Concrete experiment outline updated with refinement insights: datasets, baselines, metrics,
key ablations identified during refinement]

## Refinement Summary
[Brief paragraph summarizing what changed from the initial idea and why:
- What was simplified or removed (and why)
- What was added or concretized (and why)
- Which persona drove the most impactful change
- Key risk mitigations added during refinement]

This section is mandatory — do NOT skip the full refined ideas or collapse them into the comparison table. The user needs to see the complete, refined version to make an informed selection.

Show full SKILL.md (673 more words)Show less
Part 3: Selection Prompt
Which idea would you like to develop into a full proposal? (1/2/3, or combine elements)

After presenting top-3, trigger Step 6 (evo-memory IDE) before finalizing user selection. The user may:

  • Pick one of the top-3
  • Ask to combine elements from multiple ideas
  • Request modifications before expanding
  • Ask to regenerate with different constraints

Step 6: Update evo-memory

After the tournament and before the user selects, trigger evo-memory IDE (Idea Direction Evolution):

  1. Save the top-3 directions to /direction-summary.md
  2. Trigger IDE protocol via evo-memory skill with the direction summary
  3. Each top direction is added to M_I as a feasible direction with its ELO score
  4. Any ideas that were clearly unworkable during refinement (Step 4) are recorded as unsuccessful directions with failure classification (fundamental vs implementation)

This ensures future ideation cycles benefit from what was learned in this cycle.

Step 7: Expand into Proposal

After the user selects an idea, expand it into a manuscript-quality research proposal. This is a two-phase process because different fields require different proposal structures.

Phase 1: Generate a Domain-Specific Template

Before writing, first generate a proposal template tailored to the user's field:

  1. Identify the field from the research goal and literature
  2. Start with universal sections (Abstract, Problem, Related Work, Method, Evaluation, Conclusion)
  3. Add field-specific sections (e.g., Ethics/IRB for medical research, Safety analysis for chemistry, Statistical power analysis for clinical trials, Ablation design for ML)
  4. Adapt terminology to the field's conventions (e.g., "Study Design" in medicine, "Methodology" in social sciences, "Proposed Method" in engineering)

See assets/proposal-template.md for the complete field-specific section guide and writing instructions.

Phase 2: Write the Proposal

Fill the generated template following these universal principles:

  • Write for a top-tier reviewer in the field — every claim supported, every design justified
  • Avoid variable confusion: clearly isolate the core contribution
  • Match the field's rigor standards (math for quantitative fields, protocols for experimental fields, coding schemes for qualitative fields)
  • Anticipate skeptical reviewer questions proactively

See references/proposal-extension.md for detailed section guidance.

Step 8: Validate and Iterate

Run experiments on representative data. If the approach fails, return to Step 3 or Step 4 with updated knowledge. See experiment-craft for systematic debugging.


Counterintuitive Rules

  1. Problem selection > solution design: Choosing WHAT to solve matters more than HOW
  2. Pursue new failure cases, not incremental improvements: Find settings where existing methods break
  3. If a well-established solution exists, switch problems: Improvement space is too small
  4. Technology is creative combination, not concatenation: Simple A→B pipelines are not contributions
  5. Quantity before quality in generation: In every refinement round all three personas write their version before any of them is evaluated — 27 versions across the three tracks for 3 champions
  6. Feasibility is not optional: Brilliant but infeasible ideas waste research cycles
  7. The tournament finds surprises: Trust rankings over gut feeling

Dependency: paper-navigator

All paper discovery goes through paper-navigator. This skill does not search for papers itself. Using WebSearch, WebFetch, or any generic search tool to find papers is PROHIBITED — these tools cannot access Semantic Scholar, citation graphs, or academic recommendation systems. Always use paper-navigator and its scripts (scholar_search, citation_traverse, arxiv_monitor, recommend, trending, etc.) for all paper discovery needs in Steps 2, 3, and 4.

StepRequires paper-navigator for
Step 2Collect 30-50 relevant papers for literature tree construction
Step 3Verify no well-established solution exists for selected problems
Step 4Cross-domain search for transferable techniques during refinement

evo-memory Integration

WhenActionDetails
Step 0 (before ideation)Read M_ILoad /memory/ideation-memory.md, select top-2 relevant entries, use feasible directions as seeds, avoid fundamental failures
Step 6 (after tournament)Write M_I via IDESave top-3 directions with ELO scores as feasible; save dead-end ideas as unsuccessful with failure classification

Handoff

ToWhenKey Artifacts
paper-planningProposal complete (Step 7) → plan paper structure/research-proposal.md, /direction-summary.md
experiment-pipelineProposal complete (Step 7) → start experiments/research-proposal.md, /direction-summary.md
evo-memoryAfter tournament (Step 6) → update Ideation Memory via IDE protocol/direction-summary.md

References & Assets

TopicFile
Literature tree constructionreferences/literature-tree.md
Problem selection frameworkreferences/problem-selection.md
Solution design methodologyreferences/solution-design.md
ELO formula & rubricreferences/elo-ranking-guide.md
Proposal section guidancereferences/proposal-extension.md
Idea candidate templateassets/idea-candidate-template.md
Ranking scorecardassets/ranking-scorecard-template.md
Direction summaryassets/direction-summary-template.md
Proposal example (E-FNO)assets/proposal-template.md

© EvoScientist, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (references, assets) in skills/research-ideation of EvoScientist/EvoSkills.

  • SKILL.md
  • assets/direction-summary-template.md
  • assets/idea-candidate-template.md
  • assets/paper-summary-template.md
  • assets/proposal-template.md
  • assets/ranking-scorecard-template.md
  • references/elo-ranking-guide.md
  • references/literature-tree.md
  • references/paper-reading.md
  • references/problem-selection.md
  • references/proposal-extension.md
  • references/solution-design.md

Open the folder on GitHubat commit 9a9f8cf

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in EvoScientist/EvoSkills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Research Ideation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Research Ideation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Research Ideation this skillEvoScientist/EvoSkills4762 repos~3.9kAutomated safety check: PassApache-2.0
Brainstormingxpinjection/test-driven-spring-boot11254 repos~2.6kAutomated safety check: PassMIT
Typesafe AIOpenAgentsInc/openagents4559 repos~2.5kAutomated safety check: PassMIT
Yao Meta Skillyaojingang/yao-meta-skill2.7k—~768Automated safety check: PassMIT
Trellis StartROYIANS/foliq-print-template-designer1356 repos~646Automated safety check: PassMIT
Brainstorming Before BuildingjnMetaCode/superpowers-zh8.3k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Brainstorming

    xpinjection/test-driven-spring-boot

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.

    112 GitHub starsUsed in 54 repos~2.6k tokens
    Agent WorkflowsAuto-check passed
  • Typesafe AI

    OpenAgentsInc/openagents

    Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.

    455 GitHub starsUsed in 9 repos~2.5k tokens
    Agent WorkflowsAuto-check passed
  • Yao Meta Skill

    yaojingang/yao-meta-skill

    Create, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts.

    2.7k GitHub stars~768 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Trellis Start

    ROYIANS/foliq-print-template-designer

    Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/.

    135 GitHub starsUsed in 6 repos~646 tokens
    Agent WorkflowsAuto-check passed
  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Om Brainstorm

    go-musicfox/go-musicfox

    Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill.

    2.6k GitHub starsUsed in 1 repo~1.6k tokens
    Agent WorkflowsAuto-check passed

More from EvoScientist/EvoSkills

All 16 skills in this repo
  • Evomath Tao

    EvoScientist/EvoSkills

    A skill your agent uses whenever the user submits a non-trivial mathematical claim that needs a rigorous proof or audit.

    476 GitHub starsUsed in 2 repos~3.8k tokens
    Auto-check passed
  • Paper Figures

    EvoScientist/EvoSkills

    A skill your agent uses to produce standalone, publication-ready PNG graphics and reproducible matplotlib scripts from tabular data (CSVs or DataFrames).

    476 GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed
  • Experiment Iterative Coder

    EvoScientist/EvoSkills

    Iterative code refinement through plan → code → evaluate → refine cycles.

    476 GitHub starsUsed in 3 repos~2.5k tokens
    Auto-check passed
  • Paper Planning

    EvoScientist/EvoSkills

    Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design…

    476 GitHub starsUsed in 3 repos~2.4k tokens
    Auto-check passed
  • Research Survey

    EvoScientist/EvoSkills

    Generates structured literature survey reports from collected papers using a multi-stage pipeline: outline generation (query-type adaptive) → draft survey → section-by-section expansion → summary…

    476 GitHub starsUsed in 3 repos~2.5k tokens
    Auto-check passed
  • Paper Navigator

    EvoScientist/EvoSkills

    Find and read academic papers (S2 + arXiv). An agent skill from EvoScientist/EvoSkills.

    476 GitHub stars~6.3k tokensUpdated 8 days ago
    Auto-check: notes

Categories

Questions about Research Ideation

What does Research Ideation do?

End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update…. Research Ideation is an agent skill from EvoScientist/EvoSkills. End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update evo-memory (IDE) → user selects direction → expand into manuscript-quality proposal.

When should I use Research Ideation?

Research Ideation fits situations like: : user wants to find a research direction; brainstorm ideas; evaluate idea novelty; design a novel solution.

How do I install Research Ideation in Claude Code?

Run `npx skills add EvoScientist/EvoSkills --skill research-ideation -a claude-code`. Or copy the skill folder (skills/research-ideation in EvoScientist/EvoSkills) into .claude/skills/research-ideation in your project. Claude Code loads it when a task matches its description.

How do I install Research Ideation in Codex?

Run `npx skills add EvoScientist/EvoSkills --skill research-ideation -a codex`. Or copy the skill folder (skills/research-ideation in EvoScientist/EvoSkills) into .agents/skills/research-ideation in your project. Codex loads it when a task matches its description.

Can I use Research Ideation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EvoScientist/EvoSkills --skill research-ideation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/research-ideation, .gemini/skills/research-ideation, .github/skills/research-ideation and .opencode/skills/research-ideation in your project.

What does Research Ideation need to run?

SKILL.md names no scripts, command-line tools or credentials: Research Ideation is instructions for the agent only. Its frontmatter pre-approves these tools: write_file, edit_file, read_file, think_tool, execute.

Does Research Ideation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Research Ideation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Research Ideation use?

Research Ideation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Research Ideation use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Research Ideation?

Skills that share tags, products or a category with Research Ideation: Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), Typesafe AI (OpenAgentsInc/openagents, 455 stars), Yao Meta Skill (yaojingang/yao-meta-skill, 2.7k stars) and Trellis Start (ROYIANS/foliq-print-template-designer, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Research Ideation?

EvoScientist (a GitHub organization) maintains it in EvoScientist/EvoSkills, which has 476 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 30, 2026.

Source: EvoScientist/EvoSkills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.