# Gait Capture Runpack

> Capture and verify deterministic Gait runpacks from normalized run input. Use when asked to record a run, produce run_id or runpack artifacts, generate ticket-ready proof, or validate artifact integrity before handoff. Use when this capability is needed.

- Skill: `tomevault-io/gait-capture-runpack` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/gait-capture-runpack`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/gait-capture-runpack/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/gait-capture-runpack

---

# Capture Runpack

Execute this workflow to record an artifact safely and deterministically.

## Gait Context

Gait is an offline-first runtime for AI agents that enforces tool-boundary policy, emits signed and verifiable evidence artifacts, and supports deterministic regressions.

Use this skill when:
- incident triage needs captured run artifacts for reproduction
- CI gate failures need verifiable artifact identity and integrity
- receipt/evidence generation depends on runpack metadata and digests

Do not use this skill when:
- Gait CLI is unavailable in the environment
- no Gait run input or artifact source is available

## Workflow

1. Validate required input path: `<run_record.json>`.
2. Run record with JSON output (required):
   - `gait run record --input <run_record.json> --json`
3. Parse output fields:
   - `ok`, `run_id`, `bundle`, `manifest_digest`, `ticket_footer`
4. Verify artifact integrity (required):
   - `gait verify <run_id_or_bundle_path> --json`
5. Return a concise handoff block that includes:
   - `run_id`
   - `bundle`
   - `manifest_digest`
   - `ticket_footer`
   - verify status

## Safety Rules

- Keep default capture mode as `reference`.
- Do not switch to raw capture unless explicitly requested.
- For replay workflows, prefer `gait run replay` (stub mode default); require explicit unsafe flags for real tool replay.
- Do not invent `run_id`, digests, or verify results.
- Treat non-zero exit from `gait run record` or `gait verify` as blocking errors.
- Keep this skill wrapper-only: do not parse policy YAML or implement custom evaluator logic.

## Determinism Rules

- Always use `--json` and parse structured fields.
- Do not rely on text-only output for workflow decisions.
- Keep output grounded in recorded artifact values only.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/clyra-ai) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->