agent-availability-report
Skill115 starsChanged 55 days agoApache-2.0View on GitHub
Generate a production availability report for NVIDIA Elements packages, skill registry, and documentation.
- Installs packages
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- projects/starters/angular/AGENTS.mdAGENTS.md
- projects/starters/bundles/AGENTS.mdAGENTS.md
- projects/starters/eleventy/AGENTS.mdAGENTS.md
- projects/starters/eleventy-ssr/AGENTS.mdAGENTS.md
- projects/starters/go/AGENTS.mdAGENTS.md
- projects/starters/go-htmx/AGENTS.mdAGENTS.md
- projects/starters/hugo/AGENTS.mdAGENTS.md
- projects/starters/importmaps/AGENTS.mdAGENTS.md
- projects/starters/lit-library/AGENTS.mdAGENTS.md
- projects/starters/mcp-app/AGENTS.mdAGENTS.md
- projects/starters/mpa/AGENTS.mdAGENTS.md
- projects/starters/nextjs/AGENTS.mdAGENTS.md
- projects/starters/nuxt/AGENTS.mdAGENTS.md
- projects/starters/react/AGENTS.mdAGENTS.md
- projects/starters/solidjs/AGENTS.mdAGENTS.md
- projects/starters/sphinx/AGENTS.mdAGENTS.md
- projects/starters/svelte/AGENTS.mdAGENTS.md
- projects/starters/typescript/AGENTS.mdAGENTS.md
- projects/starters/vue/AGENTS.mdAGENTS.md
- agent-debug-ciSkill
- agent-dependenciesSkill
- agent-startersSkill
- agent-upkeepSkill
- agent-web-modernizationSkill
- audit-accessibilitySkill
- audit-ciSkill
- audit-codeSkill
- audit-consolidationSkill
- audit-simplificationSkill
- authoring-benchmarksSkill
- authoring-componentsSkill
- authoring-documentationSkill
- authoring-examplesSkill
- authoring-patternsSkill
- authoring-projectsSkill
- authoring-testsSkill
- authoring-typescriptSkill
- elementsSkill
- github-dependabotSkill
- guidance-api-designSkill
- guidance-buildSkill
- guidance-webgpu-performanceSkill
- summarize-releasesSkill
- summarize-video-releasesSkill
- troubleshootingSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Verify that the latest NVIDIA Elements packages are available on npm, confirm the Elements skill installs from GitHub, confirm the …
- Distinctive: line 16
Read the root AGENTS.md.
- Very specific: line 17
Run from the repository root with the pinned toolchain through mise.
- Distinctive: line 22
Run the deterministic report script:
- Very specific: line 42
Do not repeat those lists or the report format in this skill.
- Distinctive: line 69
Run the deterministic script from the repository root.
- Distinctive: line 71
If the script exits non-zero after printing a report, still use the printed report and treat the exit code as the failure signal.
- Distinctive: line 73
Do not rewrite, summarize, or recompute the generated report.
- Very specific: line 79
Use --json to print structured report data.
- Very specific: line 80
Use --timestamp <iso-utc> only for deterministic verification.
- Very specific: line 81
Stop early only for environment-level problems, such as missing npm.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Availability Report
You are an Elements package availability verification agent.
Goal
Verify that the latest NVIDIA Elements packages are available on npm, confirm the Elements skill installs from GitHub, confirm the documentation site is live, and generate a brief status report.
Prepare the Run
- Read the root
AGENTS.md. - Run from the repository root with the pinned toolchain through
mise. - Preserve the current worktree. The report must not change tracked files.
Deterministic Script
Run the deterministic report script:
mise exec -- node .agents/skills/agent-availability-report/scripts/generate-availability-report.jsThe script is the source of truth for:
- package order through
PACKAGES - docs URL order through
DOCS_URLS - npm metadata checks
- npm install checks
- Node package resolution checks
- Elements skill installation through the public
skillsCLI - docs URL checks
- package version comparison
- temporary project creation and cleanup
- status calculation
- report formatting
Do not repeat those lists or the report format in this skill. Update scripts/generate-availability-report.js instead.
Script Behavior
The CLI prints timestamped phase updates and 30-second heartbeats for long-running commands to standard error. Concurrent checks can finish in any order. It reserves standard output for the formatted or JSON report and exits with code 1 only when the generated report has overallStatus: "FAIL".
The exported API returns both the formatted report and structured data:
const { formattedReport, report } = await generateReport();Return or surface formattedReport as the generated report.
The script creates temporary projects with:
mkdtemp(path.join(os.tmpdir(), 'nvidia-elements-agent-availability-report-'))npm init -ynpm install --no-audit --no-fund ...mkdtemp(path.join(os.tmpdir(), 'nvidia-elements-agent-skill-availability-'))npx skills@1.7.0 add https://github.com/nvidia/elements --skill elements- verification that
.agents/skills/elements/SKILL.mddeclares theelementsskill
It removes the temporary projects before returning the report.
Report Workflow
- Run the deterministic script from the repository root.
- Return or surface the formatted report produced by the script.
- If the script exits non-zero after printing a report, still use the printed report and treat the exit code as the failure signal.
Do not rewrite, summarize, or recompute the generated report.
Report delivery is outside this skill.
Debugging
- Use
--jsonto print structured report data. - Use
--timestamp <iso-utc>only for deterministic verification. - Stop early only for environment-level problems, such as missing
npm.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

