agentsclimarketplace
Sign in

Setup

Skill injaeryou/claude-permissions/skills/setup

Generate or update .claude/settings.json permission rules by detecting the project's stack and fetching matching modules from claude-permissions.injaeryou.dev. Use when the user asks to set up Claude Code permissions, reduce permission prompts, or generate a permissions allowlist.From its SKILL.md

Install
npx -y skills add injaeryou/claude-permissions --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

claude-permissions setup

Generate .claude/settings.json from curated permission modules at https://claude-permissions.injaeryou.dev — like gitignore.io, but for Claude Code permissions. Modules follow one policy: allow read-only, ask mutating/outbound, deny destructive or secret-leaking. Deny always wins over allow, so stacking modules never weakens a deny.

Steps

  1. Fetch the module list (names, categories, descriptions):

    curl -s https://claude-permissions.injaeryou.dev/api/list

  2. Detect the project's stack and map it to module names from that list. Typical signals:

    • always: bash, filesystem, web; host OS → macos or linux
    • .git/ → git; GitHub remote or gh usage → gh
    • package.json → node, npm
    • Cargo.toml → cargo · go.mod → go · pyproject.toml / requirements.txt → python
    • Dockerfile / compose.yaml → docker · k8s manifests → kubectl
    • Brewfile or macOS tooling → brew

    Only use names that exist in the list. Show the chosen modules to the user and confirm before writing.

  3. Fetch the merged settings for the confirmed selection:

    curl -s https://claude-permissions.injaeryou.dev/git,npm,bash

  4. Before writing anything, check whether the target file already exists (.claude/settings.json in the project root, .claude/settings.local.json if the user wants personal rules that stay out of version control — e.g. in a shared repo — or ~/.claude/settings.json if the user wants it globally). Never overwrite an existing file blindly:

    • No existing file → save the response as-is.
    • Existing file → read it first, then merge only permissions.allow / ask / deny as a union: keep every existing rule, add the new ones, drop duplicates. Every other top-level key (hooks, env, model, …) and any rules the user wrote by hand stay exactly as they were. If an existing rule conflicts with a fetched one (e.g. same command in both allow and deny), keep both and point it out — deny wins at runtime, so nothing silently loosens.

  5. Tell the user which modules went in and link the selection, e.g. https://claude-permissions.injaeryou.dev/git,npm,bash — the same URL shows the selection in a browser and returns the JSON over curl.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.