[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AAC0MSSRGJNRN1VF29TCR5":3,"skill-same:01M7AAC0MSSRGJNRN1VF29TCR5":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AAC0MSSRGJNRN1VF29TCR5","terminal-gif",null,"Record polished GIFs (and MP4\u002FWebM\u002FPNG) of terminal programs — CLIs, TUIs, REPLs, dotfiles, your own tools — by scripting them with VHS. Use this whenever the user wants to \"make a gif\", \"record a terminal\", \"capture a CLI\u002FTUI demo\", \"show this command running\", \"create a demo for the README\", \"animate my tool\", \"screen-record the terminal\", or asks for an asciinema-style recording, a terminal screenshot, or a demo of how a command-line program behaves. Trigger even when the user only describes the behavior they want to capture (e.g. \"show what happens when I run `mytool init`\") without naming GIF or VHS explicitly.","JasperHG90\u002Fshakedown","JasperHG90","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8079803?v=4","01M7AAAKN62DYZ9XRCXAN0HGEF","Jasper Ginn","01M7AAAKP8D78B8ANVKEV7MRK8",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fterminal-gif\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: terminal-gif\ndescription: |\n  Record polished GIFs (and MP4\u002FWebM\u002FPNG) of terminal programs — CLIs, TUIs, REPLs, dotfiles, your own tools — by scripting them with VHS. Use this whenever the user wants to \"make a gif\", \"record a terminal\", \"capture a CLI\u002FTUI demo\", \"show this command running\", \"create a demo for the README\", \"animate my tool\", \"screen-record the terminal\", or asks for an asciinema-style recording, a terminal screenshot, or a demo of how a command-line program behaves. Trigger even when the user only describes the behavior they want to capture (e.g. \"show what happens when I run `mytool init`\") without naming GIF or VHS explicitly.\n---\n\n## What this skill does\n\nTurns a description of a terminal interaction into a rendered GIF (or MP4\u002FWebM\u002FPNG)\nusing [VHS](https:\u002F\u002Fgithub.com\u002Fcharmbracelet\u002Fvhs). The user tells you what they want\nto capture; you write a declarative `.tape` script and render it.\n\n**Why VHS over alternatives** (asciinema, terminalizer, ttygif, t-rec): VHS is the\nonly one that is *fully scriptable and deterministic*. You write a tape file that says\n\"type this, wait for that, press Enter, sleep, screenshot\" and it renders identically\nevery time — no live recording session to drive, no manual timing. It also produces\nGIF, MP4, WebM, animated WebP, and PNG screenshots from the same script, with control\nover font, theme, window chrome, and dimensions. That makes it the right tool for an\nagent: you can author, render, inspect, and refine without a human at the keyboard.\n\n## The workflow\n\n```\n1. Check dependencies      → verify: vhs\u002Fttyd\u002Fffmpeg present (ask before installing)\n2. Understand the capture   → verify: you know the commands, timing, and output format\n3. Write the .tape file     → verify: `vhs validate file.tape` passes\n4. Render                    → verify: `vhs file.tape` exits 0 and the output file exists & is non-empty\n5. Inspect & refine          → verify: the GIF actually shows what the user asked for\n```\n\n### 1. Check dependencies (always, first)\n\nVHS needs three things on PATH: `vhs`, `ttyd`, and `ffmpeg`. Run the bundled check:\n\n```bash\nbash scripts\u002Fcheck_deps.sh\n```\n\nIt reports what's present and prints the correct install command for the detected OS\n(macOS via Homebrew, Linux via Charm's apt repo or Homebrew). **If anything is missing,\nask the user for permission before installing it** — do not silently install. Installing\ndeveloper tooling changes their machine, so it's their call. Once they say yes, run the\ncommand the script printed.\n\n### 2. Understand what to capture\n\nBefore writing a tape, get clear on these. Infer what you can from the repo and context;\nask only about what you genuinely can't determine:\n\n- **The exact commands \u002F keystrokes** in order. For a real program, what's actually typed?\n- **What signals \"done\"** for each step — a prompt returning, a specific line of output,\n  a TUI finishing its render. This determines whether you use `Sleep` or `Wait` (see below).\n- **Output format**: GIF is the default. Offer MP4\u002FWebM for smoother\u002Flonger demos (much\n  smaller files), or PNG via `Screenshot` for a still.\n- **Where the file should go** (e.g. `assets\u002Fdemo.gif`, repo root, `docs\u002F`).\n- **Look & feel**: theme, font size, dimensions, window bar. Sensible defaults are fine;\n  match the repo's existing demo assets if any exist.\n\n### 3. Write the `.tape` file\n\nA tape is a sequence of settings then commands. Skeleton:\n\n```tape\n# what this demo shows\nOutput assets\u002Fdemo.gif\n\nRequire mytool          # abort early if the program under test isn't installed\n\nSet Shell \"bash\"\nSet FontSize 22\nSet Width 1200\nSet Height 700\nSet Theme \"Dracula\"\nSet Padding 20\n\n# --- silent setup: runs but isn't shown in the GIF ---\nHide\nType \"cd \u002Fpath\u002Fto\u002Fproject && clear\" Enter\nShow\n\n# --- the actual demo ---\nType \"mytool init\" Sleep 500ms Enter\nWait                    # wait for the shell prompt to return\nSleep 1s\n```\n\nThe full command reference — every setting, key, and timing modifier — is in\n`references\u002Fvhs-tape.md`. Read it when you need anything beyond the basics below.\n\n**The patterns that matter most:**\n\n- **`Type \"...\"`** types a string at the configured typing speed. Follow with `Enter` to run.\n  Per-command speed override: `Type@30ms \"fast typing\"`.\n- **Timing — prefer `Wait` over guessing `Sleep`.** `Sleep 2s` pauses a fixed time and is\n  fine for short, predictable output. But for *real programs* whose timing varies, fixed\n  sleeps are fragile — too short and you capture a half-finished screen, too long and the\n  GIF drags. Use `Wait+Screen \u002Fregex\u002F` to block until matching text appears on screen, or\n  `Wait+Line \u002Fregex\u002F` for the current line. Plain `Wait` waits for the shell prompt. This\n  makes recordings robust regardless of how fast the machine is.\n- **`Hide` \u002F `Show`** run commands without recording them — use for `cd`, `clear`, exports,\n  and any setup the viewer shouldn't see. The demo starts clean.\n- **Keys**: `Enter`, `Tab`, `Space`, `Backspace`, `Up`\u002F`Down`\u002F`Left`\u002F`Right`, `Ctrl+C`,\n  `Ctrl+L`, `Escape`. Repeat with a count: `Down 3`, `Enter 2`.\n- **`Screenshot path.png`** grabs a still at that point — great for a quick visual sanity\n  check mid-development, or as the deliverable when the user wants a static image.\n\n### 4. Render\n\n```bash\nvhs file.tape\n```\n\nVHS exits non-zero on a bad tape. Always confirm the output file exists and is non-empty\nafterward (`ls -lh \u003Coutput>`). A 0-byte or missing file means the render failed even if the\ncommand looked like it ran.\n\nFor a fast iteration loop while dialing in timing, render to a single screenshot or a short\nclip first rather than re-rendering a long GIF every time.\n\n### 5. Inspect and refine\n\nYou can't \"see\" a GIF directly, but you can verify it meaningfully:\n\n- Add a `Screenshot frames\u002Fcheck.png` at a key moment and **Read the PNG** to confirm the\n  screen shows what you expect (the right output, no error, correct theme).\n- Check file size is reasonable — a multi-MB GIF for a 5-second clip usually means the\n  dimensions\u002Ffont are too large; offer MP4 instead.\n- Re-read the tape against the user's request: are all the steps there, in order, with\n  enough pause to be readable?\n\nThen show the user the path and a one-line summary of what it captures. If the user is in\na UI that can render it, the GIF will display.\n\n## Scenario playbook\n\n**Real program runs** (their own CLI\u002FTUI, `htop`, `vim`, etc.): use `Require` to assert\nthe binary exists, `Hide`\u002F`Show` for setup, and `Wait+Screen`\u002F`Wait+Line` for timing so the\ncapture survives machine-speed differences. Don't fake output — drive the actual program.\n\n**Scripted demos for docs\u002FREADMEs**: clarity beats realism. Slightly slower `TypingSpeed`,\ndeliberate `Sleep`s between steps so each is readable, a clean theme, and a window bar\n(`Set WindowBar Colorful`) look professional embedded in a README.\n\n**Interactive TUIs** (menus, `fzf`, full-screen apps): drive navigation with arrow keys,\n`Tab`, `Enter`. Give the app a `Sleep` to finish its initial render before interacting, and\nuse `Wait+Screen \u002F…\u002F` keyed to text the TUI draws when ready. End with the key that exits\ncleanly (often `q`, `Ctrl+C`, or `Escape`) so the final frame isn't a stuck screen.\n\n**Multi-format output**: one tape can emit several files — list multiple `Output` lines with\ndifferent extensions (`.gif`, `.mp4`, `.webp`, `.ascii`). Recommend MP4\u002FWebM for anything\nlonger than a few seconds or with lots of motion; GIFs balloon in size fast.\n\n## Gotchas\n\n- `vhs validate file.tape` checks syntax without rendering — run it before the full render to\n  catch typos cheaply.\n- `vhs new demo.tape` scaffolds a starter tape if you want a quick template.\n- Long GIFs get huge. Keep demos tight, or switch format. Dimensions and font size drive size\n  more than duration.\n- `Set` commands must come before the commands they affect (ideally all at the top).\n- If a real program needs a TTY or specific env, set it with `Env KEY value` and `Set Shell`.\n","## What this skill does\n\nTurns a description of a terminal interaction into a rendered GIF (or MP4\u002FWebM\u002FPNG)\nusing [VHS](https:\u002F\u002Fgithub.com\u002Fcharmbracelet\u002Fvhs). The user tells you what they want\nto capture; you write a declarative `.tape` script and render it.\n\n**Why VHS over alternatives** (asciinema, terminalizer, ttygif, t-rec): VHS is the\nonly one that is *fully scriptable and deterministic*. You write a tape file that says\n\"type this, wait for that, press Enter, sleep, screenshot\" and it renders identically\nevery time — no live recording session to drive, no manual timing. It also produces\nGIF, MP4, WebM, animated WebP, and PNG screenshots from the same script, with control\nover font, theme, window chrome, and dimensions. That makes it the right tool for an\nagent: you can author, render, inspect, and refine without a human at the keyboard.\n\n## The workflow\n\n```\n1. Check dependencies      → verify: vhs\u002Fttyd\u002Fffmpeg present (ask before installing)\n2. Understand the capture   → verify: you know the commands, timing, and output format\n3. Write the .tape file     → verify: `vhs validate file.tape` passes\n4. Render                    → verify: `vhs file.tape` exits 0 and the output file exists & is non-empty\n5. Inspect & refine          → verify: the GIF actually shows what the user asked for\n```\n\n### 1. Check dependencies (always, first)\n\nVHS needs three things on PATH: `vhs`, `ttyd`, and `ffmpeg`. Run the bundled check:\n\n```bash\nbash scripts\u002Fcheck_deps.sh\n```\n\nIt reports what's present and prints the correct install command for the detected OS\n(macOS via Homebrew, Linux via Charm's apt repo or Homebrew). **If anything is missing,\nask the user for permission before installing it** — do not silently install. Installing\ndeveloper tooling changes their machine, so it's their call. Once they say yes, run the\ncommand the script printed.\n\n### 2. Understand what to capture\n\nBefore writing a tape, get clear on these. Infer what you can from the repo and context;\nask only about what you genuinely can't determine:\n\n- **The exact commands \u002F keystrokes** in order. For a real program, what's actually typed?\n- **What signals \"done\"** for each step — a prompt returning, a specific line of output,\n  a TUI finishing its render. This determines whether you use `Sleep` or `Wait` (see below).\n- **Output format**: GIF is the default. Offer MP4\u002FWebM for smoother\u002Flonger demos (much\n  smaller files), or PNG via `Screenshot` for a still.\n- **Where the file should go** (e.g. `assets\u002Fdemo.gif`, repo root, `docs\u002F`).\n- **Look & feel**: theme, font size, dimensions, window bar. Sensible defaults are fine;\n  match the repo's existing demo assets if any exist.\n\n### 3. Write the `.tape` file\n\nA tape is a sequence of settings then commands. Skeleton:\n\n```tape\n# what this demo shows\nOutput assets\u002Fdemo.gif\n\nRequire mytool          # abort early if the program under test isn't installed\n\nSet Shell \"bash\"\nSet FontSize 22\nSet Width 1200\nSet Height 700\nSet Theme \"Dracula\"\nSet Padding 20\n\n# --- silent setup: runs but isn't shown in the GIF ---\nHide\nType \"cd \u002Fpath\u002Fto\u002Fproject && clear\" Enter\nShow\n\n# --- the actual demo ---\nType \"mytool init\" Sleep 500ms Enter\nWait                    # wait for the shell prompt to return\nSleep 1s\n```\n\nThe full command reference — every setting, key, and timing modifier — is in\n`references\u002Fvhs-tape.md`. Read it when you need anything beyond the basics below.\n\n**The patterns that matter most:**\n\n- **`Type \"...\"`** types a string at the configured typing speed. Follow with `Enter` to run.\n  Per-command speed override: `Type@30ms \"fast typing\"`.\n- **Timing — prefer `Wait` over guessing `Sleep`.** `Sleep 2s` pauses a fixed time and is\n  fine for short, predictable output. But for *real programs* whose timing varies, fixed\n  sleeps are fragile — too short and you capture a half-finished screen, too long and the\n  GIF drags. Use `Wait+Screen \u002Fregex\u002F` to block until matching text appears on screen, or\n  `Wait+Line \u002Fregex\u002F` for the current line. Plain `Wait` waits for the shell prompt. This\n  makes recordings robust regardless of how fast the machine is.\n- **`Hide` \u002F `Show`** run commands without recording them — use for `cd`, `clear`, exports,\n  and any setup the viewer shouldn't see. The demo starts clean.\n- **Keys**: `Enter`, `Tab`, `Space`, `Backspace`, `Up`\u002F`Down`\u002F`Left`\u002F`Right`, `Ctrl+C`,\n  `Ctrl+L`, `Escape`. Repeat with a count: `Down 3`, `Enter 2`.\n- **`Screenshot path.png`** grabs a still at that point — great for a quick visual sanity\n  check mid-development, or as the deliverable when the user wants a static image.\n\n### 4. Render\n\n```bash\nvhs file.tape\n```\n\nVHS exits non-zero on a bad tape. Always confirm the output file exists and is non-empty\nafterward (`ls -lh \u003Coutput>`). A 0-byte or missing file means the render failed even if the\ncommand looked like it ran.\n\nFor a fast iteration loop while dialing in timing, render to a single screenshot or a short\nclip first rather than re-rendering a long GIF every time.\n\n### 5. Inspect and refine\n\nYou can't \"see\" a GIF directly, but you can verify it meaningfully:\n\n- Add a `Screenshot frames\u002Fcheck.png` at a key moment and **Read the PNG** to confirm the\n  screen shows what you expect (the right output, no error, correct theme).\n- Check file size is reasonable — a multi-MB GIF for a 5-second clip usually means the\n  dimensions\u002Ffont are too large; offer MP4 instead.\n- Re-read the tape against the user's request: are all the steps there, in order, with\n  enough pause to be readable?\n\nThen show the user the path and a one-line summary of what it captures. If the user is in\na UI that can render it, the GIF will display.\n\n## Scenario playbook\n\n**Real program runs** (their own CLI\u002FTUI, `htop`, `vim`, etc.): use `Require` to assert\nthe binary exists, `Hide`\u002F`Show` for setup, and `Wait+Screen`\u002F`Wait+Line` for timing so the\ncapture survives machine-speed differences. Don't fake output — drive the actual program.\n\n**Scripted demos for docs\u002FREADMEs**: clarity beats realism. Slightly slower `TypingSpeed`,\ndeliberate `Sleep`s between steps so each is readable, a clean theme, and a window bar\n(`Set WindowBar Colorful`) look professional embedded in a README.\n\n**Interactive TUIs** (menus, `fzf`, full-screen apps): drive navigation with arrow keys,\n`Tab`, `Enter`. Give the app a `Sleep` to finish its initial render before interacting, and\nuse `Wait+Screen \u002F…\u002F` keyed to text the TUI draws when ready. End with the key that exits\ncleanly (often `q`, `Ctrl+C`, or `Escape`) so the final frame isn't a stuck screen.\n\n**Multi-format output**: one tape can emit several files — list multiple `Output` lines with\ndifferent extensions (`.gif`, `.mp4`, `.webp`, `.ascii`). Recommend MP4\u002FWebM for anything\nlonger than a few seconds or with lots of motion; GIFs balloon in size fast.\n\n## Gotchas\n\n- `vhs validate file.tape` checks syntax without rendering — run it before the full render to\n  catch typos cheaply.\n- `vhs new demo.tape` scaffolds a starter tape if you want a quick template.\n- Long GIFs get huge. Keep demos tight, or switch format. Dimensions and font size drive size\n  more than duration.\n- `Set` commands must come before the commands they affect (ideally all at the top).\n- If a real program needs a TTY or specific env, set it with `Env KEY value` and `Set Shell`.\n",{"name":5,"description":7},"main","3ac632ac167bd480d8b07868b7001fc52e2a402c",".claude\u002Fskills\u002Fterminal-gif",0,"https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown","https:\u002F\u002Fgithub.com\u002FJasperHG90","https:\u002F\u002Fjasperhg90.github.io\u002F","Data Engineer @ Xebia Data. I am interested in data analysis, history, politics, education, policy making and writing. ","2026-09-21 04:18:57",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JasperHG90\u002Fshakedown --skill terminal-gif",{"tool":39,"command":40},"bunx","bunx skills add JasperHG90\u002Fshakedown --skill terminal-gif",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JasperHG90\u002Fshakedown --skill terminal-gif","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fterminal-gif\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"evals\u002Fevals.json","REFERENCE","参考文档",2127,"https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fterminal-gif\u002Fevals\u002Fevals.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fvhs-tape.md",6522,"https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fterminal-gif\u002Freferences\u002Fvhs-tape.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fcheck_deps.sh","SCRIPT","脚本",1437,"https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fterminal-gif\u002Fscripts\u002Fcheck_deps.sh",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7AAFD8Q4CRZ5V34GB5655FX","fake-skill","A skill used only by shakedown's own offline tests.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Ftests\u002Ffake\u002Fskill\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7AAFB03PDQMX0DY841ADDR9","shakedown-canary","Run the shakedown canary check. Use whenever someone asks to run the canary check, verify the harness, or confirm shakedown is wired up correctly.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fsrc\u002Fshakedown\u002Fcanary\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AAF55DP6C2XSF7N23STFP3","create-cases","Author a shakedown cases file (`shakedowns\u002F\u003Cslug>.cases.toml`) for an existing agent skill: read the skill, turn what it promises into cases, supply fixtures for the commands it must not really run, and check the result with `shakedown case validate`. Use this whenever someone wants to measure, smoke-test, or add conformance cases for a skill, asks \"how do I test this skill\", points at a SKILL.md and wants cases written, or is editing a `.cases.toml`. Use it even when they only name the skill (\"write cases for connect-agent-to-hub\") without mentioning shakedown or TOML.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-cases\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AAEXCDG258QRVSSFQV0MV9","analyze-results","Read a shakedown report (`shakedown-report.json`) and say which file to open: the measured skill's own `SKILL.md`, the `shakedowns\u002F\u003Cslug>.cases.toml` holding its cases, the harness block in `shakedown.toml`, or a flag on the run itself. Use this whenever someone has run `shakedown case run` and wants to know what a number means or what to do about it, pastes a report or the PR comment rendered from one, asks why `skill_fired`, `tool_used`, `artifact_created` or `inputs_resolved` came out low, asks whether a rate is worth acting on, or says a conformance run failed and they cannot tell whose fault it is. Use it even when they only quote the percentage (\"my skill scores 60% on inputs_resolved, now what\") without naming shakedown or the report file.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fskills\u002Fanalyze-results\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7AAEMM68JP8A128WHMTJJTX","add-harness","Add a new agent harness (opencode, Gemini CLI, Codex, Amp, a local Ollama-backed runner, or any CLI that loads skills) to a shakedown config so its skill conformance can be measured, and diagnose a harness that `shakedown doctor` reports as not qualifying. Use this whenever someone wants shakedown to run against a harness it does not yet support, asks why a harness fails doctor, asks how to point an existing harness at a different model or provider, or is editing the `[harness.*]` block of a shakedown.toml. Use it even when they only name the tool (\"can this test opencode?\") without mentioning config or TOML.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fskills\u002Fadd-harness\u002FSKILL.md",[],[],{"skillNo":100,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7AAEEKJAS0KAJRM74K7FEFJ","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fplugins\u002Fopencode\u002Fskills\u002Fcreate-cases\u002FSKILL.md",[],[]]