🧠
AI EngineeringHTML

Research Interview

by pedrohcgs

Research Interview is an AI Engineering skill for Claude Code, published by pedrohcgs in claude-code-my-workflow.

1.5K stars2.9K forkson pedrohcgs/claude-code-my-workflowAdded 2026/08/19+1% in starsRepository updated 2026/06/10
academic-writingcausal-inferenceclaude-codeclaude-code-skillseconometricseconomicslatexquartoreproducible-researchresearch-workflow
Install in seconds
Install Research Interview
Copy Research Interview into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/interview-me ~/.claude/skills/interview-me

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/pedrohcgs/claude-code-my-workflow.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.claude/skills/interview-me/SKILL.md in pedrohcgs/claude-code-my-workflow
Installs to
~/.claude/skills/interview-me
Collection
One of 25 skills cataloged from this repository
Category
AI Engineering2451 skills

What Research Interview does

Research Interview asks clarifying questions one at a time to turn a fuzzy research idea into a structured spec covering research question, hypotheses, identification, data needs, and empirical strategy. Use it when you say "interview me" or need help formalizing a half-baked research idea into a project.

Research Interview is cataloged under AI Engineering on DirSkills. Research Interview comes from a repository tagged academic-writing, causal-inference, claude-code, claude-code-skills and econometrics.

Documentation

README

Research Interview

Conduct a structured interview to help formalize a research idea into a concrete specification.

Input: $ARGUMENTS — a brief topic description or "start fresh" for an open-ended exploration.


How This Works

This is a conversational skill. Instead of producing a report immediately, you conduct an interview by asking questions one at a time, probing deeper based on answers, and building toward a structured research specification.

Do NOT use AskUserQuestion. Ask questions directly in your text responses, one or two at a time. Wait for the user to respond before continuing.


This is the opening of the README. Read the full README on GitHub.

Frequently asked about Research Interview

  • What else does pedrohcgs publish alongside Research Interview?

    Research Interview is one of 25 skills that DirSkills catalogs from pedrohcgs/claude-code-my-workflow, the repository it ships in. Its siblings there include Audit Reproducibility, Capture Environment and Checkpoint. Each one is a separate skill with its own page in this directory, installs the same way Research Interview does, and is maintained by pedrohcgs in that same repository. The rest of the collection is listed on the pedrohcgs/claude-code-my-workflow page.

  • How does Research Interview compare to other AI Engineering skills?

    Research Interview ranks #987 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Research Interview against them. Open each page to compare what they document and how they install.

More from pedrohcgs/claude-code-my-workflow

Research Interview is one of 25 skills cataloged on DirSkills from pedrohcgs/claude-code-my-workflow.

See all 25 skills
🔍
2w ago

Audit Reproducibility

Audit Reproducibility compares numeric claims in a manuscript against actual analysis outputs and reports PASS/FAIL per claim against tolerance thresholds. Use it before submission, before releasing a replication package, or after a major revision to catch mismatches between the paper and the code.
Quality
1.5K2.9K
🧰
2w ago

Capture Environment

Capture Environment snapshots a project’s software stack for a replication package, including language versions, package locks, seeds, and RNG settings. Use it before releasing or handing off analysis code so others can rebuild the same environment.
DevOps
1.5K2.9K
📌
2w ago

Checkpoint

Checkpoint saves a structured state snapshot before stopping or handing off, capturing the active plan, recent decisions, file pointers with line numbers, open questions, and next actions. Use it before a break, model switch, or collaborator handoff when you need to resume quickly.
AI Engineering
1.5K2.9K
🤝
2w ago

Coauthor Brief

Coauthor Brief generates a Markdown handoff brief for co-authors or future selves, summarizing git changes, artifact status, open questions, and local reproduction steps. Use it when onboarding a collaborator, sending a co-author the repo, or doing a periodic sync.
Automation
1.5K2.9K
🚀
2w ago

Commit, PR, and Merge

Commit, PR, and Merge stages changes, verifies quality gates, commits with a descriptive message, creates a pull request, and merges to main when the user explicitly asks to commit or ship changes.
Automation
1.5K2.9K
📄
2w ago

Compile Beamer LaTeX Slides

Compile Beamer LaTeX Slides compiles Beamer LaTeX slide decks using XeLaTeX with a 3-pass build sequence (xelatex, bibtex, xelatex twice). Use it when the user asks to compile, build slides, rebuild PDF, run latex, or render tex files in Slides/*.tex.
Automation
1.5K2.9K