How do I install the Permission Manager skill?

Run npx skillmds@latest add sickn33/permission-manager in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Permission Manager safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Permission Manager?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Permission Manager free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Permission Manager?

sickn33 (@sickn33) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Permission Manager by sickn33 — Agent Skill

Name: Permission Manager
Rating: 4.666666666666667 (3 reviews)
Author: sickn33

File contents

What I do

Review and summarize currently always-allowed commands
Suggest safe read-only commands for auto-approval
Add or remove commands from the allow list in opencode.json
Configure skill-level permissions (allow/deny/ask) with wildcard patterns
Audit permission configs for security and usability

When to Use

Use this when optimizing opencode's permission settings, reviewing allowed commands, or configuring skill access controls.

Workflow Steps

Read current config: Load ~/.config/opencode/opencode.json or project-level opencode.json
Summarize permissions: Identify currently allowed commands and skill permissions
Suggest additions: Propose safe read-only commands for auto-allow (see recommended list below)
Apply changes: Edit the config to add/remove permission entries
Validate: Ensure JSON is valid after changes

Complements opencode's built-in allow/deny/ask permissions by auditing current config and recommending adjustments through conversation.

Key Rules

Never allow commands that modify files, commit, push, or change system state
Prefer exact command entries such as git status --short, git diff --stat, and ls -la
Avoid trailing wildcards such as git status* unless the expanded command family has been manually reviewed as read-only
Confirm with user before modifying permission config
Distinguish between bash command permissions and skill permissions
Keep config organized: group related commands together

Limitations

This skill is scoped to opencode permission configuration and should not modify other agent hosts' permission stores.
Treat all write-capable command permissions as high-risk; review them manually even when a pattern looks narrow.

How to trigger me

Use the Task tool with the permission-manager subagent type:

/permissions

Or in natural language, ask opencode to "manage opencode permissions" or "review allowed commands".

Source: sickn33/agentic-awesome-skills → skills/permission-manager/SKILL.md

Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/permission-manager/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/permission-manager/SKILL.md

---name: permission-managerdescription: Manage opencode permissions: review always-allow lists, suggest safe read-only commands, configure permission patterns--- ## What I do - Review and summarize currently always-allowed commands - Suggest safe read-only commands for auto-approval - Add or remove commands from the allow list in opencode.json - Configure skill-level permissions (allow/deny/ask) with wildcard patterns - Audit permission configs for security and usability ## When to Use Use this when optimizing opencode's permission settings, reviewing allowed commands, or configuring skill access controls. ## Workflow Steps 1. **Read current config**: Load `~/.config/opencode/opencode.json` or project-level `opencode.json` 2. **Summarize permissions**: Identify currently allowed commands and skill permissions 3. **Suggest additions**: Propose safe read-only commands for auto-allow (see recommended list below) 4. **Apply changes**: Edit the config to add/remove permission entries 5. **Validate**: Ensure JSON is valid after changes Complements opencode's built-in allow/deny/ask permissions by auditing current config and recommending adjustments through conversation. ## Key Rules - Never allow commands that modify files, commit, push, or change system state - Prefer exact command entries such as `git status --short`, `git diff --stat`, and `ls -la` - Avoid trailing wildcards such as `git status*` unless the expanded command family has been manually reviewed as read-only - Confirm with user before modifying permission config - Distinguish between bash command permissions and skill permissions - Keep config organized: group related commands together ## Limitations - This skill is scoped to opencode permission configuration and should not modify other agent hosts' permission stores. - Treat all write-capable command permissions as high-risk; review them manually even when a pattern looks narrow. ## How to trigger me Use the Task tool with the `permission-manager` subagent type: ``` /permissions ``` Or in natural language, ask opencode to "manage opencode permissions" or "review allowed commands". --- **Source:** [`sickn33/agentic-awesome-skills`](https://github.com/sickn33/agentic-awesome-skills) → `skills/permission-manager/SKILL.md` **Also appears in:** `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/permission-manager/SKILL.md`, `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/permission-manager/SKILL.md`

Frequently asked questions

Permission Manager