Agent skill · Code Review & Quality

research-pipeline

Full research pipeline: Workflow 1 (idea discovery) → implementation → Workflow 2 (auto review loop) → Workflow 3 (paper writing, optional). Goes from a broad research direction all the way to a polished PDF. Use when user says \"全流程\", \"full pipeline\", \"从找idea到投稿\", \"end-to-end research\", or wants the complete autonomous research lifecycle.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill research-pipeline-wanshuiyin-auto-claude-code-res --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Allowed tools: Bash(*)ReadWriteEditGrepGlobWebSearchWebFetchAgentSkillmcp__codex__codexmcp__codex__codex-reply
Path: skills/analysis/research-pipeline-wanshuiyin-auto-claude-code-res/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Full Research Pipeline: Idea → Experiments → Submission End-to-end autonomous research workflow for: **$ARGUMENTS** ## Constants - **AUTO_PROCEED = true** — When `true`, Gate 1 auto-selects the top-ranked idea (highest pilot signal + novelty confirmed) and continues to implementation. When `false`, always waits for explicit user confirmation before proceeding. - **ARXIV_DOWNLOAD = false** — When `true`, `/research-lit` downloads the top relevant arXiv PDFs during literature survey. When `false` (default), only fetches metadata via arXiv API. Passed through to `/idea-discovery` → `/research-lit`. - **HUMAN_CHECKPOINT = false** — When `true`, the auto-review loops (Stage 4) pause after each round's review to let you see the score and provide custom modification instructions before fixes are implemented. When `false` (default), loops run fully autonomously. Passed through to `/auto-review-loop`. - **REVIEWER_DIFFICULTY = medium** — How adversarial the reviewer is. `medium` (default): standard MCP review. `hard`: adds reviewer memory + debate protocol. `nightmare`: GPT reads repo directly via `codex exec` + memory + debate. Passed through to `/auto-review-loop`. - **AUTO_WRITE = fals

What's inside
Steps it walks through
  1. Constants
  2. Overview
  3. Pipeline
  4. Stage 1: Idea Discovery (Workflow 1)
  5. Stage 2: Implementation
  6. Stage 3: Deploy Experiments (Workflow 2 — Part 1)
  7. Stage 4: Auto Review Loop (Workflow 2 — Part 2)
  8. Stage 5: Research Summary & Writing Handoff
  9. Stage 6: Paper Writing (Workflow 3 — Optional)
  10. Output Protocols
  11. Key Rules
  12. Typical Timeline
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the research-pipeline skill do?

Full research pipeline: Workflow 1 (idea discovery) → implementation → Workflow 2 (auto review loop) → Workflow 3 (paper writing, optional). Goes from a broad research direction all the way to a polished PDF. Use when user says \"全流程\", \"full pipeline\", \"从找idea到投稿\", \"end-to-end research\", or wants the complete autonomous research lifecycle.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill research-pipeline-wanshuiyin-auto-claude-code-res --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going