update-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.

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.

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.

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.

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.

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.