improve-skills

Updates existing SKILL.md files with learnings captured from the current session.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/aminojagh/LLMZC --skill improve-skills-aminojagh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-skills
Source: https://github.com/aminojagh/LLMZC/tree/main/05_02_dlt_workshop/.agents/skills/improve-skills
Command: npx skills add https://github.com/aminojagh/LLMZC --skill improve-skills-aminojagh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skills accumulate value only when real session learnings are written back into them; without a structured process, debugging discoveries, data quirks, and workflow fixes are lost when the session ends. ## Core Features & Use Cases - Session Learning Extraction: Scans the conversation for new error patterns, data and schema surprises, query techniques, and configuration quirks worth capturing. - Lean Skill Updates: Reads each target SKILL.md first, avoids duplication, and appends minimal bullets, short code snippets, or essential doc references to the right section. - Approval-Gated Edits: Presents a summary of proposed updates per skill and applies changes only after user approval, then checks workflow.md cross-references. - Use Case: After a long dlt debugging session where you discovered a pagination quirk and a useful ibis query pattern, run this Skill to fold those findings into the relevant skills so the next session starts smarter. ## Quick Start Ask the assistant to review this session and update the relevant skills with anything new we learned.

Frequently Asked Questions about improve-skills

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

FAQPage Schema
How do I update AI agent skills after a work session?▼

Run the improve-skills workflow at the end of the session. It scans the conversation for new debugging patterns, data issues, and workflow fixes, maps them to active skills, and proposes minimal edits for your approval.

How to keep SKILL.md files from becoming bloated?▼

Add only lean updates: a single bullet or a 3-5 line code snippet per learning. Read the existing SKILL.md first to avoid duplication, and never restructure or rewrite existing content.

What kinds of session learnings should be captured in skills?▼

Capture real problems only: new error types and their diagnostic commands, schema surprises, library-specific gotchas, auth or pagination quirks, and essential documentation links. Skip hypothetical scenarios.

Does improve-skills edit files without confirmation?▼

No. It presents a summary of proposed updates per skill and waits for user approval before editing any SKILL.md file. You can adjust, skip, or extend the proposed changes.

When should I not add a learning to a skill?▼

Skip anything already covered in the skill, anything that did not actually happen in the session, and anything the user did not explicitly ask to capture. Hypothetical or generic advice does not belong in skills.