sync-skills

Audit and bridge skill parity between Claude skills and GitHub Copilot prompts.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill sync-skills-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-skills
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/sync-skills
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill sync-skills-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using both Claude and GitHub Copilot often end up with capabilities available in one tool but missing in the other, forcing users to remember which tool supports which workflow. This Skill audits both toolsets and creates bridging files so every capability is invocable from either platform. ## Core Features & Use Cases - Parity Audit: Lists all Claude skills, Copilot agents, and Copilot prompts, then identifies capabilities present in one tool but absent from the other. - Bridging File Generation: Creates thin wrapper files that delegate to the canonical agent definition, keeping both tools in sync without duplicating logic. - Near-Match Detection: Flags same-concept capabilities with different names for human review instead of auto-bridging them. - Use Case: After adding a new Claude skill for code review, run the sync to generate the matching Copilot prompt so Copilot users can invoke the same workflow. ## Quick Start Ask the assistant to sync skills and report any missing prompts between Claude and Copilot.

Frequently Asked Questions about sync-skills

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

FAQPage Schema
How do I sync Claude skills with GitHub Copilot prompts?▼

Invoke the sync-skills workflow, which scans .claude/skills, .github/agents, and .github/prompts, identifies gaps, and creates bridging files that delegate to the canonical agent definition so both tools can invoke every capability.

What is a bridging file for AI agent parity?▼

A bridging file is a thin wrapper created in one tool's directory that delegates to the canonical definition shared by both tools. It lets Claude and Copilot invoke the same capability without duplicating the underlying logic.

Can I only report skill gaps without creating files?▼

Yes, pass the 'report' argument to only report gaps without writing anything. You can also use 'copilot-only' to create only Copilot prompts or 'claude-only' to create only Claude skills.

Does the sync handle skills with similar but different names?▼

Near-matches, meaning the same concept under different names, are flagged for human review rather than auto-bridged. This prevents incorrect merges when naming conventions differ between the two toolsets.

Where is the sync logic defined for Claude and Copilot?▼

The single source of truth is .github/agents/sync-skills.agent.md, which is shared with GitHub Copilot. The Claude skill reads that file and executes its workflow rather than duplicating the instructions.