Agent skill

Sync Permissions

by flonat in flonat/flonat-research

Reconcile the current project's Claude and Codex permission surfaces with the canonical global policy.

MITAuto-check passed

Install Sync Permissions

skills CLI
$ npx skills add flonat/flonat-research --skill sync-permissions -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install flonat/flonat-research sync-permissions --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sync-permissions .claude/skills/sync-permissions && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sync-permissions
GitHub stars
145
Token cost
~1.1k tokens
SKILL.md length
410 words
Files
1
Skills in repo
83
Repo updated
First seen
Licence
MIT

At a glance

Reconcile the current project's Claude and Codex permission surfaces with the canonical global policy.

  • Works in 6 steps: Read Both Permission Files → Compute the Union → Write the Merged Result → …
  • Project permissions are missing
  • SKILL.md covers Purpose, When to Use, What It Does and What It Does NOT Do, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sync Permissions is an agent skill from flonat/flonat-research. Reconcile the current project's Claude and Codex permission surfaces with the canonical global policy. Use when project permissions are missing, stale, or inconsistent after setup or migration. Not for syncing skills, hooks, or agents; use $sync-ai-infra.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

  • Project permissions are missing
  • Inconsistent after setup

Example prompts

  • “/sync-permissions”

Requirements

  • Pre-approved tools (allowed-tools): Bash(jq*), Bash(ls*), Bash(test*), Bash(readlink*), Read, Write, Edit

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Read Both Permission Files
  2. Compute the Union
  3. Write the Merged Result
  4. Verify Skills Directory
  5. Verify Agents Directory
  6. Report

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(jq*)
    • Bash(ls*)
    • Bash(test*)
    • Bash(readlink*)
    • Read
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sync Permissions loads about 1.1k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 410 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 410 words, ~1,062 tokens.

Download SKILL.mdSave it as .claude/skills/sync-permissions/SKILL.md (or your agent's skills folder).
name
sync-permissions
description
Reconcile the current project's Claude and Codex permission surfaces with the canonical global policy. Use when project permissions are missing, stale, or inconsistent after setup or migration. Not for syncing skills, hooks, or agents; use $sync-ai-infra.
allowed-tools
Bash(jq*), Bash(ls*), Bash(test*), Bash(readlink*), Read, Write, Edit
argument-hint
(no arguments)

Update Rules Skill

Sync global permissions, skills, and agents into the current project without losing project-specific settings.

Purpose

The SessionStart hook only copies permissions when .claude/settings.local.json doesn't exist yet. After that, new global permissions never propagate to existing projects. This skill fills that gap — run it anytime to pull in new permissions additively.

When to Use

  • After adding new permissions to ~/.claude/settings.json
  • When starting work in a project that hasn't been updated in a while
  • After creating a new skill and wanting it available everywhere
  • When the user says "sync permissions", "update rules", "update my permissions"

What It Does

  1. Merge permissions — adds global permissions into project-local, keeping any project-specific ones
  2. Verify skills directory — ensures <skills-root>/ exists and has content
  3. Verify agents directory — ensures ~/.claude/agents/ exists and has content
  4. Report changes — shows exactly what was added

What It Does NOT Do

  • Never removes existing project permissions (additive only)
  • Never modifies ~/.claude/settings.json (reads it, never writes)
  • Never touches model, hooks, or other global settings keys

Workflow

Step 1: Read Both Permission Files

Read these two files:

  • Global: ~/.claude/settings.json → extract permissions.allow array
  • Local: .claude/settings.local.json → extract permissions.allow array

If the local file doesn't exist, create it with global permissions (same as the SessionStart hook).

Step 2: Compute the Union

Merge the two permission arrays:

  • Start with all existing local permissions (preserve everything)
  • Add any global permissions not already present in local
  • Sort the final array for readability

The merge logic:

new_permissions = local_permissions ∪ global_permissions
added = new_permissions - local_permissions
Show full SKILL.md (170 more words)Show less
Step 3: Write the Merged Result

If there are new permissions to add:

  1. Read the full local settings file (preserve any non-permissions keys)
  2. Replace permissions.allow with the merged array
  3. Write back to .claude/settings.local.json

If no new permissions, skip the write.

Step 4: Verify Skills Directory

Check that <skills-root>/ exists and has content:

  • If missing or empty, warn: "Skills directory missing — run the documented managed-copy installer or deployment command"
  • If present, report file count
Step 5: Verify Agents Directory

Check that ~/.claude/agents/ exists and has content:

  • If missing or empty, warn: "Agents directory missing — run the documented managed-copy installer or deployment command"
  • If present, report file count
Step 6: Report

Output a summary:

Permissions sync complete:
- Global permissions: [N]
- Local permissions (before): [N]
- New permissions added: [N] — [list them]
- Local permissions (after): [N]
- Skills directory: ✓ [N] files / ✗ missing
- Agents directory: ✓ [N] files / ✗ missing

If nothing changed:

Everything up to date. No new permissions to add. Skills OK. Agents OK.

Example

Running sync-permissions after adding web fetch and Skill(literature) to ~/.claude/settings.json:

Permissions sync complete:
- Global permissions: 25
- Local permissions (before): 64
- New permissions added: 2 — web fetch, Skill(literature)
- Local permissions (after): 66
- Skills directory: ✓ 496 files
- Agents directory: ✓ 16 files

Safety

  • Additive only — the skill can only add permissions, never remove them
  • No global writes — global settings are read-only
  • Directory check — verifies skills/agents directories exist and have content
  • Idempotent — safe to run multiple times; re-running with no changes produces no writes

© flonat, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/sync-permissions of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Sync Permissions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sync Permissions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sync Permissions this skillflonat/flonat-research145—~1.1kAutomated safety check: PassMIT
React Syncvercel/next.js143k—~486Automated safety check: PassMIT
Permission Managersickn33/agentic-awesome-skills47k1 repos~595Automated safety check: PassMIT
Claude-Mem Cloud Syncthedotmack/claude-mem98k1 repos~1kAutomated safety check: NotesApache-2.0
Agent Sync Coordinatorruvnet/ruflo74k2 repos~4kAutomated safety check: PassMIT
Workspace Surface Auditaffaan-m/ECC275k3 repos~1.3kAutomated safety check: NotesMIT

Similar skills

  • React Sync

    vercel/next.js

    Official

    Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration.

    143k GitHub stars~486 tokensUpdated today
    Auto-check passed
  • Permission Manager

    sickn33/agentic-awesome-skills

    Manage opencode permissions: review always-allow lists, suggest safe read-only commands, configure permission patterns

    47k GitHub starsUsed in 1 repo~595 tokens
    DevelopmentAuto-check passed
  • Claude-Mem Cloud Sync

    thedotmack/claude-mem

    Checks claude-mem cloud sync status and guides you through connecting a cmem.ai Pro account without the sync token ever passing through the chat.

    98k GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check: notes
  • Agent skill for sync-coordinator - invoke with $agent-sync-coordinator

    74k GitHub starsUsed in 2 repos~4k tokens
    Auto-check passed
  • Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows.

    275k GitHub starsUsed in 3 repos~1.3k tokens
    Agent WorkflowsAuto-check: notes
  • Fix Sync

    ClickHouse/ClickHouse

    Fix the "CH Inc sync" job in a pull request. An agent skill from ClickHouse/ClickHouse.

    50k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo
  • Latex Posters

    flonat/flonat-research

    Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.

    145 GitHub stars~1.5k tokensUpdated 9 days ago
    Auto-check: notes
  • Skill Creator

    flonat/flonat-research

    Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.

    145 GitHub stars~4.4k tokensUpdated 9 days ago
    Auto-check passed
  • DOCX

    flonat/flonat-research

    Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.

    145 GitHub stars~1.2k tokensUpdated 9 days ago
    Auto-check passed
  • PDF

    flonat/flonat-research

    Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.

    145 GitHub stars~488 tokensUpdated 9 days ago
    Auto-check passed
  • Init Project Orchestration

    flonat/flonat-research

    Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.

    145 GitHub stars~1.6k tokensUpdated 9 days ago
    Auto-check passed
  • Pre Commit Audit

    flonat/flonat-research

    Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.

    145 GitHub stars~2.8k tokensUpdated 9 days ago
    Auto-check: notes

Questions about Sync Permissions

What does Sync Permissions do?

Reconcile the current project's Claude and Codex permission surfaces with the canonical global policy. Sync Permissions is an agent skill from flonat/flonat-research. Reconcile the current project's Claude and Codex permission surfaces with the canonical global policy.

When should I use Sync Permissions?

Sync Permissions fits situations like: project permissions are missing; inconsistent after setup.

How do I install Sync Permissions in Claude Code?

Run `npx skills add flonat/flonat-research --skill sync-permissions -a claude-code`. Or copy the skill folder (skills/sync-permissions in flonat/flonat-research) into .claude/skills/sync-permissions in your project. Claude Code loads it when a task matches its description.

How do I install Sync Permissions in Codex?

Run `npx skills add flonat/flonat-research --skill sync-permissions -a codex`. Or copy the skill folder (skills/sync-permissions in flonat/flonat-research) into .agents/skills/sync-permissions in your project. Codex loads it when a task matches its description.

Can I use Sync Permissions in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill sync-permissions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-permissions, .gemini/skills/sync-permissions, .github/skills/sync-permissions and .opencode/skills/sync-permissions in your project.

What does Sync Permissions need to run?

SKILL.md names no scripts, command-line tools or credentials: Sync Permissions is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(jq*), Bash(ls*), Bash(test*), Bash(readlink*), Read, Write, Edit.

Does Sync Permissions access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sync Permissions safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sync Permissions use?

Sync Permissions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sync Permissions use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sync Permissions?

Skills that share tags, products or a category with Sync Permissions: React Sync (vercel/next.js, 143k stars), Permission Manager (sickn33/agentic-awesome-skills, 47k stars), Claude-Mem Cloud Sync (thedotmack/claude-mem, 98k stars) and Agent Sync Coordinator (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sync Permissions?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.