Skip to content
Back to skills

Gait Capture Runpack

ASecurity

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.

  • 57 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
tools

Works with

  • cli

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill gait-capture-runpack --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gait Capture Runpack?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gait Capture Runpack
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-gait-capture-runpack/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-gait-capture-runpack)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gait-capture-runpack
description: 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.
disable-model-invocation: true
---
# 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.