Tutorials
    claude code
    skill.md
    updates

    How to Update Claude Code Skills: Keep Skills Current

    Update your SKILL.md skills in Claude Code, marketplace updates, GitHub pulls, and version management.

    May 3, 20263 min read
    Share:

    Skills improve over time. Creators fix bugs, add features, and update instructions based on feedback. Here's how to keep your skills current.

    Quick Answer: Connect your MCP-compatible agent to Agensi, choose a skill and ask the agent to use it on your task. Approve any required purchase. The latest approved instructions load through get_skill on each use. Never write any part of the skill to disk; your licence does not allow you to save, copy or export it.

    Marketplace skills (Agensi)

    Connect your MCP-compatible agent to Agensi, choose a skill and ask the agent to use it on your task. Approve any required purchase. The latest approved instructions load through get_skill on each use. Never write any part of the skill to disk; your licence does not allow you to save, copy or export it.

    rm -rf ~/.claude/skills/skill-name/
    unzip skill-name-v2.zip -d ~/.claude/skills/
    

    Start a new Claude Code session to pick up the changes.

    GitHub skills

    If you cloned a skill from GitHub, pull the latest:

    cd ~/.claude/skills/skill-name/
    git pull
    

    That's it. The next Claude Code session uses the updated version.

    Manual skills

    If you created a skill yourself or pasted it from a community share, you update it by editing the SKILL.md file directly. Use any text editor.

    After editing, start a new Claude Code session. Claude Code reads skills at startup, changes mid-session aren't picked up.

    Version management

    SKILL.md doesn't have a built-in versioning system. If you want to track versions:

    • Keep the old version in a backup folder before updating
    • Add a version comment at the top of the SKILL.md body: *Version 2.1, April 2026*
    • For GitHub skills, check the commit history to see what changed

    When to update

    Update skills when:

    • The creator announces bug fixes or improvements
    • You notice the skill's output quality declining (might be due to model updates)
    • You changed your project's stack and the skill needs to match (e.g., switched from Jest to Vitest)
    • The skill references outdated practices or deprecated APIs

    Don't update for the sake of updating. If a skill works well, leave it alone.


    Find skills with active creators on Agensi.

    Frequently Asked Questions

    To update Agensi marketplace skills, download the new ZIP file from your purchase history and replace the old skill files by first removing the old directory and then unzipping the new version into '~/.claude/skills/'.

    For GitHub skills, navigate to the skill's directory within '~/.claude/skills/' and execute 'git pull' to fetch the latest changes.

    Manually created or community-shared skills are updated by directly editing their SKILL.md file with any text editor.

    Always start a new Claude Code session after updating skills for the changes to take effect, as Claude Code reads skills only at startup.

    SKILL.md does not have a built-in versioning system; however, you can add a version comment at the top of the SKILL.md body or check commit history for GitHub skills to track changes.

    Update skills when creators announce bug fixes, if output quality declines, when your project's stack changes, or if the skill references outdated practices or deprecated APIs.