sync-permissions

Merge Claude and Gemini permission settings into repository-wide configurations.

3|1|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/JacobPEvans/claude-code-plugins --skill sync-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-permissions
Source: https://github.com/JacobPEvans/claude-code-plugins/tree/main/config-management/skills/sync-permissions
Command: npx skills add https://github.com/JacobPEvans/claude-code-plugins --skill sync-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of AI tool permissions by consolidating local settings into a unified, repository-wide configuration, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Cross-Tool Synchronization: Merges permission settings from Claude and Gemini into a consistent format.
  • Intelligent Merging: Prioritizes Claude's classification when conflicts arise and preserves Gemini-specific permissions.
  • Use Case: Ensure that all AI collaborators adhere to the same security and access policies by automatically syncing their individual permission configurations to a central standard.

Quick Start

Use the sync-permissions skill to merge local AI permission settings into repository-wide permissions.

Frequently Asked Questions about sync-permissions

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

FAQPage Schema
How do I synchronize AI permissions across Claude and Gemini?

To synchronize AI permissions across Claude and Gemini, this skill scans local JSON and MD files to merge approved changes into a unified repository-wide configuration. It consolidates local settings to ensure consistency and reduce manual effort.

How does merging configuration conflicts work between Claude and Gemini?

When merging configuration conflicts between Claude and Gemini, the skill prioritizes Claude's classification while preserving Gemini-specific permissions. This intelligent merging ensures a consistent security policy without losing unique tool settings.

What's the best way to consolidate local AI tool settings into a repository-wide configuration?

The best way to consolidate local AI tool settings into a repository-wide configuration is to use a synchronization skill that analyzes local JSON and MD files. It merges approved changes to ensure all AI collaborators adhere to standard access policies.

Do I need specific file formats to sync AI permission settings for a repository?

Yes, syncing AI permission settings requires scanning local JSON and MD files for permission data. The skill extracts configurations from these specific formats to build a unified repository-wide standard.

Why should I standardize AI security permissions across multiple tools?

You should standardize AI security permissions across multiple tools to ensure all AI collaborators adhere to the same access policies. Synchronizing settings prevents configuration drift and reduces the manual effort of updating individual tool rules.