Context Boundary Reporter
Generate a machine-readable receipt documenting project context files and decisions.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/context-boundary-reporter-edonadei/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Works for every skill.What this command does
- Makes a new, empty temporary folder.
- Downloads the skill's folder,
examples/05-context-boundary, fromgithub.com/edonadei/caliper(branchmain), the GitHub repository it's listed from. You get the version that is there now, not a copy we keep. - Copies that folder to
~/.claude/skills/context-boundary-reporter-edonadei/. - Deletes the temporary folder.
Installing runs none of the skill's files; it only downloads and copies them. When you later use the skill, Claude follows its SKILL.md and may run scripts that come with it. Read them first.
Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
Write a machine-checkable context boundary receipt from provided project context files.
What this skill does
Context Boundary Reporter
When asked to produce a context boundary receipt, inspect only the files named in the request and write JSON to the requested output path.
Use this exact shape:
{
"loaded_context": [
{"ref": "path", "kind": "instructions|decision|transcript", "authority": "durable|ephemeral"}
],
"durable_decisions": [
{"decision": "...", "source_ref": "...", "supersedes": ["..."]}
],
"stale_or_excluded_items": [
{"item": "...", "source_ref": "...", "reason": "..."}
],
"verification_path": ["..."]
}
Rules:
- Treat explicit ADR/design files as more authoritative than raw transcript notes.
- Include transcript notes only as
ephemeralcontext unless another durable file confirms them. - If a transcript claim conflicts with a durable decision, put the transcript claim under
stale_or_excluded_itemsinstead ofdurable_decisions. - Do not invent files, commands, or decisions that were not present in the named inputs.
- Write only valid JSON to the requested output file.
- Write the JSON file to the requested path before you report anything. Never say the receipt is done unless you have actually written that file.
Related skills
Word Document Editor
anthropics
Create, edit, and format Word documents with tables, images, and tracked changes.
Ask Questions If Underspecified
trailofbits
Ask clarifying questions before starting work on ambiguous requests.
CLAUDE.md Optimizer
daymade
Optimize your CLAUDE.md file for clarity, efficiency, and maintainability.
Claude Skills Troubleshooter
daymade
Diagnose and fix plugin installation, enablement, and activation problems.