update-skills

Synchronize SKILL.md files from .ai/skills to .claude/skills and .github/skills.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/I-Synergy/AI --skill update-skills-i-synergy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/I-Synergy/AI/tree/main/.claude/skills/update-skills
Command: npx skills add https://github.com/I-Synergy/AI --skill update-skills-i-synergy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps skill definitions in a single source of truth and synchronizes them across all target repositories to ensure consistency and reduce drift.

Core Features & Use Cases

  • Single source of truth for skill metadata in .ai/skills and automatic propagation to .claude/skills and .github/skills.
  • Automated synchronization to prevent manual drift when skills are added, updated, or removed.
  • Auditable updates by maintaining a clear trail of changes across targets.

Quick Start

Run after updating the skill in .ai/skills to propagate the changes to .claude/skills and .github/skills.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I sync skill definitions across multiple directories in Claude Code?

To sync skill definitions across directories, this Skill propagates SKILL.md files from the .ai/skills source of truth to .claude/skills and .github/skills targets. It performs deterministic synchronization to maintain consistency and reduce manual drift.

What is the best way to prevent configuration drift when updating Claude Code skills?

The best way to prevent drift is maintaining a single source of truth in .ai/skills and running automated synchronization to propagate updates to .claude/skills and .github/skills. This keeps all target directories consistent.

Does the skill synchronization process preserve directory structure and frontmatter?

Yes, the synchronization process preserves directory structure and synchronizes SKILL.md frontmatter and content. It validates target paths to ensure deterministic file synchronization across .claude/skills and .github/skills.

When do I need to run skill synchronization for my DevOps workflow?

You need to run skill synchronization whenever skills are added, edited, or removed in the .ai/skills directory. This propagates changes across .claude/skills and .github/skills to maintain consistency in your DevOps automation workflow.

Can I use git to track changes after synchronizing skills across targets?

Yes, you can use git to track changes after synchronization because the process provides auditable updates by maintaining a clear trail of changes across targets. This enables version control of all skill definitions propagated from the source.