PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
A skill your agent uses when research files (web or GitHub findings) are available and must be synthesized into a recommendation.
MITAuto-check passed
Install Research
$ npx skills add romiluz13/cc10x --skill research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install romiluz13/cc10x research --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/romiluz13/cc10x.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/cc10x/skills/research .claude/skills/research && 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 "research" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/research into .claude/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", 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/romiluz13/cc10x/tree/main/plugins/cc10x/skills/researchType 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 romiluz13/cc10x --skill research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install romiluz13/cc10x research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/cc10x/skills/research .agents/skills/research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "research" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/research into .agents/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", 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 romiluz13/cc10x --skill research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install romiluz13/cc10x research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/cc10x/skills/research .cursor/skills/research && 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 "research" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/research into .cursor/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", 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/romiluz13/cc10x.git --path plugins/cc10x/skills/research--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 romiluz13/cc10x --skill research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install romiluz13/cc10x research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/cc10x/skills/research .gemini/skills/research && 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 "research" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/research into .gemini/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", 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 romiluz13/cc10x researchInstalls 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 romiluz13/cc10x --skill research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/cc10x/skills/research .github/skills/research && 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 "research" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/research into .github/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", 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 romiluz13/cc10x --skill research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install romiluz13/cc10x research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/cc10x/skills/research .opencode/skills/research && 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 "research" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/research into .opencode/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", 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
research- GitHub stars
- 164
- Token cost
- ~1.4k tokens
- SKILL.md length
- 643 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when research files (web or GitHub findings) are available and must be synthesized into a recommendation.
- Works in 6 steps: Answers the knowledge gap (the Reason… → Identifies the top 2-3 actionable patterns → Lists gotchas with solutions → …
- Research files (web
- SKILL.md covers Overview, Synthesis Goal, What Makes Good Synthesis and Same-Name Disambiguation, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Research is an agent skill from romiluz13/cc10x. Use when research files (web or GitHub findings) are available and must be synthesized into a recommendation. Synthesis guidance only; it does not execute research.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with GitHub. The repository describes itself as: The Loop Engine for Claude Code — engineer the loop, not the prompt. 1 router · 9 agents · 16 skills · 4 workflows. Fail-closed gates, test honesty, anti-anchored review. The licence is MIT.
When your agent uses it
- Research files (web
- GitHub findings) are available and must be synthesized into a recommendation
Example prompts
- “/research”
Requirements
- Pre-approved tools (allowed-tools): Read
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Answers the knowledge gap (the Reason field from your prompt)
- Identifies the top 2-3 actionable patterns
- Lists gotchas with solutions
- Provides specific references for debugging
- Reflects evidence quality honestly
- States the single finding that most changed the recommendation
What it can do on your machine
Read from SKILL.md and the folder at commit f346ebe. 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:
Read
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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 loads about 1.4k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 643 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
The full file from romiluz13/cc10x at commit f346ebe, republished under its MIT licence (© romiluz13). 643 words, ~1,415 tokens.
Download SKILL.mdSave it as
.claude/skills/research/SKILL.md (or your agent's skills folder).- name
- research
- description
- Use when research files (web or GitHub findings) are available and must be synthesized into a recommendation. Synthesis guidance only; it does not execute research.
- allowed-tools
- Read
- user-invocable
- false
Research Synthesis Guidance
Overview
This skill is loaded via SKILL_HINTS by cc10x:planner and cc10x:bug-investigator when the router passes research files in the prompt. It provides instructions for synthesizing web and GitHub research findings.
This skill does NOT execute research. Research execution is done by:
cc10x:researcher (web mode)— prefers Bright Data, falls back to WebSearch/WebFetchcc10x:researcher (github mode)— prefers Octocode MCP, falls back to package/docs/GitHub web research
Synthesis Goal
After the router passes research file paths in your prompt, read the available files and produce a synthesis that:
- Answers the knowledge gap (the
Reasonfield from your prompt) - Identifies the top 2-3 actionable patterns
- Lists gotchas with solutions
- Provides specific references for debugging
- Reflects evidence quality honestly
- States the single finding that most changed the recommendation
What Makes Good Synthesis
Include:
- Cross-source confirmation (when web + GitHub agree on a pattern, it's reliable)
- Primary-source preference: prefer the source that owns the claim — spec, first-party docs, shipped code. A secondary write-up citing a primary loses to the primary.
- Conflict resolution: when sources disagree, code-backed, cross-confirmed findings override single-source prose; shipped code overrides docs (docs describe intent; code is what runs). Partial matches (one strong source only) require adaptation — state the adaptation rationale explicitly.
- Confidence calibration from the router-provided
## Research Qualityblock - Gotchas the user probably hasn't considered
- Specific code snippets only when they materially change the recommendation
Exclude:
- Raw dump of all findings (summarize)
- Obvious things the AI already knows
- Findings not relevant to the specific
Reasonfor research
Same-Name Disambiguation
A name (package, repo, handle) is not a unique key. Researchers routinely retrieve content where one name collides across distinct entities — two npm packages publish under the same name, the same handle exists on two platforms run by different people, a repo name is forked or squatted under multiple owners. This is retrieval noise, not a source conflict.
Once the canonical entity is resolved — the one the project actually depends on, the owner/scope it ships under, the platform that matches the project's context — treat that resolution as authoritative:
- Lead with the canonical entity. Synthesis answers for the resolved package/repo/handle, not for the name in the abstract.
- Actively reject off-target same-name matches. Do not average them into the synthesis, do not merge their findings, do not hedge between them. A finding about the wrong
left-padis wrong, not low-confidence. - Resolve by anchor, not popularity. Pin to the version/scope in the project's manifest (
package.jsondependency name + version), theowner/repothe lockfile or import path points at, the platform the handle is referenced from. The most-starred or most-trafficked same-name hit is often not the project's. - Surface the collision when it changed the answer. If a researcher clearly retrieved the wrong entity, say so in one line (e.g. "GitHub findings were for
acme/foo, but the project depends on@acme-internal/foo— discarded") rather than silently dropping them. This is distinct from a genuine source disagreement, which still follows the conflict-resolution rules above.
Show full SKILL.md (153 more words)Show less
Synthesis Format
## Evidence Quality
- Web: [high / medium / low / none]
- GitHub: [high / medium / low / none]
- Overall confidence: [high / medium / low]
## Web Findings
[3-5 bullets from web research. Focus on patterns and gotchas.]
## GitHub Findings
[3-5 bullets from GitHub. Focus on real implementation patterns.]
## Synthesis
**Knowledge Gap answered:** [One sentence: what we now know that we didn't before]
**Recommended approach:** [1-3 sentences: what to do]
**What changed the recommendation most:** [single sentence]
**Top patterns to apply:**
1. [Specific, actionable pattern]
2. [Specific, actionable pattern]
**Gotchas to avoid:**
- [Gotcha]: [Solution]
**References for debugging:**
- [URL or GitHub repo path]Handling Partial Research
If GitHub researcher returned [GitHub phase unavailable]:
- Note it in the synthesis header: "GitHub research unavailable — Web only"
- Use web findings only for synthesis
If BOTH unavailable:
- State clearly: "Research unavailable — all sources down. Proceeding with AI knowledge only."
- Lower confidence and rely on repo-local evidence first.
Quality weighting:
high: multiple concrete sources or code-backed findingsmedium: one strong source or partial cross-confirmationlow: indirect, sparse, or web-only/package-only signalsnone: no usable external findings
Memory Output
Do not edit .cc10x/*.md directly from this skill or from the host agent. allowed-tools: Read in this skill's frontmatter pre-approves Read; it does not restrict other tools, so this rule is an instruction to the host agent, not a tool restriction.
Instead, surface the most durable takeaway through the host agent's MEMORY_NOTES, for example:
- one research-backed gotcha worth preserving
- one reference path worth indexing
- one confidence caveat if research quality was degraded
© romiluz13, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/cc10x/skills/research of romiluz13/cc10x.
Open the folder on GitHubat commit f346ebe
Compare with similar skills
Research 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 |
|---|---|---|---|---|---|---|
| Research this skillromiluz13/cc10x | 164 | — | ~1.4k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
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.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
More from romiluz13/cc10x
All 22 skills in this repoBuilding
romiluz13/cc10x
A skill your agent uses when writing production code test-first: the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation…
Diff Driven Docs
romiluz13/cc10x
A skill your agent uses when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation.
Planning
romiluz13/cc10x
A skill your agent uses when writing an execution plan or a decision RFC: task decomposition, context references, validation levels, risk-based testing, ADR format, plan completeness gate, and…
Verification
romiluz13/cc10x
A skill your agent uses when judging whether a task reached its goal, not just finished: the gate function, self-critique gate, validation levels, evidence array protocol, and goal-backward lens.
Agent Common
romiluz13/cc10x
A skill your agent uses when a cc10x agent starts a task: the shared preamble for the memory protocol, the contract format, and the output rules.
Cc10x Guide
romiluz13/cc10x
Answers questions about cc10x itself — what it is, how to install and configure it, how the router, workflows, memory, and hooks operate, and how to troubleshoot.
Related
Works with
Questions about Research
What does Research do?
A skill your agent uses when research files (web or GitHub findings) are available and must be synthesized into a recommendation. Research is an agent skill from romiluz13/cc10x. Use when research files (web or GitHub findings) are available and must be synthesized into a recommendation.
When should I use Research?
Research fits situations like: research files (web; GitHub findings) are available and must be synthesized into a recommendation.
How do I install Research in Claude Code?
Run `npx skills add romiluz13/cc10x --skill research -a claude-code`. Or copy the skill folder (plugins/cc10x/skills/research in romiluz13/cc10x) into .claude/skills/research in your project. Claude Code loads it when a task matches its description.
How do I install Research in Codex?
Run `npx skills add romiluz13/cc10x --skill research -a codex`. Or copy the skill folder (plugins/cc10x/skills/research in romiluz13/cc10x) into .agents/skills/research in your project. Codex loads it when a task matches its description.
Can I use Research 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 romiluz13/cc10x --skill research -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, .gemini/skills/research, .github/skills/research and .opencode/skills/research in your project.
What does Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Research is instructions for the agent only. Its frontmatter pre-approves these tools: Read.
Does Research 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 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 use?
Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Research use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Research?
Skills that share tags, products or a category with Research: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Research?
romiluz13 (a GitHub user) maintains it in romiluz13/cc10x, which has 164 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 7, 2026.
Source: romiluz13/cc10x on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.