ripwire-handoff SKILL.md skillA
ripwire-handoff from redhat-et/ripwire is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add redhat-et/ripwire/ripwire-handoff@git:20261009.455b2c7Pins git:20261009.455b2c7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- redhat-et/ripwire
- Path
skills/ripwire-handoff/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261009.455b2c7, committed Oct 9, 2026
- First version recorded
- Jul 31, 2026
- Size
- 7,421 bytes
- Repository stars
- 2,530
- License
- Apache-2.0
Brief someone ELSE on a subsystem — 'hand this area off' to a successor, teammate or fresh session: purpose, the 2-3 entry points with bodies, the design docs that say WHY, hotspot/bus-factor risk — a compact pasteable brief, not a wall of source. Understanding it yourself → orient.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Handoff with ripwire > Nearest neighbours: > • You need to UNDERSTAND the subsystem yourself first (not brief someone else) → **ripwire-orient**. > • You need ONE symbol's full contract, not a whole-subsystem brief → **ripwire-navigate** (`--expand`). > • The recipient needs an architecture/layering read specifically → **ripwire-layers**. Trigger: you're handing a subsystem to another agent or developer and want to give them a fast, accurate brief — not a wall of source code. `<dir>` = repo root. `SUBSYSTEM` = the area in plain words (e.g. "ingest pipeline", "graph ranking", "MCP server loop"). 1. **Task-relevant symbols** — `ripwire <dir> --for="SUBSYSTEM" --signatures-only` Output: `<sigs>` ranked by relevance. The top 10 are the symbols the recipient most needs to know. Note their file paths, complexity (`cx=`), and reuse count (`in=`). (`--top-k` does not narrow `--for` — the binary says so on stderr and serves the whole list; `--signatures-only` skips the inline bodies, since step 2 expands the ones you pick.) 2. **Expand the key symbols** — `ripwire <dir> --expand=SYM1,SYM2,SYM3 --legend=compact` (Pick the top 3 by rank from step 1.) …
Read the whole file at its exact version.
How to install
mdr add redhat-et/ripwire/ripwire-handoff@sha256:b968af66108baba0The line at the top of this page pins the label git:20261009.455b2c7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_g6krqq3ozxigq7uf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Jul 31, 2026 and Oct 9, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261009.455b2c7 latest | 2026-10-09 | 455b2c7 | 7,421 B | A | view · diff |
| git:20261007.c70fc81 | 2026-10-07 | c70fc81 | 7,369 B | A | view · diff |
| git:20260913.30a5a3c | 2026-09-13 | 30a5a3c | 7,175 B | A | view · diff |
| git:20260907.9e1e9f9 | 2026-09-07 | 9e1e9f9 | 7,107 B | A | view · diff |
| git:20260810.cc63a3b | 2026-08-10 | cc63a3b | 7,469 B | A | view · diff |
| git:20260803.ef9d174 | 2026-08-03 | ef9d174 | 7,420 B | A | view · diff |
| git:20260801.b78f1c2 | 2026-08-01 | b78f1c2 | 6,625 B | A | view · diff |
| git:20260731.3315fb1 | 2026-07-31 | 3315fb1 | 6,620 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7421 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
redhat-et/ripwire · 2,530 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g6krqq3ozxigq7uf GET https://markdownregistry.com/api/v1/resolve?ref=redhat-et/ripwire/ripwire-handoff GET https://markdownregistry.com/api/v1/blob/b968af66108baba0b42776767ed15eeb9eb2e4eadfc6646fc6618979eddd230a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.