This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
ketchup-video from painhardcore/pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text under it. Use for /ketchup-video.
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
# Ketchup video
Follow [`/ketchup`](../ketchup/SKILL.md), but show what happened in a short subtitled video instead of its summary and visuals. Its window starts at the last message the user wrote before `/ketchup-video`, not before any earlier `/ketchup`. Writing and rendering the video, outside the repo, is the one exception to its read-only rule. The reply is ketchup's opening sentence, the embedded video, one line naming any work left that you can do yourself, and the action items. When the video shows a call's options, call each option by the name the video gives it. If the render fails, say so in one line and give only the calls.
## Slides
Use the screenshots, recordings, diffs, and data the work produced, not the chat's prose about them. Before you draw, write the one sentence the user should leave with and one line per slide. Drop each slide that does not change what the user knows. Use at most 10 slides, and fewer is better. Neither note goes in the reply.
…
The line at the top of this page pins the label git:20261101.1922dfd, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_zybgruffdea4o7ou
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/ketchup-video
GET https://markdownregistry.com/api/v1/blob/fa032bece48c7255575179e6d002425dc303cc2e2f23c45b476bcdb12fc8da5b
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.
painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
painhardcore/pstack · .opencode/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
painhardcore/pstack · .opencode/skills/benchmark-checklist/SKILL.md · Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened)…
painhardcore/pstack · .opencode/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
painhardcore/pstack · .opencode/skills/correct/SKILL.md · Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types…
painhardcore/pstack · .opencode/skills/create-formal-verification-skill/SKILL.md · Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in…
painhardcore/pstack · .opencode/skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
painhardcore/pstack · .opencode/skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
painhardcore/pstack · .opencode/skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
painhardcore/pstack · .opencode/skills/in-your-own-words/SKILL.md · Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for…
painhardcore/pstack · .opencode/skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
cursor/plugins · harness/pstack/claude-code/skills/ketchup-video/SKILL.md · Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text…
cursor/plugins · pstack/skills/ketchup-video/SKILL.md · Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text…
michael-denyer/pstack-claude · plugins/pstack/skills/ketchup-video/SKILL.md · Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text…
backnotprop/pstack · skills/ketchup-video/SKILL.md · Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text…
creedants/pstack-t3 · skills/ketchup-video/SKILL.md · Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text…
arjitj2/open-pstack · plugins/pstack/skills/ketchup-video/SKILL.md · Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text…
painhardcore/pstack · skills/ketchup-video/SKILL.md · Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text…
