skill-evolution

AI Community

Repo stars 2,319
License Apache-2.0
Author repo NeMo-Agent-Toolkit

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Use before creating, editing, or deciding whether to update any AI coding agent skill in this repository, including corrections…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to Update Skills”, “Update Workflow”, “Naming and Layout”, “Quality Bar”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-evolution directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to Update Skills / Update Workflow / Naming and Layout” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: AI
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 94 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @NVIDIA · Apache-2.0
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Python
Detected file/system behavior: Read-only
Write / modify
Env read
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-evolution.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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

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

## Naming and Layout

Use the flat skills layout:

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

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

```yaml
---
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.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> When to Update Skills → Update Workflow → Naming and Layout → Quality Bar
terms    -> Use this skill before creating, editing, or deciding whether to update any AI coding agent skill in this repository. · - A user corrects agent behavior in a way that should generalize. · Do not update skills for one-off user preferences, temporary local environment quirks, or speculative guidance that was not validated. · 1. Finish the user's requested task first unless the skill update is the task. · Use author and license frontmatter instead of long license headers in SKILL.md files. · Use specific names that describe the task surface. · - Skills should tell agents what to do, what to read next, and what to validate.
files/cmd -> type · references/ · AGENTS.md · author · license · nat
body sha256 -> 96514d2e244b