suggest-permissions

Parse Claude Code session JSONL histories to generate .claude/settings.json permission blocks.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill suggest-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suggest-permissions
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/sessionkit/skills/suggest-permissions
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill suggest-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze Claude Code session history to identify permissions you repeatedly approved, helping you streamline settings and reduce future prompts.

Core Features & Use Cases

  • Automates detection of frequently approved operations across Bash commands, file edits, and MCP tools.
  • Generates actionable additions to .claude/settings.json to minimize prompts.
  • Use Case: When you regularly approve similar permissions across sessions, this skill suggests a minimal, safe permissions set for the project.

Quick Start

Run /suggest-permissions to analyze your recent session history and generate permission suggestions.

Frequently Asked Questions about suggest-permissions

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

FAQPage Schema
How do I reduce repeated permission prompts in Claude Code?

You can reduce repeated permission prompts in Claude Code by analyzing session JSONL histories to detect recurring approvals and generating a ready-to-apply .claude/settings.json permissions block for safe auto-approval.

How do I find recurring Bash and file edit approvals from Claude Code session histories?

Finding recurring approvals involves parsing per-session JSONL histories to detect repeated Bash commands, file edits, and MCP tool approvals, which can then be consolidated into a minimal permissions set.

Can I automatically generate a .claude/settings.json permissions block from past sessions?

Yes, you can automatically generate a .claude/settings.json permissions block by parsing recent Claude Code session histories, detecting recurring permission patterns, and outputting actionable configuration additions to streamline approvals.

Does analyzing Claude Code session histories work for MCP tool approvals?

Yes, analyzing Claude Code session histories works for MCP tool approvals by parsing per-session JSONL logs to detect recurring permissions across Bash commands, file edits, and MCP tool usage into a unified settings block.

What is the best way to streamline Claude Code permissions across multiple sessions?

The best way to streamline Claude Code permissions across multiple sessions is to parse per-session JSONL histories, identify recurring approvals, and apply a generated .claude/settings.json permissions block to minimize future prompts.