pdugan20/validate-all
skills/validate-all/SKILL.md
Runs comprehensive claudelint validation on all Claude Code project files. Use when user asks to "check everything", "run all validators", "full audit", "validate my entire project", or "what's wrong with my config". Validates CLAUDE.md, skills, settings, hooks, MCP servers, and plugin manifests.
$ install --global
skillsauthnpx skillsauth add pdugan20/claudelint validate-allInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 11:20 AM117.5s5 files scanned
SKILL.md
- name:
- validate-all
- description:
- Runs comprehensive claudelint validation on all Claude Code project files. Use when user asks to "check everything", "run all validators", "full audit", "validate my entire project", or "what's wrong with my config". Validates CLAUDE.md, skills, settings, hooks, MCP servers, and plugin manifests.
- version:
- 1.0.0
- argument-hint:
- [flags]
- - Bash(claudelint:
- *)
Validate Claude Code Project
Runs claudelint check-all to validate all Claude Code project files including CLAUDE.md, skills, settings, hooks, MCP servers, and plugin manifests.
Usage
claudelint check-all $ARGUMENTS
Options
Available flags:
--verbose- Show detailed validation output--warnings-as-errors- Treat warnings as errors--explain- Show detailed explanations and fix suggestions--format <format>- Output format: stylish, json, compact (default: stylish)--config <path>- Path to custom config file--fast- Fast mode: skip expensive checks--color/--no-color- Control color output
Examples
Example 1: Plugin won't load after changes
User says: "I just updated my CLAUDE.md and added a new skill, but now my plugin isn't loading" What happens:
- Skill runs
claudelint check-all - Finds CLAUDE.md exceeds 50KB (blocking issue)
- Finds new skill has wrong capitalization in allowed-tools
- Shows both issues need fixing before plugin will load
Result: User identifies why plugin broke and fixes both issues
Example 2: Pre-commit validation failed
User says: "My git pre-commit hook is failing but I don't know which validator is the problem" What happens:
- Skill runs
claudelint check-all --verbose - Shows validate-mcp failed: invalid transport type "sse" (deprecated)
- Shows validate-hooks passed, validate-skills passed, etc.
- Points to specific .mcp.json file and line number
Result: User fixes the one failing validator (MCP config) and commit succeeds
Example 3: After npm install, verify everything still works
User says: "I just upgraded claude-code-lint, make sure I didn't break anything" What happens:
- Skill runs
claudelint check-all - Detects new rules flagging previously-allowed patterns
- Shows deprecation warnings for old syntax
- Suggests migration path for deprecated features
Result: User knows what needs updating after version upgrade
Command Examples
Basic validation:
claudelint check-all
Verbose output with explanations:
claudelint check-all --verbose --explain
JSON output for CI/CD:
claudelint check-all --format json
Use custom config:
claudelint check-all --config .claudelintrc.custom.json
Treat warnings as errors (strict mode):
claudelint check-all --warnings-as-errors
What Gets Validated
The validate skill checks:
- CLAUDE.md files - File size, imports, frontmatter, sections
- Skills - SKILL.md schema, naming, documentation, security
- Settings - settings.json schema, permissions, environment variables
- Hooks - hooks.json schema, events, commands
- MCP Servers - .mcp.json schema, transport config, variables
- Plugins - plugin.json schema, semantic versioning, references
Exit Codes
0- No errors or warnings1- Warnings found (or warnings treated as errors)2- Errors found or fatal error (invalid config, crash)
For troubleshooting, see common issues. For customization, see configuration.
See Also
- validate-cc-md - Validate only CLAUDE.md files
- validate-skills - Validate only skills
- validate-settings - Validate only settings
- format-cc - Format Claude files with prettier/markdownlint
Related Skills
pdugan20/test-skill
testing
VerifiedTrustedCommunity
A valid test skill for testing purposes. Use this when you want to test skill validation.
5SKILL.mdUpdated Apr 28, 2026
pdugan20/no-version-skill
testing
VerifiedTrustedCommunity
This skill is missing the version field for testing purposes.
5SKILL.mdUpdated Apr 28, 2026
pdugan20/dangerous-skill
testing
VerifiedTrustedCommunity
This skill contains dangerous commands for testing security validation.
5SKILL.mdUpdated Apr 28, 2026
pdugan20/validate-skills
tools
VerifiedTrustedCommunity
Validates Claude Code skills for schema, naming, documentation, and security. Use when user asks to "check my skill", "validate skill syntax", "why isn't my skill loading", "skill errors", or "dangerous command detected". Validates SKILL.md frontmatter, allowed-tools, file references, directory organization, and shell script security.
5SKILL.mdUpdated Apr 28, 2026