update-skills

Name: update-skills
Availability: InStock
Author: aadorian

Capture repository learnings as reusable skills or instructions.

Updated Mar 28, 2026

Search Tags:#workflow #documentation #skills #repository #knowledge capture #instructions #learnability

Ready to run

npx skills add https://github.com/aadorian/VSCode_Readme --skill update-skills-aadorian

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/aadorian/VSCode_Readme/tree/main/education/sessions-chat-and-agents/sessions/skills/update-skills
Command: npx skills add https://github.com/aadorian/VSCode_Readme --skill update-skills-aadorian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps preserve important repository knowledge so repeated discoveries, tricky pitfalls, and durable process improvements do not get lost after a single session.

Core Features & Use Cases

Learning capture: Decides whether a discovery belongs in an existing instruction, a new instruction, or a standalone skill.
Repository organization: Points the content to the right place so future sessions can load it automatically or invoke it by name.
Use Case: When a recurring bug pattern or architectural constraint is uncovered, use this Skill to turn the finding into a reusable reference instead of rediscovering it later.

Quick Start

Ask the assistant to capture the major learning as a reusable skill or instruction in the appropriate repository location.

Frequently Asked Questions about update-skills

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

FAQPage Schema

How do I capture repository learnings as reusable instructions or skills?▼

To capture repository learnings, ask the assistant to document recurring patterns, architectural constraints, or pitfalls. The skill decides whether to update an existing instruction, create a new instruction, or generate a standalone skill with clear examples.

How do I save non-obvious pitfalls so I don't rediscover them in future sessions?▼

Save non-obvious pitfalls by converting the discovery into a reusable reference. The skill routes the captured knowledge to the correct repository location so future sessions can automatically load it or invoke it by name.

What is the best way to document architectural constraints discovered during a coding session?▼

The best way to document architectural constraints is to turn the finding into a standalone skill or instruction. This ensures durable process improvements are preserved and automatically loaded in future repository sessions.

When should I update an existing instruction versus creating a new standalone skill?▼

Update an existing instruction when the learning fits current repository guidelines; create a new standalone skill when capturing distinct recurring patterns or domain knowledge that require clear examples and dedicated guidance.

Can I organize repository knowledge so future sessions automatically load specific instructions?▼

Yes, you can organize repository knowledge by pointing captured learnings to the right place. The skill structures the content so future sessions can automatically load the instructions or invoke the skill by name.

Does capturing workflow knowledge as a skill require any specific dependencies?▼

No dependencies are required to capture workflow knowledge as a skill. The skill directly processes repository learnings and generates instructions or standalone skills without external components.