---
name: self-check
description: >
  Self-diagnose this ClaudeTools machine's harness wiring (tools, identity, hooks, skills, commands, scripts, capability tier, connectivity) against the fleet baseline, and optionally publish the census to coord. Use when the user says /self-check, "self check", "harness check", "doctor", "is everything wired", "fleet conformance".
---

# /self-check — ClaudeTools Harness Self-Diagnosis

This is the Grok-native skill entrypoint. It already has a matching implementation in `.claude/skills/self-check/SKILL.md` (the full model) and the runner script.

**For Grok users:** Invoking /self-check should delegate to or mirror the self-check skill.

- The command thin-runner lives at `.claude/commands/self-check.md`.
- The real engine and baseline are in `.claude/skills/self-check/`.

Recommended:
1. Read `.claude/skills/self-check/SKILL.md` for the complete description, how to run the probe script, interpreting grades (RED/AMBER/GREEN), publishing, fanout, aggregate, etc.
2. Use `run_terminal_command` to execute:
   `SELFCHECK_TS="$(date -u +%Y-%m-%dT%H:%M:%SZ)" bash .claude/skills/self-check/scripts/self-check.sh report`
   (or --json, --publish, etc.)

The self-check is driver-agnostic — it validates the files, scripts, hooks wiring, identity, tools, and the .claude/ + .grok/ harness pieces (including the new Grok hooks and skills we added for coexistence, .grok/config.toml for native MCP like grepai, .grok/agents/ mirrors, .grok/ thin reference docs for memory history/references/standards, and all .grok/skills/ adapters).

See the source skill for full details on modes, the baseline manifest (now includes .grok/ for Grok machines), and how it helps keep the fleet consistent across machines (some running Claude Code, some Grok).

Also update the census component on coord for this host.

When running under Grok, the census should reflect .grok/config.toml , .grok/hooks/claudetools.json , .grok/skills/* (all the command + .claude/skills mirrors + windows-bash), .grok/agents/, .grok/README.md + the pointer docs (REFERENCE.md etc.), and the native MCP loading.

Use GrepAI MCP in the self-check analysis for finding harness pieces.
