sync-skills

Synchronize devkit skill definitions across Claude Code, Codex, and Cursor.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Levezze/devkit --skill sync-skills-levezze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-skills
Source: https://github.com/Levezze/devkit/tree/main/skills/sync-skills
Command: npx skills add https://github.com/Levezze/devkit --skill sync-skills-levezze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It fixes broken or out-of-date devkit skill links and Codex skill metadata drift so Claude Code, Codex, and Cursor stay aligned with the same shared skill definitions.

Core Features & Use Cases

  • Cross-tool skill synchronization: Repairs small symlink issues and regenerates Codex metadata from each skill’s SKILL.md frontmatter.
  • Safety-first gap reporting: Detects larger gaps (missing managed skills, invalid frontmatter, non-symlink user modifications) and stops to request explicit user decisions.
  • Selective environment repair: Limits fixes to specific targets (Claude, Codex, Cursor) to match what the user wants to update.

Quick Start

Run the sync-skills skill to check and automatically repair safe symlink and metadata issues across Claude Code, Codex, and Cursor.

Frequently Asked Questions about sync-skills

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

FAQPage Schema
How do I fix symlink drift for shared skills across Claude Code, Codex, and Cursor?

20-50 words in English, based on metadata facts only

What causes metadata drift in Codex skills when using multiple AI editors?

Metadata drift in Codex skills occurs when installed skill state diverges from the devkit repo, often due to partial syncs across environments or broken symlinks. Synchronization regenerates Codex metadata directly from each skill's SKILL.md frontmatter to resolve inconsistencies.

Can I synchronize devkit skills for only one specific AI editor?

Yes, you can limit skill synchronization repairs to specific targets like Claude Code, Codex, or Cursor. This selective environment repair allows you to update only the AI editor you want to modify without affecting other installed environments.

How do I safely synchronize skills without losing manual modifications?

To safely synchronize skills without losing manual modifications, the process detects non-symlink user changes and stops to request explicit user approval. You can run the sync script in dry-run mode to preview gaps before applying any non-symlink modifications.

Does synchronizing AI editor skills run smoke tests after modifications?

Yes, the skill synchronization process can optionally execute repository smoke tests after modifications are applied. This ensures that the repaired symlinks and regenerated Codex metadata do not break existing devkit functionality.