skill-distillation

Extracts reusable procedures from completed tasks and writes them into a skill library.

4.0k|530|Updated May 28, 2025
One-click install
npx skills add https://github.com/isaac-sim/IsaacSim --skill skill-distillation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-distillation
Source: https://github.com/isaac-sim/IsaacSim/tree/main/skills/skill-distillation
Command: npx skills add https://github.com/isaac-sim/IsaacSim --skill skill-distillation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lessons learned during AI-assisted tasks are lost between sessions, forcing agents to rediscover the same fixes and repeat the same debugging loops. This Skill enforces a distillation pass after every task so corrections, workarounds, and novel solutions become reusable procedures in a persistent skill library.

Core Features & Use Cases

  • Trigger-Based Extraction: Automatically runs after user corrections, debugging sessions over three iterations, undocumented workarounds, or heartbeat retrospectives.
  • Classification and Routing: Decides whether new knowledge updates an existing skill, creates a new skill, goes to meta-skills, or belongs in memory as a one-off fact.
  • Library Health Checks: Detects bloat (files over 500 lines), duplication across skills, and stale version references, with sidecar offload rules for scripts, examples, and lessons.
  • Draft Skill Lifecycle: Flags skills created mid-task as high-priority drafts, enforces short check-in cycles, and defines promotion criteria to stable status.
  • Use Case: After a long Isaac Sim debugging session where a rogue RigidBodyAPI caused physics explosions, run the distillation pass to convert that one-off fix into a general asset stability check procedure stored in the library.

Quick Start

Run a distillation pass on the task we just finished and update the skill library with any reusable lessons.

Frequently Asked Questions about skill-distillation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture lessons learned from an AI agent session?

Run a distillation pass after each task: check triggers like user corrections or long debugging, extract the general procedure behind each fix, classify it as a skill update or new skill, then write and verify it in the library.

When should a new skill be created versus updating an existing one?

Update an existing skill when the knowledge fits its scope as a new rule, failure mode, or workflow. Create a new skill only for an entirely new capability, and route one-off facts to memory instead of skills.

Should code snippets be embedded in skill documentation?

No, skills should reference canonical sources like local example files or version-tagged docs rather than embed code, since APIs change between versions. Only tiny config snippets may be embedded with a version comment.

What are the limits of a SKILL.md file?

The body should stay under 500 lines and the description under 1024 characters. Offload long helpers to scripts, dated lessons to a lessons.md sidecar, and deep references to separate markdown files, one level deep only.

How do I handle a skill created during a task that is untested?

Mark it with status draft and high priority in the frontmatter, notify the user, shorten iteration cycles with frequent check-ins, and promote it to stable only after a validated task with user confirmation.