ReddRadar
Agent skill
tools-permission-sync
Synchronize marketplace permissions - generate wildcards, manage executor permissions, and migrate to executor pattern.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/tools-permission-sync
SKILL.md
Marketplace Sync Skill
PURPOSE: Synchronize Claude Code permissions with marketplace bundles and manage the executor permission pattern.
Script Reference
| Script | Notation | Purpose |
|---|---|---|
| marketplace-sync | plan-marshall:tools-permission-sync:marketplace-sync |
Marketplace permission synchronization |
Operations
generate-wildcards - Generate Permission Wildcards
Generate Skill and SlashCommand wildcards from marketplace inventory.
# Read inventory from stdin
python3 .plan/execute-script.py pm-plugin-development:tools-marketplace-inventory:scan-marketplace-inventory \
--scope marketplace --resource-types skills,commands | \
python3 .plan/execute-script.py plan-marshall:tools-permission-sync:marketplace-sync generate-wildcards
# Or from file
python3 .plan/execute-script.py plan-marshall:tools-permission-sync:marketplace-sync generate-wildcards \
--input inventory.json
Output (JSON):
{
"statistics": {
"bundles_scanned": 8,
"skills_found": 28,
"commands_found": 39,
"wildcards_generated": 22
},
"permissions": {
"skill_wildcards": ["Skill(pm-dev-builder:*)", "Skill(pm-workflow:*)"],
"command_bundle_wildcards": ["SlashCommand(/pm-dev-builder:*)", "SlashCommand(/pm-workflow:*)"],
"command_shortform": ["SlashCommand(/java-create:*)"]
}
}
ensure-executor - Ensure Executor Permission
Ensure the executor permission exists in settings.
python3 .plan/execute-script.py plan-marshall:tools-permission-sync:marketplace-sync ensure-executor \
--target global \
--dry-run
Output (JSON):
{
"executor_permission": "Bash(python3 .plan/execute-script.py *)",
"settings_file": "/Users/name/.claude/settings.json",
"action": "added",
"success": true
}
cleanup-scripts - Remove Redundant Script Permissions
Remove individual script path permissions (redundant with executor pattern).
python3 .plan/execute-script.py plan-marshall:tools-permission-sync:marketplace-sync cleanup-scripts \
--target global \
--remove-broad-python \
--dry-run
Output (JSON):
{
"individual_script_permissions": ["Bash(python3 /path/to/scripts/foo.py:*)"],
"individual_count": 5,
"broad_python_found": true,
"broad_python_removed": true,
"action": "would_remove",
"total_would_remove": 6
}
migrate-executor - Full Migration to Executor Pattern
Complete migration: add executor permission + cleanup redundant permissions.
python3 .plan/execute-script.py plan-marshall:tools-permission-sync:marketplace-sync migrate-executor \
--target global \
--remove-broad-python \
--dry-run
Output (JSON):
{
"success": true,
"dry_run": true,
"executor": {
"permission": "Bash(python3 .plan/execute-script.py *)",
"action": "added"
},
"cleanup": {
"individual_removed": 5,
"broad_python_removed": true
},
"summary": "Migrated to executor-only pattern: 1 permission replaces 5 individual script permissions"
}
Executor Permission Pattern
The executor pattern uses a single permission for all marketplace scripts:
Bash(python3 .plan/execute-script.py *)
This replaces individual script path permissions because the executor invokes scripts via subprocess (not checked by Claude Code permissions).
Benefits
- Single permission instead of N permissions (one per script)
- Automatic coverage for new scripts when executor is regenerated
- No permission prompts when adding new skills/commands
Migration Path
- Run
ensure-executorto add the executor permission - Run
cleanup-scriptsto remove redundant individual permissions - Or run
migrate-executorto do both in one step
Target Selection
| Target | File |
|---|---|
global |
~/.claude/settings.json |
project |
.claude/settings.json or .claude/settings.local.json |
Integration with Plan Marshall
The plan-marshall skill uses this during setup:
- Step 2: Generate Executor - Creates
.plan/execute-script.py - Ensure Executor Permission - Adds
Bash(python3 .plan/execute-script.py *)to global settings
python3 .plan/execute-script.py plan-marshall:tools-permission-sync:marketplace-sync ensure-executor \
--target global
Error Handling
All operations return JSON with error details:
{
"error": "Settings file not found: /path/to/settings.json",
"success": false
}
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?