runtime-evidence

Verifies config and behavioral changes actually execute at runtime using surface-specific probes.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/skills --skill runtime-evidence-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-evidence
Source: https://github.com/leonardoacosta/skills/tree/main/leo-core/skills/runtime-evidence
Command: npx skills add https://github.com/leonardoacosta/skills --skill runtime-evidence-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Config-shaped deliverables like lifecycle hooks, injected prompt blocks, status indicators, and settings keys have no test suite to run, so a change that parses and registers can still silently never fire. This Skill closes that gap by mapping each surface class to its cheapest runtime probe, proving the mechanism fired and the intended behavior changed before any completion claim. ## Core Features & Use Cases - Wired/Fired/Effected Ladder: Enforces three verification rungs so a config that merely parses is never mistaken for one that actually ran. - Probe Table by Surface Class: Maps hooks, event wiring, settings keys, injected context blocks, status indicators, preprocessors, command definitions, agent definitions, auto-triggers, git hooks, and scheduled jobs to concrete fire/effect probes. - Dead-Event Diagnosis: Cross-checks a co-resident always-on handler on the same event to distinguish a dead runtime event from a broken matcher. - Use Case: After adding a completion hook to your agent harness, run the hook script directly with a synthetic event payload and paste its stdout as evidence, then trigger the real event once in a scratch context and confirm the marker file updated. ## Quick Start Ask the agent to verify that your newly configured hook or injected context block actually fires at runtime and to paste the probe evidence before marking the task done.

Frequently Asked Questions about runtime-evidence

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

FAQPage Schema
How do I verify a lifecycle hook actually runs?

Execute the hook script directly with a synthetic payload shaped like the real event and paste its stdout and exit code. Then trigger the real event once in a scratch context and confirm firing via a log entry, marker file, or captured trace.

How to test that a config change works without a test suite?

Climb the wired/fired/effected ladder: confirm the artifact parses and registers, prove the mechanism executed at runtime, then show the intended behavior changed. Claim done only with a rung-2 or rung-3 evidence artifact pasted verbatim.

Why does my registered hook never fire?

The runtime event it depends on may never fire in that environment, even though the config reads correctly. Cross-check an always-on handler on the same event over the same window; silence on both means the event is dead, not your matcher.

Can I verify a hook by re-reading its config file?

No. Reading the config only proves the artifact is wired, not that it fired or had an effect. A registered handler can sit correctly in config for months and execute zero times, so only runtime execution evidence counts.

When should I re-verify config surfaces after changes?

Re-run the probe for every affected surface after any bulk config rewrite, since sweeping changes are how live keys get silently dropped. For surfaces that must keep working, add an ongoing liveness check or periodic re-probe.