update-skills

Re-apply upstream changes to installed channel and provider skills.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Bartunek/nanoclaw --skill update-skills-bartunek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/Bartunek/nanoclaw/tree/main/.claude/skills/update-skills
Command: npx skills add https://github.com/Bartunek/nanoclaw --skill update-skills-bartunek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams keep Claude's channel and provider skills up to date by re-applying their latest code from upstream, ensuring local customizations remain intact.

Core Features & Use Cases

  • Preflight checks for a clean working tree and the upstream remote.
  • Detects installed channel/provider skills and lists them for re-application.
  • Re-applies selected skills by invoking their own apply steps, overwriting copied-in code while preserving credentials and wiring.
  • Validation via build and test to ensure integration after updates.
  • Generates a summary of the new HEAD and updated skills for quick verification.

Quick Start

Run the update-skills command in Claude Code to re-apply all installed skills.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I refresh installed skills from upstream without losing local credentials and wiring?

Re-applying skills from upstream overwrites only the copied-in code while preserving local credentials and wiring. This skill automates that process by detecting installed channel and provider skills and selectively re-applying their latest upstream changes.

What prerequisites are needed to update channel skills from upstream in a local workspace?

Updating channel skills requires a clean working tree, a configured origin remote for channels and providers, and the ability to fetch upstream branches. You also need the environment to run validation builds and tests after the update.

Can I selectively re-apply specific provider skills instead of updating all of them at once?

Yes, selective re-application is supported. The skill detects which channel and provider skills are wired in your workspace and lists them, allowing you to choose specific skills to re-apply rather than updating everything simultaneously.

How does updating skills from upstream ensure my local customizations remain intact?

The update process invokes each skill's own apply steps to overwrite copied-in code while explicitly preserving local credentials and wiring. This separation ensures customizations survive the upstream refresh.

What happens after upstream skill changes are applied to my local workspace?

After re-applying upstream changes, the skill runs validation builds and tests to ensure integration. It then generates a summary of the new HEAD and updated skills so you can quickly verify the update succeeded.

Why do I need a clean working tree before re-applying skills from upstream?

A clean working tree is required because re-applying upstream changes overwrites copied-in code. Uncommitted local changes could conflict with the incoming upstream code, making it difficult to preserve credentials and wiring during the update.