verify

Exercise Citadel hook tool calls and validate telemetry side effects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill verify-mferris77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/verify
Command: npx skills add https://github.com/mferris77/SpringBoard --skill verify-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a live, in-session verification of the Citadel hook pipeline by exercising actual tool calls and validating resulting telemetry, ensuring hooks fire and no hook errors are introduced.

Core Features & Use Cases

  • Exercises real tool calls (Write, Edit, Bash, Read) inside a Claude Code session to trigger pre- and post-hook logic.
  • Captures telemetry baselines and validates growth in hook-timing and audit logs while checking for new hook-errors.
  • Produces a per-hook PASS/FAIL report and enforces cleanup of temporary probe files; ideal after hook changes, deployments, or initial installation.

Quick Start

Run the verify skill inside a live session to exercise hooks and generate a HOOK HEALTH report with exact telemetry deltas.

Frequently Asked Questions about verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Claude Code hooks are firing correctly after deployment?

Verify Claude Code hooks by exercising real Write, Edit, Bash, and Read tool calls in a live session, then checking telemetry logs for expected hook-timing growth and confirming no new hook errors appear.

What is the best way to test a Citadel hook pipeline for errors?

Testing a Citadel hook pipeline involves capturing a telemetry baseline, triggering actual tool calls to exercise pre- and post-hook logic, and generating a per-hook PASS/FAIL report to identify any introduced errors.

Can I run an integration test for Claude hooks inside my local development session?

Yes, you can run a live in-session integration test that exercises actual tool calls to trigger hook logic and validates resulting telemetry side effects directly within your local Claude Code development environment.

How do I check telemetry side effects when testing hook pipelines?

Check telemetry side effects by capturing baseline metrics before exercising tool calls, then validating that hook-timing and audit logs show expected growth while confirming the absence of new hook-errors in the delta.

Does the hook verification process clean up temporary probe files automatically?

Yes, the hook verification process enforces the cleanup of temporary probe files created during tool call exercises, ensuring your working directory remains clean after generating the hook health report.

When should I run a hook health check on my Claude Code project?

Run a hook health check after making hook changes, completing deployments, or performing an initial installation to ensure all pre- and post-hook logic fires correctly without introducing new errors.