update-skills

Creates or updates repository skills and instructions from session learnings.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill update-skills-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/Tyrizx/Tyrizx/tree/main/src/vs/sessions/skills/update-skills
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill update-skills-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable insights discovered during a coding session — recurring patterns, non-obvious pitfalls, architectural constraints — are often 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 Capture: Converts session discoveries into reusable knowledge stored in .github/skills/, .agents/skills/, or .github/instructions/. - Decision Guidance: Provides clear criteria for choosing between adding a learning to an existing file, creating a new skill, or creating an auto-applied instruction. - Quality Checks: Enforces standards so captured knowledge is general, actionable, example-driven, and non-duplicative. - Use Case: After spending an hour debugging a subtle build configuration issue, say "learn!" to have the root cause and correct approach documented as a skill that future sessions can invoke by name. ## Quick Start Tell the agent "learn!" after discovering a significant pattern or pitfall so it captures the insight as a skill or instruction file.

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 my current session?▼

Say "learn!" or ask the agent to capture the learning. The skill identifies the insight, checks for existing skills and instructions, then either appends to an existing file's Learnings section or creates a new skill or instruction file.

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 skills and instructions stored in a repository?▼

Project-level skills go in .github/skills/{name}/SKILL.md, agent-specific skills in .agents/skills/{name}/SKILL.md, and auto-applied instructions in .github/instructions/{name}.instructions.md. The skill name must match its parent folder name exactly.

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 example of right versus wrong, avoids duplicating existing knowledge, and has a description clear enough to indicate when it should be invoked.

Can I update an existing skill instead of creating a new one?▼

Yes. If an existing skill or instruction covers the topic, add the insight to its Learnings section in one to four sentences. The skill checks existing files with directory listings and grep searches before creating anything new.