# Health Check

> Report honestly what the agent currently has in its context: instruction files loaded (grouped by level: global, repo, other), skills available, and relevant session state. Use when: the user says 'health check', 'health-check', '/health-check', 'what do you have loaded', 'what instructions/skills do you have', 'what's in your context', or asks for a status of the session.

- Skill: `will12193/health-check` (Agent Skill)
- Install (CLI): `npx get-skill add will12193/health-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/will12193/health-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: will12193 (https://skillmd.com/u/will12193)
- Updated: 2026-11-19
- Page: https://skillmd.com/skills/will12193/health-check

---


# Health check

Companion to `~/.copilot/instructions/coding-agents.instructions.md` (global rules and skill map); this file is the report procedure.

A read-out of the agent's **own current context**, for the user. Be honest and concrete. This is a report, not a task: don't change any files and don't start other work.

## Rules

- Report what is **actually in your context right now** (system prompt, injected instruction blocks, the available-skills list, tool list). Never count something as loaded just because it exists on disk.
- You may do a **read-only listing** (no content reads, no edits) of the standard instruction locations to detect mismatches: `~/.copilot/instructions/`, `~/.copilot/copilot-instructions.md`, and the repo's `.github/instructions/`, `.github/copilot-instructions.md`, `AGENTS.md`, `CLAUDE.md`. Anything on disk but absent from context goes under Concerns as a mismatch, never under "loaded".
- Instruction files with an `applyTo` are path-specific in Copilot CLI: they are only included when the agent is working with a matching file, so in a file-free session they are legitimately absent. Report such files as **present but conditional**, not as broken. Files without `applyTo` should always be loaded; if one is missing, that is a real problem.
- The CLI's `/instructions` command lists discovered instruction files and can toggle them; suggest it when a mismatch is found.
- Don't guess or flatter. If you can't tell whether something is loaded, say "unsure". Never claim an instruction or skill is loaded that you can't point to.
- Loaded context can be stale: instruction files are read at session start, so edits made on disk since then may not be reflected. Say so when relevant.
- Keep it compact: one line per item, no paraphrasing of whole files.

## What to report

### 1. Environment
Working directory, git repo/branch if known, OS, and the model/agent identity if known.

### 2. Instruction files loaded, grouped by level
Work out each file's level yourself from its path and content. Use these groups, in this order, omitting empty ones:

- **Global** (`~/.copilot/instructions/`, user-level, applies to every repo)
- **Repo** (the current repo's `.github/instructions/`, `.github/copilot-instructions.md`, `AGENTS.md`, `CLAUDE.md`, etc.); name the repo it comes from
- **Other** (plugin, org, or anything you can't place)

For each: file name, one-line summary of what it tells you, and `applyTo` if present. Flag any that look like an unfilled template, are empty, duplicated, or conflict with another.

**Sentinel check.** The global instruction file contains a line starting `Health-check sentinel:` followed by a phrase. Look for that line in your loaded context (not on disk) and print the phrase exactly under the Global group, as `Sentinel: "<phrase>"`. If no such line is in your context, print `Sentinel: not found in context`, which means the global instruction file was not injected. Never guess or reconstruct the phrase.

### 3. Skills on hand, grouped by level
Same grouping, from the available-skills list (use each skill's listed location: user/global, repo/project, plugin). One line each: name and a few words on what it's for. For long plugin lists, group by plugin and give a count plus the names, not descriptions.

### 4. Tools and integrations
Short summary only: which tool families are available, which are deferred (need a search first), and any MCP servers. Don't list every tool.

### 5. Session so far
If the session has been going a while (several turns or checkpoints), give a quick summary: what was asked, what was done, what is pending or in flight (todos, background agents, running processes). If the session is new, say so in one line.

### 6. Concerns
Only if there are any: stale or conflicting instructions, context-heavy files, missing expected files (e.g. a repo with no instruction file), unfilled templates, skills with overlapping names/descriptions. One line each with a suggested fix. If none, say "No concerns."

## Format

Headings for the sections above, bullets underneath. Lead with the instruction-file groups (what the user most wants to see). No preamble, no closing offer.

## Maintaining This Skill File

Update this file when the user asks for different or additional information in the report, or when a kind of context turns out to be misreported. Keep it short.

