Parallel CI Triage
spencerpauly/awesome-cursor-skills
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.
Agent skill
Deep Researcher Maintain CI
by NVIDIA-AI-Blueprints in NVIDIA-AI-Blueprints/deep-researcher-agent
A skill your agent uses when changing Deep Researcher Agent continuous integration, pre-commit, or contributor governance — editing .github/workflows/ (ci, ui, skills-eval, request-nvskills-ci)…
Install Deep Researcher Maintain CI
$ npx skills add NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA-AI-Blueprints/deep-researcher-agent deep-researcher-maintain-ci --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/NVIDIA-AI-Blueprints/deep-researcher-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/deep-researcher-maintain-ci .claude/skills/deep-researcher-maintain-ci && 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 "deep-researcher-maintain-ci" agent skill from https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent/tree/develop/.agents/skills/deep-researcher-maintain-ci into .claude/skills/deep-researcher-maintain-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-researcher-maintain-ci", 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/NVIDIA-AI-Blueprints/deep-researcher-agent/tree/develop/.agents/skills/deep-researcher-maintain-ciType 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 NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA-AI-Blueprints/deep-researcher-agent deep-researcher-maintain-ci --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/deep-researcher-maintain-ci .agents/skills/deep-researcher-maintain-ci && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deep-researcher-maintain-ci" agent skill from https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent/tree/develop/.agents/skills/deep-researcher-maintain-ci into .agents/skills/deep-researcher-maintain-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-researcher-maintain-ci", 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 NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA-AI-Blueprints/deep-researcher-agent deep-researcher-maintain-ci --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/deep-researcher-maintain-ci .cursor/skills/deep-researcher-maintain-ci && 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 "deep-researcher-maintain-ci" agent skill from https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent/tree/develop/.agents/skills/deep-researcher-maintain-ci into .cursor/skills/deep-researcher-maintain-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-researcher-maintain-ci", 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/NVIDIA-AI-Blueprints/deep-researcher-agent.git --path .agents/skills/deep-researcher-maintain-ci--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 NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA-AI-Blueprints/deep-researcher-agent deep-researcher-maintain-ci --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/deep-researcher-maintain-ci .gemini/skills/deep-researcher-maintain-ci && 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 "deep-researcher-maintain-ci" agent skill from https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent/tree/develop/.agents/skills/deep-researcher-maintain-ci into .gemini/skills/deep-researcher-maintain-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-researcher-maintain-ci", 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 NVIDIA-AI-Blueprints/deep-researcher-agent deep-researcher-maintain-ciInstalls 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 NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/deep-researcher-maintain-ci .github/skills/deep-researcher-maintain-ci && 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 "deep-researcher-maintain-ci" agent skill from https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent/tree/develop/.agents/skills/deep-researcher-maintain-ci into .github/skills/deep-researcher-maintain-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-researcher-maintain-ci", 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 NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA-AI-Blueprints/deep-researcher-agent deep-researcher-maintain-ci --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/deep-researcher-maintain-ci .opencode/skills/deep-researcher-maintain-ci && 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 "deep-researcher-maintain-ci" agent skill from https://github.com/NVIDIA-AI-Blueprints/deep-researcher-agent/tree/develop/.agents/skills/deep-researcher-maintain-ci into .opencode/skills/deep-researcher-maintain-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-researcher-maintain-ci", 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
deep-researcher-maintain-ci- GitHub stars
- 886
- Token cost
- ~1.5k tokens
- SKILL.md length
- 594 words
- Files
- 3 (incl. references)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when changing Deep Researcher Agent continuous integration, pre-commit, or contributor governance — editing .github/workflows/ (ci, ui, skills-eval, request-nvskills-ci)…
- Works in 6 steps: Locate the exact workflow, hook, or… → Make the smallest scoped change; keep… → Lint the change: validate YAML and, for… → …
- Changing Deep Researcher Agent continuous integration
- SKILL.md covers Start Here, Authoritative References, Workflow and Validation, plus 2 more sections
- Calls uv and actionlint
What it does
Deep Researcher Maintain CI is an agent skill from NVIDIA-AI-Blueprints/deep-researcher-agent. Use when changing Deep Researcher Agent continuous integration, pre-commit, or contributor governance — editing .github/workflows/ (ci, ui, skills-eval, request-nvskills-ci), .pre-commit-config.yaml hooks, .github/CODEOWNERS, .coderabbit.yaml, copy-pr-bot, or the .github/skill-eval harness — and validating those changes without breaking the gate.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/skill-eval-harness.md` and `references/workflows-and-hooks.md`). Compatibility notes: Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools.
It sits in Agent Workflows, covering Agent evaluation and testing and CI/CD. It works with GitHub, GitHub Actions and pytest. The repository describes itself as: The NVIDIA Deep Researcher Agent Blueprint is an open reference example for building intelligent AI agents that connect to your enterprise data, reason using state-of-the-art… The licence is Apache-2.0.
When your agent uses it
- Changing Deep Researcher Agent continuous integration
- Contributor governance — editing .github/workflows/ (ci
- Request-nvskills-ci)
- .pre-commit-config.yaml hooks
Example prompts
- “/deep-researcher-maintain-ci”
Requirements
- Compatibility (from SKILL.md): Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools.
- Pre-approved tools (allowed-tools): Read, Bash, Edit
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Locate the exact workflow, hook, or governance file and read it plus the
- Make the smallest scoped change; keep job names, triggers, and the
- Lint the change: validate YAML and, for workflows, run actionlint if it is
- Reproduce the affected gate locally where possible — run the pre-commit hooks
- Note that the real CI run happens on the copy-pr-bot mirror after a maintainer
- Summarize changed files and the local validation evidence.
What it can do on your machine
Read from SKILL.md and the folder at commit 951a1a1. 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:
ReadBashEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
uvactionlint
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
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.
Compatibility
Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools.
From compatibility in the SKILL.md frontmatter.
Context cost
Deep Researcher Maintain CI loads about 1.5k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 594 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Edit
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 NVIDIA-AI-Blueprints/deep-researcher-agent at commit 951a1a1, republished under its Apache-2.0 licence (© NVIDIA-AI-Blueprints). 594 words, ~1,458 tokens.
Download SKILL.mdSave it as
.claude/skills/deep-researcher-maintain-ci/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- deep-researcher-maintain-ci
- description
- Use when changing Deep Researcher Agent continuous integration, pre-commit, or contributor governance — editing .github/workflows/ (ci, ui, skills-eval, request-nvskills-ci), .pre-commit-config.yaml hooks, .github/CODEOWNERS, .coderabbit.yaml, copy-pr-bot, or the .github/skill-eval harness — and validating those changes without breaking the gate.
- allowed-tools
- Read, Bash, Edit
- compatibility
- Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools.
- license
- Apache-2.0
- metadata.version
- 0.1.0
- metadata.source-repo
- NVIDIA-AI-Blueprints/deep-researcher-agent
- metadata.tags
- deep-researcher ci github-actions pre-commit governance skill-eval
Maintain Deep Researcher Agent CI and Governance
Use this skill when a developer changes Deep Researcher Agent's CI, pre-commit hooks, or contributor governance — the GitHub Actions workflows, the pre-commit config, CODEOWNERS, the CodeRabbit review config, the copy-pr-bot mirror, or the product-level skill-eval harness. These surfaces gate every PR, so a change must keep the gate working and must not weaken security or review rules.
Start Here
- Identify the surface: a workflow (
.github/workflows/), a pre-commit hook (.pre-commit-config.yaml), governance (.github/CODEOWNERS,.coderabbit.yaml,.github/copy-pr-bot.yaml), or the skill-eval harness (.github/skill-eval/). - Read the authoritative files below and
CONTRIBUTING.md"CI and Bot Workflow" before editing — the bot/mirror flow is easy to break. - Make the smallest change; do not weaken secret detection, auth gating, or
code-owner review without a prior design discussion (see
AGENTS.md). - Remember CI runs on the copy-pr-bot mirror after
/ok to test, not on push.
Authoritative References
- CONTRIBUTING.md: "CI and Bot Workflow" — copy-pr-bot
mirroring to
pull-request/<N>,/ok to test,/nvskills-ci,/merge. - AGENTS.md: "Git and PR hygiene" and the validation commands CI mirrors.
.github/workflows/ci.yml: jobspre-commit,test(pytest + coverage),helm-lint,test-scripts. Thepre-commitjob runs Ruff separately and skips the push-stage pytest and Helm hooks when it runspre-commit run --all-files— those checks run as their own jobs instead..github/workflows/ui.yml: jobsinstall,lint,type-check,unit-test,build..github/workflows/skills-eval.yml: the Skills Eval gate (push +workflow_dispatch;detect-changespath gate →generate-datasetsspec validation →harbor-evalon the self-hosteddeep-researcher-evalrunner)..github/workflows/request-nvskills-ci.yml: comment-triggered NVSkills CI..pre-commit-config.yaml: the hook set. Notepytest-root,pytest-mcp, andhelm-lintarestages: [push](see the reference for what that means locally). Root and MCP pytest checks use their own uv projects; MCP is not a root dependency group..github/CODEOWNERS,.coderabbit.yaml,.github/copy-pr-bot.yaml: review routing, path-scoped automated review, and the PR mirror.
Longer procedures live in this bundle:
- references/workflows-and-hooks.md: the workflows, their jobs/triggers, the copy-pr-bot mirror flow, and the pre-commit hook inventory (incl. the push-stage hooks).
- references/skill-eval-harness.md: how the
.github/skill-eval/regression gate finds specs, runs adapters, and verifies.
Show full SKILL.md (276 more words)Show less
Workflow
- Locate the exact workflow, hook, or governance file and read it plus the
relevant
CONTRIBUTING.mdsection. - Make the smallest scoped change; keep job names, triggers, and the
detect-changespath gate intact unless that is the change. - Lint the change: validate YAML and, for workflows, run
actionlintif it is installed. - Reproduce the affected gate locally where possible — run the pre-commit hooks or the job's underlying command (see the references).
- Note that the real CI run happens on the copy-pr-bot mirror after a maintainer
comments
/ok to test. - Summarize changed files and the local validation evidence.
Validation
uv run pre-commit run --all-files # default-stage hooks (NOT pytest/helm-lint)
uv run pre-commit run --all-files --hook-stage push # adds the push-stage pytest + helm-lint hooks
uv run pre-commit run --files <changed> # faster, during iteration
actionlint .github/workflows/<file>.yml # if actionlint is installedExpected: hooks pass (or only auto-fix) and any edited workflow is valid YAML.
pytest and helm-lint are push-stage, so the default --all-files run skips
them — CI runs them as the dedicated test and helm-lint jobs. For skill-eval
changes, see the harness reference: full Harbor runs need the self-hosted runner,
so validate spec/adapter shape locally and rely on the mirrored CI run.
Common Mistakes
- Adding a trigger
paths:filter toskills-eval.ymlinstead of using thedetect-changesjob — the comment in that workflow explains why path-filtering the trigger is wrong here. - Weakening
detect-secrets, auth gating, or code-owner review to make CI pass. - Expecting CI to run on push; it runs on the copy-pr-bot mirror after
/ok to test. - Assuming
pre-commit run --all-filesreproduces the whole gate —pytestandhelm-lintarestages: [push], so they do not run at the default stage. Use--hook-stage push(or run them directly), and remember CI runs them as separate jobs. - Editing
.github/CODEOWNERSwithout updating the paths it routes, so reviews go to the wrong owners.
Related Skills
deep-researcher-release-qadeep-researcher-prepare-pr
© NVIDIA-AI-Blueprints, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .agents/skills/deep-researcher-maintain-ci of NVIDIA-AI-Blueprints/deep-researcher-agent.
- SKILL.md
- references/skill-eval-harness.md
- references/workflows-and-hooks.md
Open the folder on GitHubat commit 951a1a1
Compare with similar skills
Deep Researcher Maintain CI 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 |
|---|---|---|---|---|---|---|
| Deep Researcher Maintain CI this skillNVIDIA-AI-Blueprints/deep-researcher-agent | 886 | — | ~1.5k | Automated safety check: Notes | Apache-2.0 | |
| Parallel CI Triagespencerpauly/awesome-cursor-skills | 844 | — | ~793 | Automated safety check: Pass | CC0-1.0 | |
| GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb | 6.7k | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| CI Watchdoglatitude-dev/latitude-llm | 4.7k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Megatron-LM CI Failure TriageNVIDIA/Megatron-LM | 18k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Simple Modern Uvjlevy/simple-modern-uv | 301 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
GreptimeDB Fuzz CI Failure Investigation
GreptimeTeam/greptimedb
Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
- Official
Megatron-LM CI Failure Triage
NVIDIA/Megatron-LM
Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.
Simple Modern Uv
jlevy/simple-modern-uv
Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.
Review
apollographql/apollo-mcp-server
Review a GitHub pull request for a Rust codebase. An agent skill from apollographql/apollo-mcp-server.
More from NVIDIA-AI-Blueprints/deep-researcher-agent
All 15 skills in this repoDeep Researcher Configure Workflow
NVIDIA-AI-Blueprints/deep-researcher-agent
A skill your agent uses when composing, adapting, or validating an Deep Researcher Agent workflow YAML under configs/ — selecting a shipped profile, enabling tools and datasourceregistry sources…
Deep Researcher Research
NVIDIA-AI-Blueprints/deep-researcher-agent
A skill your agent uses when asked to run deep research or Deep Researcher Agent research through a reachable NVIDIA Deep Researcher Agent Blueprint backend.
Deep Researcher Add Data Source
NVIDIA-AI-Blueprints/deep-researcher-agent
A skill your agent uses when adding or changing an Deep Researcher Agent data source under sources/, registering it as a NeMo Agent Toolkit function, wiring it into the datasourceregistry for UI…
Deep Researcher Add Tool
NVIDIA-AI-Blueprints/deep-researcher-agent
A skill your agent uses when adding or changing a general-purpose Deep Researcher Agent tool (a NeMo Agent Toolkit function) under sources/, defining its FunctionBaseConfig schema, registering it…
Deep Researcher Customize Prompts Models
NVIDIA-AI-Blueprints/deep-researcher-agent
A skill your agent uses when customizing Deep Researcher Agent behavior through Jinja2 prompt templates or per-agent model selection — editing prompts under src/deepresearcheragent/agents//prompts/…
Deep Researcher Deploy
NVIDIA-AI-Blueprints/deep-researcher-agent
A skill your agent uses when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA Deep Researcher Agent Blueprint infrastructure.
Related
Works with
Questions about Deep Researcher Maintain CI
What does Deep Researcher Maintain CI do?
A skill your agent uses when changing Deep Researcher Agent continuous integration, pre-commit, or contributor governance — editing .github/workflows/ (ci, ui, skills-eval, request-nvskills-ci)…. Deep Researcher Maintain CI is an agent skill from NVIDIA-AI-Blueprints/deep-researcher-agent.github/skill-eval harness — and validating those changes without breaking the gate.
When should I use Deep Researcher Maintain CI?
Deep Researcher Maintain CI fits situations like: changing Deep Researcher Agent continuous integration; contributor governance — editing .github/workflows/ (ci; request-nvskills-ci); .pre-commit-config.yaml hooks.
How do I install Deep Researcher Maintain CI in Claude Code?
Run `npx skills add NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a claude-code`. Or copy the skill folder (.agents/skills/deep-researcher-maintain-ci in NVIDIA-AI-Blueprints/deep-researcher-agent) into .claude/skills/deep-researcher-maintain-ci in your project. Claude Code loads it when a task matches its description.
How do I install Deep Researcher Maintain CI in Codex?
Run `npx skills add NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a codex`. Or copy the skill folder (.agents/skills/deep-researcher-maintain-ci in NVIDIA-AI-Blueprints/deep-researcher-agent) into .agents/skills/deep-researcher-maintain-ci in your project. Codex loads it when a task matches its description.
Can I use Deep Researcher Maintain CI 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 NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-maintain-ci -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deep-researcher-maintain-ci, .gemini/skills/deep-researcher-maintain-ci, .github/skills/deep-researcher-maintain-ci and .opencode/skills/deep-researcher-maintain-ci in your project.
What does Deep Researcher Maintain CI need to run?
Going by SKILL.md and its folder, Deep Researcher Maintain CI needs the command-line tools its instructions call (uv and actionlint). Its frontmatter pre-approves these tools: Read, Bash, Edit. Compatibility (from SKILL.md): Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools..
Does Deep Researcher Maintain CI access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Deep Researcher Maintain CI safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Deep Researcher Maintain CI use?
Deep Researcher Maintain CI is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deep Researcher Maintain CI use?
About 1.5k tokens (SKILL.md is roughly 5.8k 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 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Deep Researcher Maintain CI?
Skills that share tags, products or a category with Deep Researcher Maintain CI: Parallel CI Triage (spencerpauly/awesome-cursor-skills, 844 stars), GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars), CI Watchdog (latitude-dev/latitude-llm, 4.7k stars) and Megatron-LM CI Failure Triage (NVIDIA/Megatron-LM, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deep Researcher Maintain CI?
NVIDIA-AI-Blueprints (a GitHub organization) maintains it in NVIDIA-AI-Blueprints/deep-researcher-agent, which has 886 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.
Source: NVIDIA-AI-Blueprints/deep-researcher-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.