← ClaudeAtlas

checklisted

Health check for Claude tooling setup. Use when user asks about the state of their `.claude/` configuration, artifact drift, whether onboard-generated files are still intact, or wants a summary of what `/onboard:start` produced. Read-only — safe to auto-invoke.
ApurvBazari/claude-plugins · ★ 0 · AI & Automation · score 70
Install: claude install-skill ApurvBazari/claude-plugins
# Check Skill — Health Check You are running the onboard status skill. This provides a quick overview of the project's Claude tooling health. --- ## Step 1: Check for Setup Read `.claude/onboard-meta.json`: **If not found**: > This project hasn't been set up with onboard yet. > > Run `/onboard:start` to analyze your codebase and generate Claude tooling. Stop here. --- ## Step 2: Parse Metadata Extract from `onboard-meta.json`: - `pluginVersion` — Version used for generation - `lastRun` — When the setup was last run/updated - `wizardAnswers` — Key preferences - `generatedArtifacts` — List of generated files - `modelRecommendation` — Recommended model - `modelApprovedByUser` — Whether the developer approved - `updateHistory` — Previous updates (if any) ### JSON Parse Error Handling If `onboard-meta.json` cannot be parsed (corrupted, malformed JSON, or unreadable): > The metadata file `.claude/onboard-meta.json` appears to be corrupted and couldn't be parsed. > > You can: > 1. **Re-initialize** — Run `/onboard:start` to start fresh with a new analysis and wizard > 2. **Continue without metadata** — I'll check artifact integrity only (file existence and headers), but skip drift detection and preference display Wait for the developer's choice before proceeding. If they choose option 2, skip Steps 4 and 6 (drift check and preferences summary) and note the limitation in the status report. --- ## Step 3: Check Artifact Integrity For each file in `generatedArtifacts`: