permission-check

Diagnose Claude Code permission issues by analyzing settings across multiple layers.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/fredmilhome/laffer_tobacco --skill permission-check-fredmilhome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permission-check
Source: https://github.com/fredmilhome/laffer_tobacco/tree/main/.claude/skills/permission-check
Command: npx skills add https://github.com/fredmilhome/laffer_tobacco --skill permission-check-fredmilhome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users quickly diagnose why Claude Code is prompting for permission, providing a clear overview of the permission mode across all relevant layers.

Core Features & Use Cases

  • Permission Mode Visualization: Shows the full permission-mode picture across all layers Claude Code honors, making it easy to understand why prompts are (or aren't) firing.
  • Layer Analysis: Identifies which layer is causing the permission issue, whether it's a local or host-global setting.
  • Read-Only Diagnostic: Designed for defense-in-depth, the skill reads only repo-local files by default and requires explicit user confirmation to read host-global files.

Quick Start

Run the 'permission-check' skill to diagnose permission issues in Claude Code.

Frequently Asked Questions about permission-check

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

FAQPage Schema
Why does Claude Code keep prompting for permission despite my project settings?

Claude Code permission prompts can occur when a higher-priority settings layer overrides your project configuration. This diagnostic analyzes permission mode across VSCode user, CLI user, workspace, and project layers to pinpoint the exact source.

How do I check my Claude Code permission mode across different settings layers?

You can check Claude Code permission mode by running a diagnostic script that reads and visualizes settings across VSCode, CLI, workspace, and project layers. It safely defaults to repo-local files and requests confirmation for host-global access.

What is a permission settings layer in Claude Code?

A permission settings layer in Claude Code represents a specific configuration level, such as VSCode user, workspace, CLI user, or project-local settings. Each layer can enforce different permission modes that affect prompt behavior.

Can I diagnose Claude Code permission issues without modifying my global settings?

Yes, you can diagnose permission issues safely without immediate global changes. The diagnostic reads only repo-local files by default and requires explicit user confirmation before accessing any host-global settings files.

What's the best way to troubleshoot Claude Code permission mode conflicts?

The best way to troubleshoot Claude Code permission mode conflicts is to analyze the full settings hierarchy. This diagnostic identifies the specific VSCode, CLI, or project layer causing the unwanted permission prompt.