skill-transfer

To compare skills across agent repositories, scan directories like .claude/skills, .gemini/skills, .agents/skills, and .github/skills. The process uses file hashing and SKILL.md frontmatter extraction to classify conflicts and generate a concise report of synced, new, and conflicting skills.

Auditing skill inventory mismatches involves applying directory hashing and content comparison across .claude/skills and .gemini/skills folders. This detects version differences and classifies conflicts, returning a compact summary of what can be synced automatically versus what needs manual review.

No, skill syncing across agent repositories does not modify your original files. The process performs a read-only audit that applies directory hashing and conflict classification to generate a concise, decision-focused report without altering any skill content or directory structures.

To identify transferable skill updates before copying files, compare your chosen skill directories to detect content mismatches via hashing. The resulting audit report highlights new skills and version differences, showing exactly what should be propagated elsewhere.

You should manually resolve conflicts during cross-repo skill consolidation when the audit report identifies true content mismatches where versions differ. The report distinguishes between synced skills that can transfer automatically and conflicts that still require your manual choice.