sync-plugin-skills

Copy approved Claude Code plugin skills into a repository with a sync manifest.

2|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill sync-plugin-skills-timgranlundmarsden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-plugin-skills
Source: https://github.com/timgranlundmarsden/claude-agent-flow/tree/main/skills/sync-plugin-skills
Command: npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill sync-plugin-skills-timgranlundmarsden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

This Skill makes installed Claude Code plugin skills available inside repository-based web workflows by copying approved skills from local plugin caches into the project.

Core Features & Use Cases

  • Selective Vendoring: Sync only the skills listed in skills-filter.yaml so teams control exactly what gets copied into the repo.
  • Cache Discovery and Validation: Locate plugins across multiple local cache roots, handle versioned plugin layouts, and skip invalid names or symlinks for safer syncing.
  • Audit-Friendly Output: Produce a manifest of synced skills and preserve open-source license files when available.
  • Use Case: Use this when you already have skills installed locally but need the same capabilities to work in Claude Code web sessions or shared repository environments.

Quick Start

Run the /sync-plugin-skills command from a local Claude Code session where the desired plugins are already installed.

Frequently Asked Questions about sync-plugin-skills

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

FAQPage Schema
How do I sync Claude Code plugin skills into a repository for web sessions?

To sync plugin skills into a repository, this tool copies approved skill folders from local plugin caches while validating names, rejecting symlinks, and recording a sync manifest for audit tracking. It selectively vendors only the skills listed in skills-filter.yaml so they work in web sessions.

What is the best way to vendor Claude Code skills selectively from local plugin caches?

The best way to vendor Claude Code skills selectively is by using a skills-filter.yaml configuration to control exactly which plugin folders get copied from local cache roots into your project. This approach skips invalid names and symlinks while preserving open-source license files.

Do I need jq installed to sync Claude Code plugin skills locally?

Yes, you need jq installed to sync Claude Code plugin skills locally. The synchronization process requires jq to parse and validate plugin metadata when discovering plugins across multiple local cache roots and versioned plugin layouts.

Can I use installed Claude Code skills in shared repository environments without manual copying?

Yes, you can use installed Claude Code skills in shared repository environments without manual copying by running the sync command from a local session. It automates cache discovery, validates skill names, copies approved folders, and generates an audit manifest for tracking.

Why does the skill sync process reject symlinks and invalid names from plugin caches?

The skill sync process rejects symlinks and invalid names from plugin caches to ensure safer syncing. By validating names and skipping symlinks during cache discovery, it prevents potentially unsafe or malformed skill directories from being vendored into your repository.

Does Claude Code plugin skill syncing preserve license files when copying to a repository?

Yes, Claude Code plugin skill syncing preserves open-source license files when available. During the selective vendoring process, the tool copies approved skill folders from local plugin caches while maintaining their associated license files for compliance.