skill-updater

Update and repackage existing Claude skills from a writable working directory.

40|5|Updated Mar 9, 2026

Search Tags:#workflow automation #packaging #change management #skill editing #read-only filesystem #cross-skill deduplication #installation artifacts

Ready to run

npx skills add https://github.com/ShawhinT/non-coding-skills --skill skill-updater-shawhint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-updater
Source: https://github.com/ShawhinT/non-coding-skills/tree/main/skill-updater
Command: npx skills add https://github.com/ShawhinT/non-coding-skills --skill skill-updater-shawhint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you update and repackage an existing Claude skill without trying to edit it in place on a read-only filesystem, preventing common packaging and permission failures.

Core Features & Use Cases

Change planning before editing: Summarizes proposed additions/modifications, suggested removals, and runs a cross-skill scan to flag duplication so updates stay clean and maintainable.
Read-only safe workflow: Copies the skill to a writable session directory, applies edits there, and verifies the result before packaging.
Correct packaging sequence: Runs the packaging step from the skill-creator directory with the correct positional arguments and then renames the output back to the canonical skill name.

Quick Start

Tell the AI: "Update the existing skill <skill-name> using these feedback points: <paste feedback>, and propose specific additions and removals before making any edits."

Frequently Asked Questions about skill-updater

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

FAQPage Schema

How do I update an existing Claude skill without encountering read-only filesystem errors?▼

To update an existing Claude skill safely, copy the target skill from the installed directory to a writable working session directory, apply edits only to the copy, and then repackage the result to prevent permission failures.

What is the best way to avoid cross-skill duplication when modifying workflow automation skills?▼

Avoiding cross-skill duplication requires running a pre-edit change planning scan that flags overlapping content across your installed skills, ensuring your modifications and additions stay clean and maintainable.

How do I repackage an edited skill using the skill-creator directory and positional arguments?▼

Repackaging an edited skill involves running the skill-creator packaging script directly from its own directory with the correct positional arguments, then renaming the output .skill file back to the canonical skill name for proper installation.

Can I create a new skill from scratch using the skill-updater workflow?▼

No, this workflow applies only to editing, fixing, improving, or tweaking skills already present in the installed skills directory, not creating new skills from scratch.

Why does my skill packaging fail when I try to edit installation artifacts in place?▼

Editing installation artifacts in place fails because the installed skills directory operates as a read-only filesystem, requiring you to copy the target skill to a writable directory before applying any edits.

Do I need to propose specific additions and removals before making edits to an existing skill?▼

Yes, the workflow requires summarizing proposed additions, modifications, and suggested removals before editing, allowing you to verify the change plan and scan for duplication prior to modifying the copied files.