Skip to content

feat(docs): improve skill and documentation - #374

Merged
rapids-bot[bot] merged 2 commits into
NVIDIA-AI-Blueprints:release/2.2from
soumilinandi:feat/fdr-feedback
Jul 21, 2026
Merged

feat(docs): improve skill and documentation#374
rapids-bot[bot] merged 2 commits into
NVIDIA-AI-Blueprints:release/2.2from
soumilinandi:feat/fdr-feedback

Conversation

@soumilinandi

@soumilinandi soumilinandi commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Overview

Addresses FDR feedback for the AI-Q release docs and public skills:

  • Adds missing Helm documentation for Modal sandbox and S3-compatible artifact storage environment variables [minor]
  • Corrects the local NIMs GPU-memory note so it matches the nvidia/nemotron-3-super-120b-a12b model used in the example.
  • Updates public skill headings to the expected When to Use This Skill and Workflow format.
  • Adds simple sibling-distractor negative eval cases for aiq-deploy and aiq-research.

DCO sign-off for the squash commit

Signed-off-by: Soumili Nandi soumilin@nvidia.com

Validation

  • I ran the relevant local checks or explained why they are not applicable.
  • I added or updated tests for behavior changes.
  • I updated documentation for user-facing or contributor-facing changes.
  • I confirmed this PR does not include secrets, credentials, or internal-only data.
  • I certify this contribution under the Developer Certificate of Origin (DCO) and signed my commits with git commit -s or an equivalent sign-off.
  • I replaced the DCO sign-off placeholder with my GitHub commit identity and kept the required angle brackets around the email address.

Validation run:

doc changes - skill validated using invoking via Agent

Where should reviewers start?

Start with:

  • skills/aiq-deploy/SKILL.md
  • skills/aiq-research/SKILL.md
  • skills/aiq-deploy/evals/evals.json
  • skills/aiq-research/evals/evals.json

The docs-only deployment updates are in:

  • deploy/helm/README.md
  • docs/source/examples/cli-with-local-nims.md

Related Issues

  • Relates to #

Summary by CodeRabbit

  • Documentation

    • Extended deployment guidance with additional optional artifact storage provider and credential configuration details.
    • Updated local NIM GPU sizing guidance to avoid fixed VRAM targets and instead reference current model requirements and hardware inspection.
    • Refreshed headings in deployment and research workflow guides for clearer structure.
  • Tests

    • Added new eval scenarios to verify correct handling of negative research/deployment requests and routing/initialization behavior.
  • Maintenance

    • Adjusted a Python dependency version constraint for improved compatibility.

Signed-off-by: Soumili Nandi <soumilin@nvidia.com>
@soumilinandi
soumilinandi requested a review from a team July 21, 2026 19:30
@soumilinandi
soumilinandi changed the base branch from develop to release/2.2 July 21, 2026 19:31
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: babd32eb-3eeb-49e7-a4fc-6ffbf5afefe0

📥 Commits

Reviewing files that changed from the base of the PR and between 8c3ac75 and baf138a.

⛔ Files ignored due to path filters (1)
  • mcp/uv.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • mcp/pyproject.toml
📜 Recent review details
⏰ Context from checks skipped due to timeout. (4)
  • GitHub Check: Run Harbor skill eval
  • GitHub Check: Lint and Hooks
  • GitHub Check: Script Validation
  • GitHub Check: Pytest and Coverage
🧰 Additional context used
📓 Path-based instructions (1)
{.github/**,ci/**,.pre-commit-config.yaml,pyproject.toml,uv.lock,mcp/pyproject.toml,mcp/uv.lock}

⚙️ CodeRabbit configuration file

{.github/**,ci/**,.pre-commit-config.yaml,pyproject.toml,uv.lock,mcp/pyproject.toml,mcp/uv.lock}: Review automation and packaging changes for least-privilege permissions, pinned versions where appropriate,
copy-pr-bot pull-request/ branch behavior, reproducible uv/npm setup, secret handling, and consistency with
the documented validation matrix.

Files:

  • mcp/pyproject.toml
🔇 Additional comments (1)
mcp/pyproject.toml (1)

74-74: LGTM!


Walkthrough

Documentation adds optional artifact-storage secrets and revises local NIM GPU guidance. Skill headings and cross-skill routing evaluations are updated, and the pyasn1 dependency constraint is raised.

Changes

Documentation, skill evaluation, and dependency updates

Layer / File(s) Summary
Artifact configuration and local NIM guidance
deploy/helm/README.md, docs/source/examples/cli-with-local-nims.md
Documents optional Modal and artifact-storage settings, and replaces fixed VRAM guidance with model-card and nvidia-smi-based sizing instructions.
Skill documentation structure
skills/aiq-deploy/SKILL.md, skills/aiq-research/SKILL.md
Renames the main sections to “When to Use This Skill” and “Workflow” while retaining their existing content.
Cross-skill routing evaluations
skills/aiq-deploy/evals/evals.json, skills/aiq-research/evals/evals.json
Adds negative cases preventing premature deployment routing for research requests and research routing for deployment requests.
Dependency version constraint
mcp/pyproject.toml
Raises the pyasn1 override minimum from 0.6.3 to 0.6.4 while retaining the <0.7 bound.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title uses Conventional Commits correctly and summarizes the docs and skills updates without exceeding the length limit.
Description check ✅ Passed The description follows the template and covers overview, DCO, validation, reviewers, and issues, though a few sections are only minimally filled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@deploy/helm/README.md`:
- Around line 366-374: Update the aiq-credentials rotation procedure to preserve
or recreate all documented optional credentials alongside the four required
keys, including Modal, artifact-storage, and AWS S3 values listed in the
environment-variable table. Ensure the secret workflow remains
configuration-parity with the supported keys documented near MODAL_TOKEN_ID and
AIQ_ARTIFACT_BLOB_PROVIDER.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 8c000933-a262-4e63-a063-f4a6eee45033

📥 Commits

Reviewing files that changed from the base of the PR and between babbcd9 and 8c3ac75.

📒 Files selected for processing (6)
  • deploy/helm/README.md
  • docs/source/examples/cli-with-local-nims.md
  • skills/aiq-deploy/SKILL.md
  • skills/aiq-deploy/evals/evals.json
  • skills/aiq-research/SKILL.md
  • skills/aiq-research/evals/evals.json
📜 Review details
⏰ Context from checks skipped due to timeout. (2)
  • GitHub Check: Run Harbor skill eval
  • GitHub Check: Pytest and Coverage
🧰 Additional context used
📓 Path-based instructions (5)
docs/source/**/*

📄 CodeRabbit inference engine (AGENTS.md)

Update the docs under docs/source/ when behavior, configuration, or workflows change

Files:

  • docs/source/examples/cli-with-local-nims.md
{docs/**,README.md,CONTRIBUTING.md,SECURITY.md,CODE-OF-CONDUCT.md}

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,SECURITY.md,CODE-OF-CONDUCT.md}: Review documentation for command accuracy, branch-name consistency, current CI and copy-pr-bot behavior, public
vs internal boundary clarity, stale examples, and links that no longer match the repository layout.

Files:

  • docs/source/examples/cli-with-local-nims.md
{deploy/**,configs/**}

⚙️ CodeRabbit configuration file

{deploy/**,configs/**}: Review deployment and config changes for secret separation, safe defaults, local-vs-production behavior, Helm and
Docker portability, and documentation parity. Flag committed credentials, environment-specific NVIDIA internals in
public defaults, and changes that make examples diverge from CI-tested paths.

Files:

  • deploy/helm/README.md
{skills/**,.agents/skills/**,.claude/skills/**,.github/skill-eval/**}

⚙️ CodeRabbit configuration file

{skills/**,.agents/skills/**,.claude/skills/**,.github/skill-eval/**}: Review Agent Skill and skill-eval changes for valid skill metadata, deterministic eval specs, safe handling of
credentials, and clear generated-output boundaries. Do not flag SKILL.md files for missing SPDX headers when the
entrypoint intentionally starts with YAML frontmatter.

Files:

  • skills/aiq-research/evals/evals.json
  • skills/aiq-deploy/evals/evals.json
  • skills/aiq-deploy/SKILL.md
  • skills/aiq-research/SKILL.md
skills/aiq-research/**/SKILL.md

📄 CodeRabbit inference engine (skills/aiq-research/SKILL.md)

skills/aiq-research/**/SKILL.md: Use this skill only for research-shaped requests; do not use it for install, deploy, start, stop, UI, CLI, Docker, Helm, or troubleshooting requests.
Run the health command before sending research requests.
Before sending a user query, state the exact AI-Q backend URL that will receive it; use non-local URLs only after the user explicitly confirms they are trusted.
Do not send credentials, cookies, bearer tokens, API keys, basic-auth credentials, or other secret values in query text or AIQ_SERVER_URL.
If no backend is reachable, ask for a backend URL or hand off to aiq-deploy; do not fabricate a research answer.
If the backend returns HTTP 401 or 403, stop and explain that this public skill does not manage authentication; do not retry until authentication is resolved.
Poll asynchronous research jobs when a job_id is returned, and stop on failed, failure, or cancelled jobs without retrying automatically.
Present completed reports with citations and source URLs intact; do not truncate them.
Use status, report, or research_poll to resume interrupted jobs because jobs continue server-side.
For report questions answerable from an existing report, answer directly without calling the backend again; use a fresh request only when new investigation is needed.
For a redo, treat the request as a new job: state and verify the target endpoint again, then poll and present the result using the normal workflow.
Use the configured AIQ_SERVER_URL, defaulting to http://localhost:8000 when it is unset.
Only proceed when the Blueprint version is compatible with skill version 2.2.0: matching major version and Blueprint minor version greater than or equal to 2.2.
When materializing artifacts, use the provided artifact download or portable report commands and preserve rewritten artifact links in shareable reports.

Files:

  • skills/aiq-research/SKILL.md
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: NVIDIA-AI-Blueprints/aiq

Timestamp: 2026-07-21T19:31:22.628Z
Learning: When no deployment mode is specified, ask the user to choose Skill backend, CLI, UI, or Custom before starting services; do not ask this when the mode is already specified or when `aiq-research` has routed a backend request.
Learnt from: CR
Repo: NVIDIA-AI-Blueprints/aiq

Timestamp: 2026-07-21T19:31:22.628Z
Learning: After deployment, report the verified `AIQ_SERVER_URL` to `aiq-research`, and do not continue into deep research or deep-research completion validation unless the user requests or confirms it.
Learnt from: CR
Repo: NVIDIA-AI-Blueprints/aiq

Timestamp: 2026-07-21T19:31:22.628Z
Learning: When troubleshooting port conflicts, identify the process first and obtain user approval before stopping it; alternatively configure a different deployment port and revalidate health.
Learnt from: CR
Repo: NVIDIA-AI-Blueprints/aiq

Timestamp: 2026-07-21T19:31:22.628Z
Learning: Use `configs/config_web_default_llamaindex.yml` for the default Skill backend when API-enabled configuration is required by `aiq-research`.
🔇 Additional comments (5)
docs/source/examples/cli-with-local-nims.md (1)

205-206: LGTM!

skills/aiq-deploy/SKILL.md (1)

27-27: LGTM!

Also applies to: 62-62

skills/aiq-research/SKILL.md (1)

35-35: LGTM!

Also applies to: 67-67

skills/aiq-deploy/evals/evals.json (1)

30-41: LGTM!

skills/aiq-research/evals/evals.json (1)

45-56: LGTM!

Comment thread deploy/helm/README.md

@AjayThorve AjayThorve left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Signed-off-by: Soumili Nandi <soumilin@nvidia.com>
@AjayThorve

Copy link
Copy Markdown
Member

/merge

@rapids-bot
rapids-bot Bot merged commit 0e3cafa into NVIDIA-AI-Blueprints:release/2.2 Jul 21, 2026
11 checks passed
@AjayThorve AjayThorve added this to the v2.2 milestone Jul 21, 2026
@coderabbitai coderabbitai Bot mentioned this pull request Jul 22, 2026
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants