Agent skill

Deep Researcher Release QA

by NVIDIA-AI-Blueprints in NVIDIA-AI-Blueprints/deep-researcher-agent

A skill your agent uses when validating an Deep Researcher Agent change before opening or merging a PR — choosing and running the right Python, frontend, docs, or eval checks for the surfaces you…

Apache-2.0Auto-check: notesFrontend & Design

Install Deep Researcher Release QA

skills CLI
$ npx skills add NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-release-qa -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA-AI-Blueprints/deep-researcher-agent deep-researcher-release-qa --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-release-qa .claude/skills/deep-researcher-release-qa && rm -rf skills-src

Use ~/.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/

Facts

Skill name
deep-researcher-release-qa
GitHub stars
886
Token cost
~1.2k tokens
SKILL.md length
488 words
Files
2 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when validating an Deep Researcher Agent change before opening or merging a PR — choosing and running the right Python, frontend, docs, or eval checks for the surfaces you…

  • Works in 5 steps: List the changed paths (git status, git… → Run the scoped Python, UI, docs, or eval… → If the change touches shared code or… → …
  • Validating an Deep Researcher Agent change before opening
  • SKILL.md covers Start Here, Authoritative References, Workflow and Validation, plus 2 more sections
  • Calls uv, npm and git

What it does

Deep Researcher Release QA is an agent skill from NVIDIA-AI-Blueprints/deep-researcher-agent. Use when validating an Deep Researcher Agent change before opening or merging a PR — choosing and running the right Python, frontend, docs, or eval checks for the surfaces you touched instead of one fixed command list.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/validation-matrix.md`). Compatibility notes: Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools.

It sits in Frontend & Design. It works with Python and Model Context Protocol. 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

  • Validating an Deep Researcher Agent change before opening
  • Merging a PR — choosing and running the right Python
  • Eval checks for the surfaces you touched instead of one fixed command list

Example prompts

  • “/deep-researcher-release-qa”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools.
  • Pre-approved tools (allowed-tools): Read, Bash

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. List the changed paths (git status, git diff --name-only) and map them to
  2. Run the scoped Python, UI, docs, or eval checks for those surfaces.
  3. If the change touches shared code or config, broaden to the full suite for
  4. Re-run until lint, format, type, and tests all pass; fix failures rather than
  5. Record the exact commands and their output for the PR description.

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:

    • Read
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv
    • npm
    • git
    • ruff

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, npm and git, 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 Release QA loads about 1.2k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 488 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

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.

  • NoteMentions a .env fileSKILL.md:30
    - Never paste secrets or `deploy/.env` values into command output you share.
  • NoteMentions a .env fileSKILL.md:111
    Forgetting that `nat eval` needs `deploy/.env`; run evals via
  • NoteMentions a .env fileSKILL.md:112
    `dotenv -f deploy/.env run nat eval ...` (see the matrix reference).
  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash

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). 488 words, ~1,164 tokens.

Download SKILL.mdSave it as .claude/skills/deep-researcher-release-qa/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
deep-researcher-release-qa
description
Use when validating an Deep Researcher Agent change before opening or merging a PR — choosing and running the right Python, frontend, docs, or eval checks for the surfaces you touched instead of one fixed command list.
allowed-tools
Read, Bash
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 nemo-agent-toolkit validation testing release-qa

Deep Researcher Agent Release QA

Use this skill to validate a change in the Deep Researcher Agent repository before opening or merging a pull request. The goal is to run the narrowest set of checks that covers what you touched, then broaden only when a change crosses shared boundaries — not to run every command every time.

Start Here

  • Identify which surfaces the change touches: backend Python (src/, sources/, tests/), web UI (frontends/ui/), docs (docs/), or evals (frontends/benchmarks/).
  • Run the scoped checks for those surfaces first (see the matrix below).
  • Broaden to the full suite only when the change crosses shared boundaries (for example editing src/deep_researcher_agent/common/ or a config many agents load).
  • Capture the exact commands and their output — deep-researcher-prepare-pr requires this as validation evidence.
  • Never paste secrets or deploy/.env values into command output you share.

Authoritative References

  • AGENTS.md: the "Build, test, and validation commands" section is the source of truth for every command below.
  • CONTRIBUTING.md: "Local Validation" — the exact commands to run and the requirement to include their output in the PR.
  • pyproject.toml and uv.lock: root Ruff config (line length 120, rule sets E,F,W,I,PL,UP) and the root dev environment.
  • mcp/pyproject.toml and mcp/uv.lock: the independent MCP runtime and dev environment. MCP is not a root dependency group.
  • frontends/ui/package.json: the real scripts (lint, type-check, test:ci, build) — use these names, do not invent npm scripts.

For the full per-surface command list and expected results:

Workflow

  1. List the changed paths (git status, git diff --name-only) and map them to surfaces.
  2. Run the scoped Python, UI, docs, or eval checks for those surfaces.
  3. If the change touches shared code or config, broaden to the full suite for that surface.
  4. Re-run until lint, format, type, and tests all pass; fix failures rather than skipping checks.
  5. Record the exact commands and their output for the PR description.
Show full SKILL.md (182 more words)Show less

Validation

Pick the block that matches the change. Run the narrowest first.

Backend Python (run from the repo root; the project uses uv):

bash
uv run ruff check <changed paths>          # lint
uv run ruff format --check <changed paths> # format check
uv run pytest <scoped test paths>          # tests

MCP server (run from the repo root):

bash
uv sync --project mcp --extra dev
uv run ruff check mcp
uv run ruff format --check mcp
uv run --project mcp --extra dev pytest mcp/tests

Broaden to the whole tree when the change crosses shared boundaries:

bash
uv run ruff check .
uv run ruff format --check .
uv run pytest
uv run --project mcp --extra dev pytest mcp/tests

Frontend (from frontends/ui/):

bash
npm run lint
npm run type-check
npm run test:ci

Expected: Ruff reports no lint or format failures, tests pass, and the frontend lint/type-check/test commands exit cleanly. For docs and eval changes, see the matrix reference.

Common Mistakes

  • Running both complete root and MCP test suites for a one-package change instead of scoping to the touched paths first — slow, and it buries the relevant signal.
  • Running MCP tests in the root environment; use uv run --project mcp so the check consumes the isolated MCP lock and dev extra.
  • Skipping ruff format --check and pushing unformatted code that fails CI.
  • Hand-reformatting unrelated code; only the changed code should move.
  • Forgetting that nat eval needs deploy/.env; run evals via dotenv -f deploy/.env run nat eval ... (see the matrix reference).
  • Inventing npm scripts; stick to the canonical checks lint, type-check, test:ci, and build defined in frontends/ui/package.json.
  • deep-researcher-prepare-pr
  • deep-researcher-add-tool
  • deep-researcher-add-data-source

© 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 1 other file (references) in .agents/skills/deep-researcher-release-qa of NVIDIA-AI-Blueprints/deep-researcher-agent.

  • SKILL.md
  • references/validation-matrix.md

Open the folder on GitHubat commit 951a1a1

Compare with similar skills

Deep Researcher Release QA 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.

Deep Researcher Release QA compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deep Researcher Release QA this skillNVIDIA-AI-Blueprints/deep-researcher-agent886—~1.2kAutomated safety check: NotesApache-2.0
DocsPrefectHQ/fastmcp28k—~1kAutomated safety check: PassApache-2.0
Jarvis Setupethanplusai/jarvis846—~2.5kAutomated safety check: NotesCustom licence
Fast Agent Designevalstate/fast-agent3.9k—~220Automated safety check: PassApache-2.0
Site Checkguardana/guardana259—~679Automated safety check: PassApache-2.0
NSFC Literature Review WriterHuiyuLi-2000/Chinese-Grant-Writer-Skills4391 repos~1.4kAutomated safety check: NotesMIT

Similar skills

  • Docs

    PrefectHQ/fastmcp

    Write or revise a page under docs/ for gofastmcp.com. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Jarvis Setup

    ethanplusai/jarvis

    A skill your agent uses when helping someone install, configure, or debug a fresh clone of JARVIS (this repo) — especially "the mic doesn't work", "JARVIS says his language systems are down", any…

    846 GitHub stars~2.5k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check: notes
  • Fast Agent Design

    evalstate/fast-agent

    A skill your agent uses to generate well-branded interfaces and assets for fast-agent, either for production or throwaway prototypes/mocks/etc.

    3.9k GitHub stars~220 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Site Check

    guardana/guardana

    Check the landing page and the generated documentation site (site/, guardana.dev) in a real browser — confirm a page renders after a docs change, review it at phone width, read the console and…

    259 GitHub stars~679 tokensUpdated today
    Frontend & DesignAuto-check passed
  • NSFC Literature Review Writer

    HuiyuLi-2000/Chinese-Grant-Writer-Skills

    Writes the research-status literature review and critique section of an NSFC grant proposal, backed by a bundled multi-source literature search.

    439 GitHub starsUsed in 1 repo~1.4k tokens
    Research & ScienceAuto-check: notes
  • Arxiv MCP Server

    blazickjp/arxiv-mcp-server

    A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…

    3.2k GitHub stars~353 tokensUpdated 2 days ago
    Research & ScienceAuto-check passed

More from NVIDIA-AI-Blueprints/deep-researcher-agent

All 15 skills in this repo
  • Deep 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…

    886 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes
  • 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.

    886 GitHub stars~4.4k tokensUpdated yesterday
    Auto-check: notes
  • 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…

    886 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes
  • 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…

    886 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes
  • 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/…

    886 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check: notes
  • 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.

    886 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check: notes

Questions about Deep Researcher Release QA

What does Deep Researcher Release QA do?

A skill your agent uses when validating an Deep Researcher Agent change before opening or merging a PR — choosing and running the right Python, frontend, docs, or eval checks for the surfaces you…. Deep Researcher Release QA is an agent skill from NVIDIA-AI-Blueprints/deep-researcher-agent. Use when validating an Deep Researcher Agent change before opening or merging a PR — choosing and running the right Python, frontend, docs, or eval checks for the surfaces you touched instead of one fixed command list.

When should I use Deep Researcher Release QA?

Deep Researcher Release QA fits situations like: validating an Deep Researcher Agent change before opening; merging a PR — choosing and running the right Python; eval checks for the surfaces you touched instead of one fixed command list.

How do I install Deep Researcher Release QA in Claude Code?

Run `npx skills add NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-release-qa -a claude-code`. Or copy the skill folder (.agents/skills/deep-researcher-release-qa in NVIDIA-AI-Blueprints/deep-researcher-agent) into .claude/skills/deep-researcher-release-qa in your project. Claude Code loads it when a task matches its description.

How do I install Deep Researcher Release QA in Codex?

Run `npx skills add NVIDIA-AI-Blueprints/deep-researcher-agent --skill deep-researcher-release-qa -a codex`. Or copy the skill folder (.agents/skills/deep-researcher-release-qa in NVIDIA-AI-Blueprints/deep-researcher-agent) into .agents/skills/deep-researcher-release-qa in your project. Codex loads it when a task matches its description.

Can I use Deep Researcher Release QA 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-release-qa -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-release-qa, .gemini/skills/deep-researcher-release-qa, .github/skills/deep-researcher-release-qa and .opencode/skills/deep-researcher-release-qa in your project.

What does Deep Researcher Release QA need to run?

Going by SKILL.md and its folder, Deep Researcher Release QA needs the command-line tools its instructions call (uv, npm, git and ruff). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Bash. Compatibility (from SKILL.md): Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools..

Does Deep Researcher Release QA access the network?

SKILL.md contains no URLs. Its commands use uv, npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Deep Researcher Release QA safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; 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 Release QA use?

Deep Researcher Release QA 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 Release QA use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 905 tokens, read only when the agent opens those files.

What are the alternatives to Deep Researcher Release QA?

Skills that share tags, products or a category with Deep Researcher Release QA: Docs (PrefectHQ/fastmcp, 28k stars), Jarvis Setup (ethanplusai/jarvis, 846 stars), Fast Agent Design (evalstate/fast-agent, 3.9k stars) and Site Check (guardana/guardana, 259 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deep Researcher Release QA?

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.