GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Guides the user through an interactive conversation to define their research project, then generates researchbrief.json and tasks.json.
Install Inno Pipeline Planner
$ npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenLAIR/dr-claw inno-pipeline-planner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenLAIR/dr-claw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inno-pipeline-planner .claude/skills/inno-pipeline-planner && rm -rf skills-srcUse ~/.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/
Install the "inno-pipeline-planner" agent skill from https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-planner into .claude/skills/inno-pipeline-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inno-pipeline-planner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-plannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenLAIR/dr-claw inno-pipeline-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenLAIR/dr-claw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/inno-pipeline-planner .agents/skills/inno-pipeline-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "inno-pipeline-planner" agent skill from https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-planner into .agents/skills/inno-pipeline-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inno-pipeline-planner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenLAIR/dr-claw inno-pipeline-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenLAIR/dr-claw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/inno-pipeline-planner .cursor/skills/inno-pipeline-planner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "inno-pipeline-planner" agent skill from https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-planner into .cursor/skills/inno-pipeline-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inno-pipeline-planner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenLAIR/dr-claw.git --path skills/inno-pipeline-planner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenLAIR/dr-claw inno-pipeline-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenLAIR/dr-claw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/inno-pipeline-planner .gemini/skills/inno-pipeline-planner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "inno-pipeline-planner" agent skill from https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-planner into .gemini/skills/inno-pipeline-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inno-pipeline-planner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenLAIR/dr-claw inno-pipeline-plannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenLAIR/dr-claw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/inno-pipeline-planner .github/skills/inno-pipeline-planner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "inno-pipeline-planner" agent skill from https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-planner into .github/skills/inno-pipeline-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inno-pipeline-planner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenLAIR/dr-claw inno-pipeline-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenLAIR/dr-claw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/inno-pipeline-planner .opencode/skills/inno-pipeline-planner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "inno-pipeline-planner" agent skill from https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-planner into .opencode/skills/inno-pipeline-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inno-pipeline-planner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
inno-pipeline-planner- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 569 words
- Files
- 6 (incl. references)
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guides the user through an interactive conversation to define their research project, then generates researchbrief.json and tasks.json.
- Works in 5 steps: Inspect existing pipeline state → Collect project context via conversation → Write pipeline files → …
- Starting a new project
- SKILL.md covers Non-negotiables, Workflow, 1) Inspect existing pipeline… and 2) Collect project context via…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Inno Pipeline Planner is an agent skill from OpenLAIR/dr-claw. Guides the user through an interactive conversation to define their research project, then generates researchbrief.json and tasks.json. Use when starting a new project, when no researchbrief.json exists, when the user wants to start from a specific pipeline stage, or when the user wants to redefine their research pipeline.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `references/brief-schema.md` and `references/generation-rules.md`).
It sits in Research & Science, covering Deep research. The repository describes itself as: A Super AI Lab with massive AI Doctors as Assistants. Best IDE for Research via AI Power.
When your agent uses it
- Starting a new project
- No researchbrief.json exists
- The user wants to start from a specific pipeline stage
- The user wants to redefine their research pipeline
Example prompts
- “Use the inno-pipeline-planner skill to guide the user through an interactive conversation to define their research project, then generates…”
- “/inno-pipeline-planner”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Inspect existing pipeline state
- Collect project context via conversation
- Write pipeline files
- Summarize and confirm next action
- Handle iteration requests
What it can do on your machine
Read from SKILL.md and the folder at commit d51b64e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
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
Inno Pipeline Planner loads about 1.3k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 569 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 569 words (~1,268 tokens).
“Run an interactive planning flow that turns user conversation into:”
- name
- inno-pipeline-planner
Files
SKILL.md and 5 other files (references) in skills/inno-pipeline-planner of OpenLAIR/dr-claw.
- SKILL.md
- agents/openai.yaml
- references/brief-schema.md
- references/generation-rules.md
- references/pipeline-contract.md
- references/tasks-schema.md
Open the folder on GitHubat commit d51b64e
Compare with similar skills
Inno Pipeline Planner 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Inno Pipeline Planner this skillOpenLAIR/dr-claw | 1.2k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Deep Research WorkflowTokenRhythm/opensquilla | 7.1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Deep Researchsanjay3290/ai-skills | 432 | 9 repos | ~683 | Automated safety check: Notes | Apache-2.0 | |
| Horizontal-Vertical Deep ResearchKKKKhazix/khazix-skills | 21k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Academic Research PipelineImbad0202/academic-research-skills | 51k | — | ~15k | Automated safety check: Pass | Custom licence |
Similar skills
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
Deep Research
sanjay3290/ai-skills
Execute autonomous multi-step research using Google Gemini Deep Research Agent.
Horizontal-Vertical Deep Research
KKKKhazix/khazix-skills
Runs a two-axis deep research method on a product, company, concept or person: its full history over time, compared with peers today, delivered as a typeset PDF report.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
Academic Research Suite for Codex
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
More from OpenLAIR/dr-claw
All 36 skills in this repoAcademic Rebuttal Drafting
OpenLAIR/dr-claw
Analyzes reviewer comments and drafts venue-specific rebuttals for AI and computer science conferences, with an issue board, task list and paper edit plan.
Academic Presentation Maker
OpenLAIR/dr-claw
Turns a research paper into a slide deck and, optionally, a narrated demo video, through script, slide generation, text-to-speech and video assembly stages you control.
News to Research Idea Briefing
OpenLAIR/dr-claw
Clusters the latest news-feed results by topic and writes a briefing of research idea seeds with citations, plus a structured seeds file, without crawling new sources.
ML Dataset Discovery
OpenLAIR/dr-claw
Searches Hugging Face Hub, OpenML, GitHub and paper references for datasets that fit a research task and returns a ranked, de-duplicated table.
Gemini Deep Research
OpenLAIR/dr-claw
Runs multi-source web research through Google's Gemini Deep Research Agent with a bundled Python script and saves a structured, cited report as files.
Grant Proposal Writing Workflow
OpenLAIR/dr-claw
Six-phase workflow for writing, revising and adapting grant proposals for NSF, NIH, DOE, DARPA, NASA and China's NSFC, from profiling through simulated peer review.
Related
Categories
Questions about Inno Pipeline Planner
What does Inno Pipeline Planner do?
Guides the user through an interactive conversation to define their research project, then generates researchbrief.json and tasks.json. Inno Pipeline Planner is an agent skill from OpenLAIR/dr-claw.json.
When should I use Inno Pipeline Planner?
Inno Pipeline Planner fits situations like: starting a new project; no researchbrief.json exists; the user wants to start from a specific pipeline stage; the user wants to redefine their research pipeline.
How do I install Inno Pipeline Planner in Claude Code?
Run `npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a claude-code`. Or copy the skill folder (skills/inno-pipeline-planner in OpenLAIR/dr-claw) into .claude/skills/inno-pipeline-planner in your project. Claude Code loads it when a task matches its description.
How do I install Inno Pipeline Planner in Codex?
Run `npx skills add OpenLAIR/dr-claw --skill inno-pipeline-planner -a codex`. Or copy the skill folder (skills/inno-pipeline-planner in OpenLAIR/dr-claw) into .agents/skills/inno-pipeline-planner in your project. Codex loads it when a task matches its description.
Can I use Inno Pipeline Planner 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 OpenLAIR/dr-claw --skill inno-pipeline-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inno-pipeline-planner, .gemini/skills/inno-pipeline-planner, .github/skills/inno-pipeline-planner and .opencode/skills/inno-pipeline-planner in your project.
What does Inno Pipeline Planner need to run?
SKILL.md names no scripts, command-line tools or credentials: Inno Pipeline Planner is instructions for the agent only.
Does Inno Pipeline Planner 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 Inno Pipeline Planner 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 Inno Pipeline Planner use?
Inno Pipeline Planner has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Inno Pipeline Planner use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 3.1k tokens, read only when the agent opens those files.
What are the alternatives to Inno Pipeline Planner?
Skills that share tags, products or a category with Inno Pipeline Planner: GitHub Deep Research (bytedance/deer-flow, 84k stars), Deep Research Workflow (TokenRhythm/opensquilla, 7.1k stars), Deep Research (sanjay3290/ai-skills, 432 stars) and Horizontal-Vertical Deep Research (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Inno Pipeline Planner?
OpenLAIR (a GitHub organization) maintains it in OpenLAIR/dr-claw, which has 1,155 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on September 17, 2026.
Source: OpenLAIR/dr-claw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.