Skill Evolution Agent Skill

Use before creating, editing, or deciding whether to update any AI coding agent skill in this repository, including corrections to existing skill behavior, references, or routing.

636 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

2551

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/NVIDIA/NeMo-Agent-Toolkit --skill skill-evolution

The instruction itself

5 sections, as written by the author

Skill Evolution

Use this skill before creating, editing, or deciding whether to update any AI coding agent skill in this repository.

When to Update Skills

Update a skill when any of the following happens:

A user corrects agent behavior in a way that should generalize.
A command fails and the recovery path should be remembered.
A reference link, command, component _type, or installation instruction is stale.
Task routing is too broad, too narrow, or points to the wrong skill.
A repeated instruction appears in multiple skills and should move to a shared entry point.
A skill contains too much detail and should move detail into focused references.

Do not update skills for one-off user preferences, temporary local environment quirks, or speculative guidance that was not validated.

Update Workflow

Finish the user's requested task first unless the skill update is the task.
Identify the smallest skill that should change.
Keep each SKILL.md concise and task-oriented.
Move detailed examples or long reference material into that skill's references/ directory.
Update AGENTS.md when a new skill is added or task routing changes.
Run Markdown link checks through pre-commit on the changed skill files.

Naming and Layout

Use the flat skills layout:

skills/
  nat-installation/
    SKILL.md
    references/
  nat-workflow-creation/
    SKILL.md
    references/

Each skill folder must contain one SKILL.md with frontmatter:

---
name: skill-name
description: Use when ...
author: NVIDIA Corporation and Affiliates
license: Apache-2.0
---

Use author and license frontmatter instead of long license headers in SKILL.md files.

Use specific names that describe the task surface. Avoid catch-all folders that hide routing information.

Quality Bar

Skills should tell agents what to do, what to read next, and what to validate.
Prefer canonical repository docs over copied long-form explanations.
Keep cross-skill links relative and valid.
Use "NVIDIA NeMo Agent Toolkit" on first prose use, then "NeMo Agent Toolkit" or "the toolkit".
Use nat only for technical identifiers such as the CLI, package name, Python namespace, paths, and environment variables.

Other skills for the same job

different authors, same section of the catalogue

Writing Skills

by ZhanlinCui

×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.

4k tokens

Edge Strategy Designer

by BaggaT236

×1

Convert abstract edge concepts into strategy draft variants and optional exportable ticket YAMLs for edge-candidate-agent export/validation.

7k tokens scripts

Langgraph Fundamentals

by langchain-ai

vendor ×1

INVOKE THIS SKILL when writing ANY LangGraph code. Covers StateGraph, state schemas, nodes, edges, Command, Send, invoke, streaming, and error handling.

6k tokens

Harness Model Protocol

by ComeOnOliver

×1

Analyze the protocol layer between agent harness and LLM model. Use when (1) understanding message wire formats and API contracts, (2) examining tool call encoding/decoding mechanisms, (3) evaluating streaming protocols and partial response handling, (4) identifying agentic chat primitives (system prompts, scratchpads, interrupts), (5) comparing multi-provider abstraction strategies, or (6) understanding how frameworks translate between native LLM APIs and internal representations.

Translate SKILL.md and README.md files into multiple languages for sharing skills internationally

11k tokens

Agent Setup Maintenance

by langfuse

vendor

| Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.

>- Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).

2k tokens

How to use it

Copy the folder

Take nvidia/skill-evolution from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.