Menü
Use when you need to sync global permissions into the current project.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | sync-permissions |
| description | Use when you need to sync global permissions into the current project. |
| allowed-tools | Bash(jq*), Bash(ls*), Bash(test*), Bash(readlink*), Read, Write, Edit |
| argument-hint | (no arguments) |
Sync global permissions, skills, and agents into the current project without losing project-specific settings.
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.
~/.claude/settings.json~/.claude/skills/ exists and has content~/.claude/agents/ exists and has content~/.claude/settings.json (reads it, never writes)model, hooks, or other global settings keysRead these two files:
~/.claude/settings.json → extract permissions.allow array.claude/settings.local.json → extract permissions.allow arrayIf the local file doesn't exist, create it with global permissions (same as the SessionStart hook).
Merge the two permission arrays:
The merge logic:
new_permissions = local_permissions ∪ global_permissions
added = new_permissions - local_permissions
If there are new permissions to add:
permissions.allow with the merged array.claude/settings.local.jsonIf no new permissions, skip the write.
Check that ~/.claude/skills/ exists and has content:
sync-to-claude-home.sh to populate"Check that ~/.claude/agents/ exists and has content:
sync-to-claude-home.sh to populate"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.
Running /sync-permissions after adding WebFetch and Skill(literature) to ~/.claude/settings.json:
Permissions sync complete:
- Global permissions: 25
- Local permissions (before): 64
- New permissions added: 2 — WebFetch, Skill(literature)
- Local permissions (after): 66
- Skills directory: ✓ 496 files
- Agents directory: ✓ 16 files
Use when you need to audit a research project against the init-project-research template.
Use when you need to validate a paper's bibliography — cross-references \cite{} keys against .bib files or embedded \bibitem entries, finds missing/unused/typo'd keys, and checks every key against the Paperpile library via the local resolver. Deep verification mode spawns parallel agents for DOI/metadata validation at scale. Fix mode rekeys drifted keys to canonical and stages missing entries for Paperpile.
Use when you need to bootstrap a full research project with directory scaffold and Overleaf symlink.
Use when you need to create a preprint / working-paper variant of a paper currently in conference or journal format. Forks the existing Overleaf project — adds a `preprint/` subfolder using the user's `your-template` Template, ports the body content from the source paper. The preprint is accessed locally via the existing `paper-{venue}/paper/preprint/` path (subfolder under the conference paper's symlink); no separate `paper-wp/` directory. Trigger on "set up a working paper", "create a preprint", "WP version", "arXiv-ready version", "ready to preprint". Never creates a new top-level Overleaf project — always nests inside the existing one. Never uses the conference's own style (.sty / .cls); always swaps to `your-template`.
Use when you need academic proofreading of a LaTeX paper (11 check categories).
Use when you need to assemble, anonymize, or audit a replication package.