update-skills

Captures repository learnings as persistent skills and instructions for future sessions.

10|1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill update-skills-kevinhuangislearning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/KevinHuangIsLearning/shortestpath-ide/tree/main/src/vs/sessions/skills/update-skills
Command: npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill update-skills-kevinhuangislearning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable insights discovered during a coding session—recurring patterns, non-obvious pitfalls, architectural constraints—are lost when the session ends. This Skill captures those learnings as persistent skills or instructions so future sessions benefit from them. ## Core Features & Use Cases - Learning Classification: Decides whether a discovery belongs in an existing instruction, a new skill, or a new instruction file based on scope and reusability. - Structured Capture Workflow: Guides creation of SKILL.md files with correct frontmatter, naming conventions, and placement in .github/skills/ or .agents/skills/. - Quality Validation: Checks that captured knowledge is general, actionable, example-backed, and non-duplicative before saving. - Use Case: After spending an hour debugging a subtle build configuration issue, say "learn!" and the Skill records the root cause and fix as a reusable instruction for all future sessions. ## Quick Start Tell the agent to capture the debugging insight we just found as a new repository skill.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I save a learning from an AI coding session?

Say "learn!" or ask the agent to capture the insight. The Skill evaluates whether the knowledge fits an existing instruction, warrants a new skill, or should become an auto-applied instruction file, then writes it to the appropriate location.

When should I create a skill versus an instruction file?

Create a skill when the knowledge is substantial, covers a distinct domain, and should be invoked by name. Create an instruction when the rule should apply automatically based on file patterns or globally, such as coding conventions or architectural constraints.

Where are repository skills and instructions stored?

Project-level skills go in .github/skills/{name}/SKILL.md and agent-specific skills in .agents/skills/{name}/SKILL.md. Instructions live in .github/instructions/ as .instructions.md files with optional applyTo glob patterns.

What makes a captured learning high quality?

A good learning is general enough to help future sessions, specific enough to be actionable, includes a concrete right-versus-wrong example, and does not duplicate knowledge already captured elsewhere in the repository.

Does the skill name need to match anything specific?

Yes, the name field in the SKILL.md frontmatter must exactly match the parent folder name. This ensures the skill can be discovered and invoked correctly by name in future sessions.