update-skills

Synchronize installed skill files with the latest upstream repository version.

5|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/garethrhughes/fragile --skill update-skills-garethrhughes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/garethrhughes/fragile/tree/main/.opencode/skills/update-skills
Command: npx skills add https://github.com/garethrhughes/fragile --skill update-skills-garethrhughes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps a skills repository current by pulling the latest upstream version and reporting exactly what changed, so you do not have to inspect or merge updates manually.

Core Features & Use Cases

  • Repository Sync: Updates installed skill files from the upstream source using the bundled update workflow.
  • Change Reporting: Summarizes added, modified, and removed skills along with meaningful file-level changes.
  • Operational Safety: Preserves local project context where applicable and warns about rule file conflicts.
  • Use Case: Use it when a shared skills installation needs to be refreshed across workstations or project environments.

Quick Start

Run the update-skills skill to sync the latest upstream changes and return a concise report of what changed.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I sync a shared skills repository with the latest upstream version?

Synchronizing a skills repository involves executing a bundled update workflow that pulls the latest upstream version and returns a detailed change report. This eliminates manual inspection and merging of updated skill files.

What happens to my local project context when I refresh skill files?

Refreshing skill files preserves your local project context where applicable during the upstream synchronization process. The update workflow also specifically warns you about any potential rule file conflicts.

Can I track what changed in my skills directory after an upstream update?

You can track changes because the skill synchronization workflow generates a concise change report. This report summarizes added, modified, and removed skills along with meaningful file-level changes across root files, scripts, rules, and profiles.

Do I need Bash to run a skills repository updater?

Yes, you need Bash execution capability to run the bundled update workflow for synchronizing installed skill files. This requirement ensures the updater can properly pull upstream changes and generate the change report.

What is the best way to update installed skills across multiple workstations?

The best way to update installed skills across workstations is using an automated synchronization workflow that pulls upstream changes while preserving local project context. It safely refreshes shared installations and warns about rule file conflicts.

Why does my skills repository update warn about rule file conflicts?

Your skills repository update warns about rule file conflicts to prevent overwriting critical local configurations during the upstream sync. This operational safety measure ensures local project context is preserved while applying updates.