NGINX Ingress Controller Feature Checklists
nginx/kubernetes-ingress
Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.
A skill your agent uses when reviewing AICR's Markdown documentation for duplication, drift, bloat, and gaps — to keep docs high-value as the project evolves.
Install Aicr Auditing Docs
$ npx skills add NVIDIA/aicr --skill aicr-auditing-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/aicr aicr-auditing-docs --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/aicr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/aicr-auditing-docs .claude/skills/aicr-auditing-docs && 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 "aicr-auditing-docs" agent skill from https://github.com/NVIDIA/aicr/tree/main/.agents/skills/aicr-auditing-docs into .claude/skills/aicr-auditing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aicr-auditing-docs", 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/aicr/tree/main/.agents/skills/aicr-auditing-docsType 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/aicr --skill aicr-auditing-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/aicr aicr-auditing-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/aicr.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/aicr-auditing-docs .agents/skills/aicr-auditing-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aicr-auditing-docs" agent skill from https://github.com/NVIDIA/aicr/tree/main/.agents/skills/aicr-auditing-docs into .agents/skills/aicr-auditing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aicr-auditing-docs", 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/aicr --skill aicr-auditing-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/aicr aicr-auditing-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/aicr.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/aicr-auditing-docs .cursor/skills/aicr-auditing-docs && 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 "aicr-auditing-docs" agent skill from https://github.com/NVIDIA/aicr/tree/main/.agents/skills/aicr-auditing-docs into .cursor/skills/aicr-auditing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aicr-auditing-docs", 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/aicr.git --path .agents/skills/aicr-auditing-docs--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/aicr --skill aicr-auditing-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/aicr aicr-auditing-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/aicr.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/aicr-auditing-docs .gemini/skills/aicr-auditing-docs && 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 "aicr-auditing-docs" agent skill from https://github.com/NVIDIA/aicr/tree/main/.agents/skills/aicr-auditing-docs into .gemini/skills/aicr-auditing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aicr-auditing-docs", 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/aicr aicr-auditing-docsInstalls 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/aicr --skill aicr-auditing-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/aicr.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/aicr-auditing-docs .github/skills/aicr-auditing-docs && 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 "aicr-auditing-docs" agent skill from https://github.com/NVIDIA/aicr/tree/main/.agents/skills/aicr-auditing-docs into .github/skills/aicr-auditing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aicr-auditing-docs", 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/aicr --skill aicr-auditing-docs -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/aicr aicr-auditing-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/aicr.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/aicr-auditing-docs .opencode/skills/aicr-auditing-docs && 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 "aicr-auditing-docs" agent skill from https://github.com/NVIDIA/aicr/tree/main/.agents/skills/aicr-auditing-docs into .opencode/skills/aicr-auditing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aicr-auditing-docs", 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
aicr-auditing-docs- GitHub stars
- 439
- Token cost
- ~1.7k tokens
- SKILL.md length
- 758 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when reviewing AICR's Markdown documentation for duplication, drift, bloat, and gaps — to keep docs high-value as the project evolves.
- Works in 5 steps: Duplication — same steps/tables/concepts… → Overlap / misplacement — content in the… → Bloat — verbose sections that lose no… → …
- Reviewing AICRs Markdown documentation for duplication
- SKILL.md covers Overview, When to Use, The Map (what to audit, and… and Sources of Truth (drift…, plus 4 more sections
- Calls make
What it does
Aicr Auditing Docs is an agent skill from NVIDIA/aicr, published by the product's own GitHub organization. Use when reviewing AICR's Markdown documentation for duplication, drift, bloat, and gaps — to keep docs high-value as the project evolves. Triggers on "audit the docs", "review documentation", "docs cleanup", "/aicr-auditing-docs", or any request to find redundant/stale/missing docs across README, docs/, demos/, and the root governance files. Produces a prioritized findings report (research, not edits) grouped by the five audit dimensions, anchored to the project's canonical sources of truth.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Container orchestration and Technical documentation. The repository describes itself as: Tooling for optimized, validated, and reproducible GPU-accelerated AI runtime in Kubernetes. The licence is Apache-2.0.
When your agent uses it
- Reviewing AICRs Markdown documentation for duplication
- Gaps — to keep docs high-value as the project evolves
- Review documentation
- /aicr-auditing-docs
Example prompts
- “audit the docs”
- “review documentation”
- “docs cleanup”
- “/aicr-auditing-docs”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Duplication — same steps/tables/concepts in >1 file. Pick the canonical
- Overlap / misplacement — content in the wrong persona tree (e.g.,
- Bloat — verbose sections that lose no value when cut: embedded SBOM/JSON
- Gaps (Diátaxis) — is each of tutorial / how-to / reference / explanation
- Staleness / style violations — TODOs, "(Future)" content shown as usable,
What it can do on your machine
Read from SKILL.md and the folder at commit f4e99c2. 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
Shell commands in SKILL.md call:
make
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
Aicr Auditing Docs loads about 1.7k tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 758 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 NVIDIA/aicr at commit f4e99c2, republished under its Apache-2.0 licence (© NVIDIA). 758 words, ~1,692 tokens.
Download SKILL.mdSave it as
.claude/skills/aicr-auditing-docs/SKILL.md (or your agent's skills folder).- name
- aicr-auditing-docs
- description
- Use when reviewing AICR's Markdown documentation for duplication, drift, bloat, and gaps — to keep docs high-value as the project evolves. Triggers on "audit the docs", "review documentation", "docs cleanup", "/aicr-auditing-docs", or any request to find redundant/stale/missing docs across README, docs/, demos/, and the root governance files. Produces a prioritized findings report (research, not edits) grouped by the five audit dimensions, anchored to the project's canonical sources of truth.
Auditing AICR Documentation
Overview
AICR's docs are mature and already well-structured: a persona split under
docs/ (user / integrator / contributor), a docs hub with glossary
(docs/README.md), ADRs in docs/design/, and a strong root README.md.
The recurring risk is not missing structure — it is duplication and
drift as features land. This skill is a repeatable audit, not a rewrite:
default to a findings report; only edit when explicitly asked.
When to Use
- Periodic doc health check, or before a release.
- After a large feature merges (new CLI flag, API endpoint, component, recipe field).
- When the same explanation appears in multiple files and you suspect drift.
- Not for: writing a single new doc (just write it, following the style
rules below), or generated content (
docs/conformance/,docs/user/container-images.md).
The Map (what to audit, and how it's owned)
| Area | Canonical owner | Notes |
|---|---|---|
| Project pitch, features, supported envs | root README.md | Quick Start may duplicate docs/user/installation.md — acceptable for README only. |
| User how-to / reference | docs/user/ | cli-reference.md owns flags; task narrative belongs in task docs (validation.md, agent-deployment.md). |
| Integration / embedding | docs/integrator/ | Resolver internals belong in contributor/, not here. |
| Project internals | docs/contributor/ | Architecture overview = contributor/index.md. |
| Demos / runbooks | demos/ | GitHub-only (not in fern/docs.yml nav). Terse names hurt discovery. |
| Governance | CONTRIBUTING.md, DEVELOPMENT.md, RELEASE.md, SECURITY.md | Each owns one concern; cross-link instead of repeating. |
| Agent rules | .claude/CLAUDE.md (canonical) → AGENTS.md (CI-synced mirror — never flag) | .github/copilot-instructions.md should be a pointer, not a copy. |
Sources of Truth (drift hotspots — check these first)
Drift between examples and these authoritative sources is the highest-value class of finding:
- Component/chart/image versions →
docs/user/container-images.md(the BOM, regenerated bymake bom-docs). Inline version examples elsewhere (cli-reference.md,api-reference.md,data-flow.md) should be marked illustrative and point here — never hand-pinned to a stale tag. - Tool versions (golangci-lint, Go, Ko) →
.settings.yaml. Never hardcode in prose or sample workflow YAML. - Criteria/enum values (service, accelerator, os, intent, platform, error
codes) → the Go type (e.g.
pkg/recipe/criteria.go). Enums are enumerated in many files; see the enum-audit checklist inCLAUDE.md→ Documentation updates. - API shape →
api/aicr/v1/server.yaml(OpenAPI). The component lists and response samples inapi-reference.mddrift from the registry — diff them.
The Five Audit Dimensions
Run every file through these. Group findings by dimension, prioritized.
- Duplication — same steps/tables/concepts in >1 file. Pick the canonical
owner (table above), trim the rest to a cross-link. Known repeat offenders:
agent/snapshot deployment, recipe-evidence walkthrough, constraint
paths/operators table,
make-target block, DCO/signing rules, the sixdemos/cuj*-{eks,gke}.mdfiles (~80% shared). - Overlap / misplacement — content in the wrong persona tree (e.g.,
resolver internals in
integrator/, agent deployment inintegrator/when it's a user concern), or a topic split awkwardly across files. - Bloat — verbose sections that lose no value when cut: embedded SBOM/JSON
dumps, repeated
export TAG=blocks, stub code that contradicts the architecture ("AICR is not a controller"), generic K8s boilerplate that isn't AICR-specific, walls of text needing structure. - Gaps (Diátaxis) — is each of tutorial / how-to / reference / explanation
present for the persona? Known holes: no end-to-end tutorial
(install→recipe→bundle→deploy→validate), no
aicr bundlehow-to. - Staleness / style violations — TODOs, "(Future)" content shown as usable,
contradictory version numbers, leftover template placeholders
(
__AICR (AICR)__), and violations of the repo's own doc-style rules below.
Show full SKILL.md (250 more words)Show less
Repo Doc-Style Rules (enforce during audit)
These are defined in CLAUDE.md → Documentation Style; flag violations:
- Auto-anchors, no manual TOCs — GitHub/Fern generate anchors. Manual
## Table of Contentsblocks (present inCONTRIBUTING.md,DEVELOPMENT.md) are violations. - Promote
**Bold Label:**to a heading sparingly — only a named topic with ≥ ~8 lines beneath it. - Anchor hygiene — when renaming/removing a heading, grep
<file>.md#<old-slug>repo-wide and fix inbound links. Broken anchors fail CI via lychee on anydocs/**PR (.github/workflows/fern-docs-ci.yaml) — but notmake qualify.
How to Run It
- Parallelize by area to protect context: dispatch one research agent per
tree — (a)
docs/persona trees, (b) root + agent docs, (c)demos/. Give each the five dimensions and the sources-of-truth list; ask for a concise (<600 word) report with file paths and concrete recommendations. - Synthesize into one prioritized report. Lead with version/enum drift (highest value), then duplication consolidations, then bloat/gaps.
- Report, don't rewrite by default. If asked to fix: one focused PR per
theme (e.g., "de-dup agent deployment", "trim SECURITY.md"), keep diffs
reviewable, and after any change run
make qualify(and note lychee is separate). Touchingdocs/**requires the lychee anchor check.
Common Mistakes
- Flagging the
AGENTS.md↔CLAUDE.mdmirror as duplication — it's intentional and CI-enforced. - Recommending a TOC "for navigation" — violates the auto-anchor rule.
- Hand-fixing a version in an example — fix the pattern (mark illustrative,
link to
container-images.md) so it can't re-drift. - Editing generated files (
container-images.md,docs/conformance/) directly instead of their generators. - Auditing one file in isolation — duplication only shows up across files; read the tree.
© NVIDIA, 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
Just SKILL.md in .agents/skills/aicr-auditing-docs of NVIDIA/aicr.
Open the folder on GitHubat commit f4e99c2
Compare with similar skills
Aicr Auditing Docs 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 |
|---|---|---|---|---|---|---|
| Aicr Auditing Docs this skillNVIDIA/aicr | 439 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress | 5.1k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Obsidian WriterAtmosphere/atmosphere | 3.8k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Provider Bug Reviewmondoohq/mql | 411 | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Kubelb Dependency Updateskubermatic/kubelb | 148 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Karmada Dashboard Quickstartkarmada-io/dashboard | 105 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Obsidian Writer
Atmosphere/atmosphere
Write well-formatted notes to the atmosphere-vault Obsidian knowledge base.
Provider Bug Review
mondoohq/mql
Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.
Kubelb Dependency Updates
kubermatic/kubelb
Sweep and update every dependency surface in the kubelb repo (go.mod, Makefile tool versions, prow images, GitHub Actions, hack/ci pins, addon Helm charts, pinned container images) and split the…
Karmada Dashboard Quickstart
karmada-io/dashboard
QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access.
- Official
Ama Logs Update Charts Release Notes
microsoft/Docker-Provider
Prepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry.
More from NVIDIA/aicr
All 10 skills in this repo- Official
Aicr Cross Review
NVIDIA/aicr
Multi-agent PR review using Claude Code, Codex, and CodeRabbit.
- Official
Aicr Analyzing Snapshots
NVIDIA/aicr
A skill your agent uses when analyzing an AICR snapshot YAML file, reviewing cluster state, comparing provider characteristics, extracting GPU/network topology insights, or generating a cluster…
- Official
Aicr Creating Guided Demos
NVIDIA/aicr
Scaffolds an interactive guided demo script (demos/.sh), live or self-paced, with the Frame → Tell → Show → Close pattern.
- Official
Aicr Creating Slide Decks
NVIDIA/aicr
A skill your agent uses when building a self-contained HTML slide deck or visual talking-point for a technical concept or workflow (e.g.
- Official
Aicr Release Notes
NVIDIA/aicr
A skill your agent uses when drafting the human-readable GitHub release notes summary for an upcoming AICR release.
- Official
Aicr Reviewing Component Drift
NVIDIA/aicr
A skill your agent uses when reviewing the weekly AICR component drift report — the Slack digest and drift-report.json artifact produced by Registry Drift Report (registry-drift.yaml) listing which…
Related
Categories
Questions about Aicr Auditing Docs
What does Aicr Auditing Docs do?
A skill your agent uses when reviewing AICR's Markdown documentation for duplication, drift, bloat, and gaps — to keep docs high-value as the project evolves. Aicr Auditing Docs is an agent skill from NVIDIA/aicr, published by the product's own GitHub organization. Use when reviewing AICR's Markdown documentation for duplication, drift, bloat, and gaps — to keep docs high-value as the project evolves.
When should I use Aicr Auditing Docs?
Aicr Auditing Docs fits situations like: reviewing AICRs Markdown documentation for duplication; gaps — to keep docs high-value as the project evolves; review documentation; /aicr-auditing-docs.
How do I install Aicr Auditing Docs in Claude Code?
Run `npx skills add NVIDIA/aicr --skill aicr-auditing-docs -a claude-code`. Or copy the skill folder (.agents/skills/aicr-auditing-docs in NVIDIA/aicr) into .claude/skills/aicr-auditing-docs in your project. Claude Code loads it when a task matches its description.
How do I install Aicr Auditing Docs in Codex?
Run `npx skills add NVIDIA/aicr --skill aicr-auditing-docs -a codex`. Or copy the skill folder (.agents/skills/aicr-auditing-docs in NVIDIA/aicr) into .agents/skills/aicr-auditing-docs in your project. Codex loads it when a task matches its description.
Can I use Aicr Auditing Docs 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/aicr --skill aicr-auditing-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aicr-auditing-docs, .gemini/skills/aicr-auditing-docs, .github/skills/aicr-auditing-docs and .opencode/skills/aicr-auditing-docs in your project.
What does Aicr Auditing Docs need to run?
Going by SKILL.md and its folder, Aicr Auditing Docs needs the command-line tools its instructions call (make).
Does Aicr Auditing Docs 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 Aicr Auditing Docs 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 Aicr Auditing Docs use?
Aicr Auditing Docs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Aicr Auditing Docs use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Aicr Auditing Docs?
Skills that share tags, products or a category with Aicr Auditing Docs: NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars), Obsidian Writer (Atmosphere/atmosphere, 3.8k stars), Provider Bug Review (mondoohq/mql, 411 stars) and Kubelb Dependency Updates (kubermatic/kubelb, 148 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Aicr Auditing Docs?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/aicr, which has 439 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 8, 2026.
Source: NVIDIA/aicr on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.