claude-permissions-optimizer

Analyze Claude Code session history and apply safe Bash commands to settings.json.

6|Updated Jan 29, 2023
One-click install
npx skills add https://github.com/rethinkhealth/glion --skill claude-permissions-optimizer-rethinkhealth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-permissions-optimizer
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/claude-permissions-optimizer
Command: npx skills add https://github.com/rethinkhealth/glion --skill claude-permissions-optimizer-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ./normalize.mjs, and includes scripts (resource) components.

What problem does it solve?

Claude Code users suffer frequent permission prompts during scripting; this skill reduces prompts by identifying safe Bash commands from session history and auto-applying them to the settings.

Core Features & Use Cases

  • Analyze session history to find commands safe to auto-allow.
  • Update settings.json to streamline permissions while preserving safety.
  • Use cases: when experiences of permission fatigue; for teams to standardize safe Bash commands.

Quick Start

Run the Claude permissions optimizer to scan your Claude Code session history and auto-apply safe Bash commands to the settings.json file.

Frequently Asked Questions about claude-permissions-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce permission prompts in Claude Code by auto-allowing safe Bash commands?

To reduce Claude Code permission prompts, you can analyze your session history to identify safe Bash commands and automatically apply them to settings.json. This filters out dangerous commands while streamlining auto-permissions for frequent tasks.

Can I update Claude Code settings.json permissions across multiple projects at once?

Yes, you can update Claude Code settings.json permissions across all projects or a specified subset. The tool reads existing settings and applies a filtered, safe set of permission rules to streamline your workflow.

How does analyzing Claude Code session history identify safe commands for auto-permissions?

Analyzing Claude Code session history identifies safe commands by reading your transcripts and evaluating past Bash commands. It outputs a filtered set of safe permission rules while applying guardrails to avoid dangerous commands.

What guardrails are in place to prevent dangerous Bash commands from being auto-applied in Claude Code?

Guardrails prevent dangerous Bash commands by filtering your session history transcripts before auto-application. The tool outputs only a safe set of permission rules to settings.json, avoiding commands that could cause harm.

Does the Claude permissions optimizer work for teams wanting to standardize safe Bash commands?

Yes, the Claude permissions optimizer works for teams to standardize safe Bash commands. It analyzes session history and outputs a filtered set of permission rules that can be applied to settings.json across all projects.