New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Aicr Creating Guided Demos

by NVIDIA in NVIDIA/aicr

Scaffolds an interactive guided demo script (demos/.sh), live or self-paced, with the Frame → Tell → Show → Close pattern.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Aicr Creating Guided Demos

skills CLI
$ npx skills add NVIDIA/aicr --skill aicr-creating-guided-demos -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/aicr aicr-creating-guided-demos --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/aicr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/aicr-creating-guided-demos .claude/skills/aicr-creating-guided-demos && 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
aicr-creating-guided-demos
GitHub stars
440
Token cost
~929 tokens
SKILL.md length
511 words
Files
2
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

Scaffolds an interactive guided demo script (demos/.sh), live or self-paced, with the Frame → Tell → Show → Close pattern.

  • Works in 4 steps: Frame — the why, for whoever's following… → Tell — name the steps before running… → Show — run the real commands one at a… → …
  • Guided walkthrough
  • SKILL.md covers Overview, When to use, The four beats and Mechanics, plus 3 more sections
  • Runs Shell scripts from its folder

What it does

Aicr Creating Guided Demos is an agent skill from NVIDIA/aicr, published by the product's own GitHub organization. Scaffolds an interactive guided demo script (demos/.sh), live or self-paced, with the Frame → Tell → Show → Close pattern. Triggers on "demo script", "guided walkthrough", "demos/.sh", "live demo".

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skeleton.sh`).

It sits in DevOps & Cloud, covering Project scaffolding and Container orchestration. 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

  • Guided walkthrough
  • Tasks that involve Project scaffolding
  • Tasks that involve Container orchestration

Example prompts

  • “demo script”
  • “guided walkthrough”
  • “demos/.sh”
  • “/aicr-creating-guided-demos”

Requirements

  • A Bash shell

Workflow steps

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

  1. Frame — the why, for whoever's following (a room, or one reader). One or two sentences: what's missing/broken and why it matters. No…
  2. Tell — name the steps before running them, so they have a map. Flag what's slow, what needs the network/VPN, what to watch for.
  3. Show — run the real commands one at a time, pausing before each, streaming their full output. Pre-stage the slow/fragile parts; keep a…
  4. Close — one line on what just happened, plus pointers: docs/ADR, related demos, the source of truth.

What it can do on your machine

Read from SKILL.md and the folder at commit e8f18da. 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

    Ships script files (Shell), which the agent can run.

    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 Creating Guided Demos loads about 929 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~929

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 e8f18da, republished under its Apache-2.0 licence (© NVIDIA). 511 words, ~929 tokens.

Download SKILL.mdSave it as .claude/skills/aicr-creating-guided-demos/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
aicr-creating-guided-demos
description
Scaffolds an interactive guided demo script (demos/*.sh), live or self-paced, with the Frame → Tell → Show → Close pattern. Triggers on "demo script", "guided walkthrough", "demos/*.sh", "live demo".

Creating Guided Demos

Overview

A guided demo is a narrative, not a command dump — and it serves two readers equally: a presenter driving it live for a room, and a lone user stepping through it to learn or reproduce the flow. Either way, at every step they know why they're here, what's about to happen, and what just happened.

Four beats: Frame → Tell → Show → Close. The script is the guide — it paces itself, explains each step, and streams the real tool output so what's watched is the actual thing working.

When to use

  • Building a demos/*.sh to present a CLI/workflow live or to let a user self-walk it (onboarding, learning, reproducing a result).
  • Turning a bare sequence of commands into a self-paced, narrated walkthrough.
  • Not for: non-interactive CI scripts, one-off scratch scripts, or pure reference docs.

The four beats

  1. Frame — the why, for whoever's following (a room, or one reader). One or two sentences: what's missing/broken and why it matters. No commands.
  2. Tell — name the steps before running them, so they have a map. Flag what's slow, what needs the network/VPN, what to watch for.
  3. Show — run the real commands one at a time, pausing before each, streaming their full output. Pre-stage the slow/fragile parts; keep a fallback for anything that can fail.
  4. Close — one line on what just happened, plus pointers: docs/ADR, related demos, the source of truth.

Mechanics

Copy skeleton.sh. It gives you:

  • banner / note / pause / run helpers — numbered sections, dim explanations, an Enter-gated pause per step, and a run that echoes then streams output verbatim. Plus an optional run_expect_fail for steps where a non-zero exit is the expected result (uses || rc=$? so set -euo pipefail doesn't abort).
  • One env config block at the top — every input is an env var; required ones fail fast (validate producer-only inputs inside the producer branch so the skip flag still works), the rest default. Each runner overrides only what differs.
  • Re-runnability — DEMO_NO_PAUSE=1 runs unattended; a skip flag (e.g. SKIP_SETUP=1) reuses pre-staged state. Skip contract: guard the producer, assert the artifact exists (fail loudly), then run the fast steps either way.
Show full SKILL.md (158 more words)Show less

Rules

  • Show real output. Never >/dev/null, never fabricate. Watching the real tool is the point.
  • Don't fake success. Never weaken a gate/threshold to force green — an honest failure is a valid beat.
  • Respect time. Anything multi-minute (deploys, benchmarks, sign-in) is pre-staged; live steps are seconds.
  • Commit-ready by default. No home paths, kubeconfig paths, or private refs; generic defaults. (A throwaway personal demo can relax this.)

Worked example

demos/evidence-demo.sh — the split-leg recipe-evidence walkthrough: Frame (the reachability gap) → Tell (validate → publish → verify) → Show (each leg, streamed, pre-staged with fallbacks) → Close (ADR-007 + related demos). Reads the same whether presented live or run solo.

Common mistakes

  • Command dump, no Frame/Close → the runner never learns why, or what they saw.
  • Slow producer step run live → blows the time budget; pre-stage it and add a skip flag.
  • Hardcoded paths/criteria → not reusable; use env vars and fail fast on required ones.
  • Faked/suppressed output or a weakened gate → destroys the trust the demo exists to build.

© 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

SKILL.md and 1 other file in .agents/skills/aicr-creating-guided-demos of NVIDIA/aicr.

  • SKILL.md
  • skeleton.sh

Open the folder on GitHubat commit e8f18da

Compare with similar skills

Aicr Creating Guided Demos 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.

Aicr Creating Guided Demos compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Aicr Creating Guided Demos this skillNVIDIA/aicr440—~929Automated safety check: PassApache-2.0
Kopiur Designhome-operations/kopiur115—~2.4kAutomated safety check: PassAGPL-3.0
Helm Chart ScaffoldingCybereason-Public/owLSM28013 repos~381Automated safety check: PassGPL-2.0
Helm Chart Scaffoldingdiegosouzapw/awesome-omni-skills159—~2.4kAutomated safety check: PassMIT
NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress5.1k—~1.4kAutomated safety check: PassApache-2.0
Provider Bug Reviewmondoohq/mql412—~2.9kAutomated safety check: PassCustom licence

Similar skills

  • Kopiur Design

    home-operations/kopiur

    Design norms and locked decisions for the Kopiur Kopia-native Kubernetes backup operator (Rust/kube-rs).

    115 GitHub stars~2.4k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Helm Chart Scaffolding

    Cybereason-Public/owLSM

    Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.

    280 GitHub starsUsed in 13 repos~381 tokens
    DevOps & CloudAuto-check passed

  • Helm Chart Scaffolding

    diegosouzapw/awesome-omni-skills

    Helm Chart Scaffolding workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.

    159 GitHub stars~2.4k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed

  • 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.

    5.1k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed

  • 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.

    412 GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check passed

  • 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…

    148 GitHub stars~1.3k tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed

More from NVIDIA/aicr

All 10 skills in this repo

  • Aicr Cross Review

    NVIDIA/aicr

    Official

    Multi-agent PR review using Claude Code, Codex, and CodeRabbit.

    440 GitHub stars~15k tokensUpdated today
    Auto-check passed

  • Aicr Analyzing Snapshots

    NVIDIA/aicr

    Official

    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…

    440 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Aicr Creating Slide Decks

    NVIDIA/aicr

    Official

    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.

    440 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Aicr Release Notes

    NVIDIA/aicr

    Official

    A skill your agent uses when drafting the human-readable GitHub release notes summary for an upcoming AICR release.

    440 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Aicr Reviewing Component Drift

    NVIDIA/aicr

    Official

    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…

    440 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Aicr Uat Report

    NVIDIA/aicr

    Official

    A skill your agent uses when reporting on UAT health across services and GPU targets — which service (EKS/GKE/AKS) x GPU (H100/GB200) x intent combinations are passing or failing in the UAT Run…

    440 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Aicr Creating Guided Demos

What does Aicr Creating Guided Demos do?

Scaffolds an interactive guided demo script (demos/.sh), live or self-paced, with the Frame → Tell → Show → Close pattern. Aicr Creating Guided Demos is an agent skill from NVIDIA/aicr, published by the product's own GitHub organization.sh), live or self-paced, with the Frame → Tell → Show → Close pattern.

When should I use Aicr Creating Guided Demos?

Aicr Creating Guided Demos fits situations like: guided walkthrough; tasks that involve Project scaffolding; tasks that involve Container orchestration.

How do I install Aicr Creating Guided Demos in Claude Code?

Run `npx skills add NVIDIA/aicr --skill aicr-creating-guided-demos -a claude-code`. Or copy the skill folder (.agents/skills/aicr-creating-guided-demos in NVIDIA/aicr) into .claude/skills/aicr-creating-guided-demos in your project. Claude Code loads it when a task matches its description.

How do I install Aicr Creating Guided Demos in Codex?

Run `npx skills add NVIDIA/aicr --skill aicr-creating-guided-demos -a codex`. Or copy the skill folder (.agents/skills/aicr-creating-guided-demos in NVIDIA/aicr) into .agents/skills/aicr-creating-guided-demos in your project. Codex loads it when a task matches its description.

Can I use Aicr Creating Guided Demos 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-creating-guided-demos -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-creating-guided-demos, .gemini/skills/aicr-creating-guided-demos, .github/skills/aicr-creating-guided-demos and .opencode/skills/aicr-creating-guided-demos in your project.

What does Aicr Creating Guided Demos need to run?

Going by SKILL.md and its folder, Aicr Creating Guided Demos needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Aicr Creating Guided Demos 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 Creating Guided Demos 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 Creating Guided Demos use?

Aicr Creating Guided Demos 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 Creating Guided Demos use?

About 929 tokens (SKILL.md is roughly 3.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 Aicr Creating Guided Demos?

Skills that share tags, products or a category with Aicr Creating Guided Demos: Kopiur Design (home-operations/kopiur, 115 stars), Helm Chart Scaffolding (Cybereason-Public/owLSM, 280 stars), Helm Chart Scaffolding (diegosouzapw/awesome-omni-skills, 159 stars) and NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Aicr Creating Guided Demos?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/aicr, which has 440 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 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.