Skip to content

pedrohcgs/claude-code-my-workflow / .agents/skills/research-ideation

research-ideation

Unverified

Generate structured research questions, testable hypotheses, and candidate empirical strategies from a topic, phenomenon, or dataset description. Use when user says "give me research ideas on X", "brainstorm questions about Y", "what could I study with this data?", "I'm looking for a paper idea on...", "generate hypotheses for...". One-shot generation, not multi-turn. For idea-refinement use `/interview-me`.

FileKindSize
SKILL.mdskill md2.2 KB
---
name: research-ideation
description: Generate structured research questions, testable hypotheses, and candidate empirical strategies from a topic, phenomenon, or dataset description. Use when user says "give me research ideas on X", "brainstorm questions about Y", "what could I study with this data?", "I'm looking for a paper idea on...", "generate hypotheses for...". One-shot generation, not multi-turn. For idea-refinement use `/interview-me`.
---
<!-- Generated by scripts/sync-agent-skills.py from .claude/skills/research-ideation/SKILL.md. Do not edit: change the source and re-run the script. -->

# research-ideation

This skill's instructions live in [`.claude/skills/research-ideation/SKILL.md`](../../../.claude/skills/research-ideation/SKILL.md).
Read that file now and follow it, with the files it points to. Read [`AGENTS.md`](../../../AGENTS.md)
first if you have not already.

It was written for Claude Code. Running it from Codex, Antigravity or another agent:

- **Arguments.** Where it says `$ARGUMENTS`, use what the user asked for.
- **Claude Code agents.** Where a step hands work to an agent in `.claude/agents/` (through the
  `Agent` or `Task` tool), do that step where it appears in the procedure: never later, and never
  skip it. A step that gates what follows still gates it (`/commit` runs its verifier before it
  commits). Read the agent's file for what the step checks.
- **Fresh context.** If the step needs a context that has not seen your work, for example a claim
  verifier that must never see the draft, run it in a separate session or worker that has not
  seen the draft, if your tool can start one, and give it only what the step says to pass. If it
  cannot, do the step yourself, mark every result it produced *not independently verified*, and
  tell the user to repeat that check in Claude Code (`/verify-claims` for citations) before
  relying on it.
- **Claude Code settings.** `allowed-tools`, `model`, `effort`, `argument-hint` and
  `disable-model-invocation` in the source's frontmatter configure Claude Code. Ignore them.
- **Guards.** Claude Code's guard hooks do not run for you. Follow the rules in `AGENTS.md`
  yourself; the git pre-commit gate and CI still apply to your commits.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall