project-health

Audits and configures Claude Code project settings, permissions, and context files.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill project-health-scsm-unrestrict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-health
Source: https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent/tree/main/frontend-engineer/skills/project-health
Command: npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill project-health-scsm-unrestrict

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Claude Code projects accumulate permission prompts, bloated CLAUDE.md files, leaked secrets in settings, and stale documentation. This Skill centralizes project setup, health auditing, permission tidying, and learning capture into one workflow so configuration stays clean over a project's lifetime. ## Core Features & Use Cases - Full Health Audit: Launches parallel sub-agents to check permissions (missing MCP servers, leaked secrets, legacy syntax, junk entries) and context quality (CLAUDE.md scoring, stale references, missing docs). - New Project Setup: Detects project type from indicator files (wrangler.toml, package.json, Cargo.toml, etc.) and generates settings.local.json, CLAUDE.md, and .gitignore from curated presets. - Permission Presets & Capture Learnings: Merges language/deployment permission presets without duplicates and saves session discoveries to the right context file. - Use Case: After weeks of development, run a health check to find three leaked API keys in settings.local.json, an oversized 400-line CLAUDE.md, and missing ARCHITECTURE.md — then apply all fixes with one confirmation. ## Quick Start Ask the agent to run a project health check and fix any permission or context issues it finds.

Frequently Asked Questions about project-health

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

FAQPage Schema
How do I set up Claude Code permissions for a new project?

Run the setup mode, which detects your project type from files like package.json or wrangler.toml, then generates settings.local.json by stacking the Universal Base preset with language and deployment presets. It also creates CLAUDE.md and .gitignore from templates.

How to audit CLAUDE.md file quality automatically?

The Context Auditor sub-agent scores each CLAUDE.md on a 100-point rubric covering commands, architecture clarity, non-obvious patterns, conciseness, currency, and actionability. It flags oversized files, stale references, and content overlapping with README or docs.

Why does Bash(git *) not match some gh or npx subcommands?

Broad wildcards like Bash(gh *) and Bash(npx *) sometimes miss subcommands due to a known matching bug. The presets include explicit entries such as Bash(gh issue *) and Bash(npx tsc *) as a workaround.

Does project settings.local.json merge with global settings?

No, project settings.local.json shadows global settings entirely rather than merging. Home-relative paths like ~/Documents/** belong only in the global file, and changes require a session restart to take effect.

Can it detect leaked secrets in permission settings?

Yes, the Permission Auditor scans settings.local.json for entries containing API keys, tokens, bearer strings, and long hex or base64 values. Findings are reported in the health check with recommended removals.