update-skill

Update Claude Code skill documentation by analyzing troubleshooting conversation history.

1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/asnar00/miso --skill update-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skill
Source: https://github.com/asnar00/miso/tree/main/.claude/skills/update-skill
Command: npx skills add https://github.com/asnar00/miso --skill update-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of improving existing Claude Code skills by incorporating learnings from troubleshooting and usage. It ensures that skill documentation evolves, preventing repeated issues and making skills more robust and reliable over time, saving future debugging effort.

Core Features & Use Cases

  • Intelligent Documentation Updates: Analyzes conversation history to identify problems, solutions, and missing context, then applies targeted edits to the SKILL.md file.
  • Targeted Edits: Adds prerequisites, enhances instructions, expands troubleshooting sections, or updates frontmatter based on discovered needs.
  • Use Case: After resolving a "device not found" error with an iOS deployment skill, use this skill to update the ios-deploy-usb documentation with the exact steps to enable developer mode and trust the device, so the issue doesn't recur.

Quick Start

Update the 'ios-deploy-usb' skill based on the recent troubleshooting about VPN interference.

Frequently Asked Questions about update-skill

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

FAQPage Schema
How do I update skill documentation after troubleshooting an issue?

Update skill documentation by analyzing your conversation history to identify the problem, solution, and missing context, then apply targeted edits to the skill's SKILL.md file. This automates incorporating learnings into prerequisites, instructions, troubleshooting sections, or frontmatter based on what you discovered during debugging.

What should I document in a skill's troubleshooting section to prevent recurring issues?

Document the exact steps and root causes from issues you've resolved—such as enabling developer mode or configuring environment variables. Capturing these learnings in the troubleshooting section ensures future users avoid the same problems and reduces debugging effort across repeated skill executions.

Can I automate improvements to existing skill documentation based on real usage?

Yes, this skill automates documentation improvements by extracting root causes and fixes from troubleshooting conversation history, then applying targeted edits to prerequisites, instructions, troubleshooting, and frontmatter. This makes skills more robust and prevents repeated issues over time.

When should I update a skill's SKILL.md file instead of just fixing the code?

Update SKILL.md when troubleshooting reveals missing prerequisites, incomplete instructions, or undocumented edge cases—not just code bugs. Documentation updates ensure the next user with the same problem finds the answer immediately without repeating your debugging work.

What metadata and formatting requirements must skill documentation follow?

Skill documentation must maintain valid YAML frontmatter, proper Markdown formatting, and categorized sections for prerequisites, instructions, and troubleshooting. This skill validates your edits to ensure documentation remains parseable and consistent across all skills.