claude-skills-sync-init

Generate a deterministic Claude skill-sync script and update project configuration.

2|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Adonis0123/adonis-skills --skill claude-skills-sync-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-skills-sync-init
Source: https://github.com/Adonis0123/adonis-skills/tree/main/skills/claude-skills-sync-init
Command: npx skills add https://github.com/Adonis0123/adonis-skills --skill claude-skills-sync-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a bootstrap workflow to automate Claude skill-sync across repositories. It creates a deterministic synchronization script, injects package.json scripts and postinstall hooks, and ensures the target repo contains a .claude/skills directory.

Core Features & Use Cases

  • Generate scripts: scripts/sync-llm-skills.ts for seamless skill synchronization in Claude environments.
  • Inject and guard postinstall: automatically adds a ci-safe invocation to run the sync on install, while avoiding duplicates.
  • Atomic synchronization: copies new content to a temporary directory and atomically switches to .claude/skills to prevent partial updates; ensures .gitignore contains .claude/skills.
  • Use cases: when a team wants to bootstrap Claude skill-sync across multiple repos or set up a new project to host Claude skills.

Quick Start

Run the bootstrap script to initialize Claude skill-sync in your repository.

Frequently Asked Questions about claude-skills-sync-init

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

FAQPage Schema
How do I sync Claude skills from .agents/skills to .claude/skills automatically?

To sync Claude skills automatically, this bootstrap generates a deterministic synchronization script that moves skills from .agents/skills to .claude/skills and keeps them updated. It ensures CI-safe postinstall behavior by injecting guarded hooks into package.json.

What is atomic directory replacement for skill synchronization and why use it?

Atomic directory replacement for skill synchronization copies new content to a temporary directory before switching to .claude/skills. This mechanism prevents partial updates and ensures developers always access a complete, consistent set of Claude skills during automated sync.

How to set up a CI-safe postinstall hook for repository automation scripts?

To set up a CI-safe postinstall hook for repository automation, the bootstrap injects a guarded script invocation into package.json. It automatically bootstraps the is-ci dependency and avoids duplicate entries to ensure deterministic postinstall behavior across environments.

Does Claude skill-sync bootstrap work with an existing package.json configuration?

Claude skill-sync bootstrap works with an existing package.json by requiring it to be writable. It injects synchronization scripts and postinstall hooks while checking for duplicates to avoid overwriting your current repository configuration.

Why does my automated skill synchronization fail during partial directory updates?

Automated skill synchronization fails during partial updates if files are replaced directly without atomic switching. The bootstrap solves this by copying to a temporary directory first and atomically replacing the target to prevent corrupted states.

Do I need to update .gitignore when moving Claude skills to .claude/skills?

Yes, you need to update .gitignore when moving Claude skills to .claude/skills. The bootstrap automatically ensures .gitignore contains the .claude/skills directory entry to prevent committing synchronized files to your repository.