Validate Settings

Name: Validate Settings
Author: pdugan20

ASecurity

Validates Claude Code settings.json files for schema, permissions, and security. Use when user asks to "check my settings", "validate settings.json", "permission errors", "environment variable issues", or "settings syntax errors". Validates model names, permission rules, hooks configuration, and environment variables.

12 stars
0 votes
0 copies
2 views
Added May 26, 2026

toolsbashsecurity

Works with

claude code

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add pdugan20/claudelint --skill validate-settings --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Validate Settings?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Validate Settings

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pdugan20-validate-settings/badge)](https://www.skillsdirectory.com/skills/pdugan20-validate-settings)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: validate-settings
description: Validates Claude Code settings.json files for schema, permissions, and security. Use when user asks to "check my settings", "validate settings.json", "permission errors", "environment variable issues", or "settings syntax errors". Validates model names, permission rules, hooks configuration, and environment variables.
version: 1.0.0
argument-hint: "[flags]"
allowed-tools:
  - Bash(claudelint:*)
---

# Validate Settings

Runs `claudelint validate-settings` to validate `.claude/settings.json` and `.claude/settings.local.json` files.

## Usage

```bash
claudelint validate-settings $ARGUMENTS
```

## Options

- `--path <path>` - Custom path to settings.json
- `--verbose` - Show detailed output
- `--warnings-as-errors` - Treat warnings as errors

## What Gets Validated

- JSON syntax
- Model validation (sonnet, opus, haiku)
- Permission rules (tool names, actions: allow/block)
- Hooks configuration
- Environment variables (naming, empty values, secrets detection)

## Examples

```bash
claudelint validate-settings
claudelint validate-settings --path /path/to/settings.json
```

## See Also

- [validate-all](../validate-all/SKILL.md) - Run all validators