boost-check

name	boost-check
description	Run a read-only diagnostic of your Claude Code setup. Shows your Boost Score and lists what's configured vs. what's missing across 3 levels.
argument-hint	[level]
allowed-tools	["Read","Glob","Grep","Bash"]

Boost Check — Configuration Diagnostic

Run a read-only diagnostic of the user's Claude Code setup. Report findings without making changes.

Instructions

When this skill is invoked, perform ALL diagnostic checks below, then display the results.

If the user passes an argument (e.g., /boost-check 2), only diagnose that level. Otherwise diagnose all levels.

Step 1: Run Diagnostics

Check each item below. For each, record status as CONFIGURED or MISSING.

Level 1 — Essentials

1.1 CLAUDE.md

• Check: Does CLAUDE.md exist in the current project root?
• How: Use Glob to find CLAUDE.md in the working directory
• CONFIGURED if: File exists AND has more than 5 lines
• MISSING if: File does not exist or has 5 or fewer lines
• Also check: Does it contain a "Model routing" or "model" section? If CLAUDE.md exists but has no model routing → flag as "CLAUDE.md exists but missing model routing"

1.2 settings.json

• Check: Read ~/.claude/settings.json
• CONFIGURED if: File exists AND has a permissions object with at least one allow entry
• MISSING if: File doesn't exist, or permissions is empty, or all entries are deny/empty

1.3 Memory System

• Check: Does the project's memory directory have a MEMORY.md?
• How: Read ~/.claude/projects/ — find the subdirectory matching the current project path, then check for MEMORY.md
• CONFIGURED if: MEMORY.md exists and has at least one entry
• MISSING if: No MEMORY.md or empty

Level 2 — Power Features

2.1 CLAUDE.md Advanced

• Check: Does CLAUDE.md contain sections for context management or workflow modes?
• How: Read CLAUDE.md, search for keywords: "compact", "context management", "mode", "workflow", "debug", "routing"
• CONFIGURED if: At least 2 of these keywords found in distinct sections
• MISSING if: Fewer than 2 found

2.2 MCP Servers

• Check: Read ~/.claude/mcp.json and project .mcp.json
• CONFIGURED if: At least one MCP server is defined in either file
• MISSING if: Neither file exists or both are empty

2.3 Plugins

• Check: Read ~/.claude/plugins/installed_plugins.json
• CONFIGURED if: At least 2 plugins installed (boost itself doesn't count)
• MISSING if: 0-1 plugins (excluding boost)

2.4 Git Integration

• Check: Is the current directory a git repository?
• How: Run git rev-parse --is-inside-work-tree 2>/dev/null
• CONFIGURED if: Is a git repo
• MISSING if: Not a git repo

Level 3 — Expert

3.1 Hooks

• Check: Read ~/.claude/settings.json for a hooks section
• CONFIGURED if: At least one custom hook defined (not from plugins)
• MISSING if: No hooks section or empty

3.2 Keybindings

• Check: Read ~/.claude/keybindings.json
• CONFIGURED if: File exists and has at least one custom binding
• MISSING if: File doesn't exist or is default/empty

Step 2: Calculate Boost Score

Count configured items per level:

• Level 1: X/3
• Level 2: X/4
• Level 3: X/2
• Total: X/9

Step 3: Display Results

Format the output as follows:

╔══════════════════════════════════════════════════╗
║  Boost Score: X/9                                ║
║  Level 1: a/3 | Level 2: b/4 | Level 3: c/2     ║
╚══════════════════════════════════════════════════╝

Level 1 — Essentials
  ✓ CLAUDE.md — configured (but missing model routing)
  ✗ settings.json — permissions not configured
  ✗ Memory system — not set up

Level 2 — Power Features
  ✗ CLAUDE.md advanced — no workflow/mode sections
  ✓ MCP servers — 2 servers configured
  ✗ Plugins — only 1 plugin installed
  ✓ Git — repository detected

Level 3 — Expert
  ✗ Hooks — no custom hooks
  ✗ Keybindings — using defaults

Run /boost to set up missing items.

Adapt the check marks and descriptions based on actual findings. Use ✓ for CONFIGURED and ✗ for MISSING.

Important

• This skill is READ-ONLY. Do not create, modify, or delete any files.
• If a file cannot be read (permission error), report it as "Unable to check" rather than MISSING.
• Always suggest /boost at the end for users who want to fix issues.