[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWM2FN212E3P1SPNEH1TX9":3,"skill-same:01M7AWM2FN212E3P1SPNEH1TX9":72},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M7AWM2FN212E3P1SPNEH1TX9","printing-press-import",null,"Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for \u002Fprinting-press-polish or \u002Fprinting-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken\u002Flost internal copy. Trigger phrases: \"import the CLI\", \"bring it into my library\", \"fetch from public library\", \"I don't have it locally yet\".","barkleesanders\u002Fclaude-code-starter","barkleesanders","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F30680901?v=4","01M7AW019CGBYWDA8MFJEN1JXC","Barklee Sanders","01M7AW01A5H994ASJ2QZPW67AV",4,"MIT","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fprinting-press-import\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: printing-press-import\ndescription: >\n  Bring a published CLI from the public library into the internal library\n  so it's identical to a freshly-generated copy — module path reverted,\n  manuscripts placed alongside, ready for \u002Fprinting-press-polish or\n  \u002Fprinting-press-emboss. Use when the public library has a CLI you\n  don't have locally, or to recover from a broken\u002Flost internal copy.\n  Trigger phrases: \"import the CLI\", \"bring it into my library\",\n  \"fetch from public library\", \"I don't have it locally yet\".\nallowed-tools:\n  - Bash\n  - Read\n  - Glob\n  - Grep\n  - AskUserQuestion\n---\n\n# \u002Fprinting-press-import\n\nBring a published CLI from the public library\n([`mvanhorn\u002Fprinting-press-library`](https:\u002F\u002Fgithub.com\u002Fmvanhorn\u002Fprinting-press-library))\ninto the internal library at `$PRESS_LIBRARY\u002F` so it matches\nthe form the generator would produce. Manuscripts ride along.\n\n```bash\n\u002Fprinting-press-import notion\n\u002Fprinting-press-import cal.com\n\u002Fprinting-press-import allrecipes --from-clone ~\u002FCode\u002Fprinting-press-library\n```\n\nThe internal library is the working copy; the public library is the\ndurable artifact. After import, the CLI is ready for polish, emboss, or\nre-publish — the publish step will re-apply the module path rewrites.\n\n## When to run\n\n- The public library has a CLI you don't have locally\n- The internal copy is broken, lost, or out of sync\n- You want a clean baseline before running polish on a published CLI\n\nIf the user is asking to polish a CLI and mentions \"in\u002Ffrom the public\nlibrary\" or \"from the repo\", suggest running this skill first.\n\n## Setup\n\n```bash\nPRESS_HOME=\"${PRINTING_PRESS_HOME:-$HOME\u002Fprinting-press}\"\nPRESS_LIBRARY=\"$PRESS_HOME\u002Flibrary\"\nPRESS_MANUSCRIPTS=\"$PRESS_HOME\u002Fmanuscripts\"\nSCRIPTS_DIR=\"$(dirname \"${BASH_SOURCE[0]:-\\$0}\")\u002Freferences\"\n```\n\nThe four reference scripts live alongside this SKILL.md under\n`references\u002F`:\n\n- `import-fetch.sh \u003Clibrary-path> \u003Cstaging> [--clone \u003Cpath>]`\n- `import-backup.sh \u003Capi-slug>` (prints zip path on stdout)\n- `import-rewrite.sh \u003Cstaging> \u003Capi-slug>`\n- `import-place.sh \u003Cstaging> \u003Capi-slug>`\n\n## Phase 1 — Resolve the CLI\n\nThe argument can be anything natural: an API slug (`notion`), a brand\nname (`cal.com`), an old CLI name (`notion-pp-cli`), or close enough\n(`Allrecipes`). Resolve via the public library's `registry.json` —\nwhich carries `name`, `category`, `api`, `description`, and `path` for\nevery entry, in one fetch.\n\n```bash\nREGISTRY=$(mktemp)\ngh api -H \"Accept: application\u002Fvnd.github.v3.raw\" \\\n  repos\u002Fmvanhorn\u002Fprinting-press-library\u002Fcontents\u002Fregistry.json \\\n  > \"$REGISTRY\"\n```\n\nMatch in this order:\n\n1. **Exact `name` match** — `jq --arg q \"$ARG\" '.entries[] | select(.name == $q)' \"$REGISTRY\"`\n2. **Normalized exact** — strip `-pp-cli` suffix, lowercase, dot→hyphen, then exact match\n3. **Substring on `name` or `description`** — case-insensitive contains\n\n```bash\n# Exact:\njq --arg q \"$ARG\" '.entries[] | select(.name == $q)' \"$REGISTRY\"\n\n# Normalized exact (after $ARG2 = lowercase, dot→hyphen, suffix-stripped):\njq --arg q \"$ARG2\" '.entries[] | select(.name == $q)' \"$REGISTRY\"\n\n# Fuzzy (substring on name or description):\njq --arg q \"$ARG2\" '.entries[]\n  | select((.name | ascii_downcase | contains($q | ascii_downcase))\n        or (.description | ascii_downcase | contains($q | ascii_downcase)))\n' \"$REGISTRY\"\n```\n\nIf you get one match: use it. If multiple: present at most 4 to the user\nvia `AskUserQuestion` showing `name` + `description` per candidate. If\nzero: tell the user the public library doesn't have that CLI.\n\nThe matched entry gives you everything you need:\n- `LIB_PATH` from `.path` (e.g., `library\u002Fproductivity\u002Fcal-com`)\n- `API_SLUG` from `.name`\n- `CATEGORY` from `.category`\n\n**Don't slurp whole files** when reasoning over candidates. The fields\nabove are enough; if you genuinely need more, the per-CLI manifest is\njust `\u003CLIB_PATH>\u002Fmanifest.json` and the description there can be pulled\nthe same way (`gh api -H \"Accept: ... raw\" ...\u002Fmanifest.json | jq -r '.description'`).\n\n## Phase 2 — Decide on overwrite\n\nCheck whether the internal library already has this CLI:\n\n```bash\nLIB_TARGET=\"$PRESS_LIBRARY\u002F$API_SLUG\"\nMAN_TARGET=\"$PRESS_MANUSCRIPTS\u002F$API_SLUG\"\n```\n\n**If neither exists:** straightforward import — proceed to Phase 3.\n\n**If either exists:** read provenance from both sides to decide whether\nto overwrite. Don't read whole `.printing-press.json` files — pull just\nthe fields that matter:\n\n```bash\n# Internal provenance (if present):\njq '{run_id, generated_at, printing_press_version, spec_checksum}' \\\n  \"$LIB_TARGET\u002F.printing-press.json\" 2>\u002Fdev\u002Fnull\n\n# Public provenance (one-shot via raw):\ngh api -H \"Accept: application\u002Fvnd.github.v3.raw\" \\\n  repos\u002Fmvanhorn\u002Fprinting-press-library\u002Fcontents\u002F$LIB_PATH\u002F.printing-press.json \\\n  | jq '{run_id, generated_at, printing_press_version, spec_checksum}'\n```\n\nReason over the diff:\n\n- **Same `run_id`** — public is the same generation as internal. Likely\n  no-op; ask before clobbering. If the user wants to import anyway\n  (e.g., to recover from a broken internal copy), proceed.\n- **Public newer `generated_at`** — public has changes the internal\n  doesn't. Importing is the safe move; ask the user to confirm.\n- **Internal newer `generated_at`** — internal has work the public\n  doesn't (in-progress polish, manual fixes). Importing would clobber\n  that. Stop and surface this to the user — they likely want to publish\n  the internal changes first.\n- **Either side missing `.printing-press.json`** — older or hand-imported.\n  Ask the user.\n\nWhen the user confirms overwrite, the backup step in Phase 3 captures\nthe current internal state.\n\n## Phase 3 — Import\n\n```bash\nSTAGING=$(mktemp -d)\n\n# Fetch (remote unless --from-clone was passed)\nif [[ -n \"${CLONE_PATH:-}\" ]]; then\n  bash \"$SCRIPTS_DIR\u002Fimport-fetch.sh\" \"$LIB_PATH\" \"$STAGING\" --clone \"$CLONE_PATH\"\nelse\n  bash \"$SCRIPTS_DIR\u002Fimport-fetch.sh\" \"$LIB_PATH\" \"$STAGING\"\nfi\n\n# Backup if anything is being clobbered. Prints zip path on stdout.\nif [[ -d \"$LIB_TARGET\" || -d \"$MAN_TARGET\" ]]; then\n  BACKUP_ZIP=$(bash \"$SCRIPTS_DIR\u002Fimport-backup.sh\" \"$API_SLUG\")\n  echo \"Backed up to: $BACKUP_ZIP\"\nfi\n\n# Reverse the publish-step module path rewrites.\nbash \"$SCRIPTS_DIR\u002Fimport-rewrite.sh\" \"$STAGING\" \"$API_SLUG\"\n\n# Atomically move staging into place.\nbash \"$SCRIPTS_DIR\u002Fimport-place.sh\" \"$STAGING\" \"$API_SLUG\"\n```\n\n## Phase 4 — Verify internal consistency\n\nAfter the move, confirm the imported CLI builds and is structurally\nintact. Treat any failure as a real problem — don't paper over it.\n\n```bash\ncd \"$LIB_TARGET\"\n\n# Module path is local form\ngrep -q \"^module ${API_SLUG}-pp-cli\\$\" go.mod \\\n  || { echo \"FAIL: go.mod still on public module path\"; exit 1; }\n\n# No public module path leaked into source\nif grep -rq \"github.com\u002Fmvanhorn\u002Fprinting-press-library\u002Flibrary\" \\\n   --include='*.go' --include='*.yaml' --include='*.yml' .; then\n  echo \"FAIL: source still references public module path\"\n  exit 1\nfi\n\n# Build\ngo build .\u002F... \\\n  || { echo \"FAIL: go build\"; exit 1; }\n\n# Doctor (self-check)\nmake doctor 2>\u002Fdev\u002Fnull \\\n  || .\u002Fbin\u002F${API_SLUG}-pp-cli doctor 2>\u002Fdev\u002Fnull \\\n  || true   # best-effort; not all CLIs have doctor wired the same way\n```\n\nReport the import outcome:\n\n- Source path (from registry: `\u003Ccategory>\u002F\u003Capi-slug>`)\n- Run ID (from `.printing-press.json`)\n- Manuscripts run-ids placed (count + names)\n- Backup zip path (if any)\n- Build status\n\n## Polish-side hint\n\nIf the user's request to import was triggered by a polish ask (e.g.,\nthey said \"polish notion in the public library\"), suggest:\n\n```\nImported $API_SLUG. To polish: \u002Fprinting-press-polish $API_SLUG\n```\n\nThe polish skill operates on the internal library, so import-then-polish\nis the right flow when starting from a published CLI.\n","# \u002Fprinting-press-import\n\nBring a published CLI from the public library\n([`mvanhorn\u002Fprinting-press-library`](https:\u002F\u002Fgithub.com\u002Fmvanhorn\u002Fprinting-press-library))\ninto the internal library at `$PRESS_LIBRARY\u002F` so it matches\nthe form the generator would produce. Manuscripts ride along.\n\n```bash\n\u002Fprinting-press-import notion\n\u002Fprinting-press-import cal.com\n\u002Fprinting-press-import allrecipes --from-clone ~\u002FCode\u002Fprinting-press-library\n```\n\nThe internal library is the working copy; the public library is the\ndurable artifact. After import, the CLI is ready for polish, emboss, or\nre-publish — the publish step will re-apply the module path rewrites.\n\n## When to run\n\n- The public library has a CLI you don't have locally\n- The internal copy is broken, lost, or out of sync\n- You want a clean baseline before running polish on a published CLI\n\nIf the user is asking to polish a CLI and mentions \"in\u002Ffrom the public\nlibrary\" or \"from the repo\", suggest running this skill first.\n\n## Setup\n\n```bash\nPRESS_HOME=\"${PRINTING_PRESS_HOME:-$HOME\u002Fprinting-press}\"\nPRESS_LIBRARY=\"$PRESS_HOME\u002Flibrary\"\nPRESS_MANUSCRIPTS=\"$PRESS_HOME\u002Fmanuscripts\"\nSCRIPTS_DIR=\"$(dirname \"${BASH_SOURCE[0]:-\\$0}\")\u002Freferences\"\n```\n\nThe four reference scripts live alongside this SKILL.md under\n`references\u002F`:\n\n- `import-fetch.sh \u003Clibrary-path> \u003Cstaging> [--clone \u003Cpath>]`\n- `import-backup.sh \u003Capi-slug>` (prints zip path on stdout)\n- `import-rewrite.sh \u003Cstaging> \u003Capi-slug>`\n- `import-place.sh \u003Cstaging> \u003Capi-slug>`\n\n## Phase 1 — Resolve the CLI\n\nThe argument can be anything natural: an API slug (`notion`), a brand\nname (`cal.com`), an old CLI name (`notion-pp-cli`), or close enough\n(`Allrecipes`). Resolve via the public library's `registry.json` —\nwhich carries `name`, `category`, `api`, `description`, and `path` for\nevery entry, in one fetch.\n\n```bash\nREGISTRY=$(mktemp)\ngh api -H \"Accept: application\u002Fvnd.github.v3.raw\" \\\n  repos\u002Fmvanhorn\u002Fprinting-press-library\u002Fcontents\u002Fregistry.json \\\n  > \"$REGISTRY\"\n```\n\nMatch in this order:\n\n1. **Exact `name` match** — `jq --arg q \"$ARG\" '.entries[] | select(.name == $q)' \"$REGISTRY\"`\n2. **Normalized exact** — strip `-pp-cli` suffix, lowercase, dot→hyphen, then exact match\n3. **Substring on `name` or `description`** — case-insensitive contains\n\n```bash\n# Exact:\njq --arg q \"$ARG\" '.entries[] | select(.name == $q)' \"$REGISTRY\"\n\n# Normalized exact (after $ARG2 = lowercase, dot→hyphen, suffix-stripped):\njq --arg q \"$ARG2\" '.entries[] | select(.name == $q)' \"$REGISTRY\"\n\n# Fuzzy (substring on name or description):\njq --arg q \"$ARG2\" '.entries[]\n  | select((.name | ascii_downcase | contains($q | ascii_downcase))\n        or (.description | ascii_downcase | contains($q | ascii_downcase)))\n' \"$REGISTRY\"\n```\n\nIf you get one match: use it. If multiple: present at most 4 to the user\nvia `AskUserQuestion` showing `name` + `description` per candidate. If\nzero: tell the user the public library doesn't have that CLI.\n\nThe matched entry gives you everything you need:\n- `LIB_PATH` from `.path` (e.g., `library\u002Fproductivity\u002Fcal-com`)\n- `API_SLUG` from `.name`\n- `CATEGORY` from `.category`\n\n**Don't slurp whole files** when reasoning over candidates. The fields\nabove are enough; if you genuinely need more, the per-CLI manifest is\njust `\u003CLIB_PATH>\u002Fmanifest.json` and the description there can be pulled\nthe same way (`gh api -H \"Accept: ... raw\" ...\u002Fmanifest.json | jq -r '.description'`).\n\n## Phase 2 — Decide on overwrite\n\nCheck whether the internal library already has this CLI:\n\n```bash\nLIB_TARGET=\"$PRESS_LIBRARY\u002F$API_SLUG\"\nMAN_TARGET=\"$PRESS_MANUSCRIPTS\u002F$API_SLUG\"\n```\n\n**If neither exists:** straightforward import — proceed to Phase 3.\n\n**If either exists:** read provenance from both sides to decide whether\nto overwrite. Don't read whole `.printing-press.json` files — pull just\nthe fields that matter:\n\n```bash\n# Internal provenance (if present):\njq '{run_id, generated_at, printing_press_version, spec_checksum}' \\\n  \"$LIB_TARGET\u002F.printing-press.json\" 2>\u002Fdev\u002Fnull\n\n# Public provenance (one-shot via raw):\ngh api -H \"Accept: application\u002Fvnd.github.v3.raw\" \\\n  repos\u002Fmvanhorn\u002Fprinting-press-library\u002Fcontents\u002F$LIB_PATH\u002F.printing-press.json \\\n  | jq '{run_id, generated_at, printing_press_version, spec_checksum}'\n```\n\nReason over the diff:\n\n- **Same `run_id`** — public is the same generation as internal. Likely\n  no-op; ask before clobbering. If the user wants to import anyway\n  (e.g., to recover from a broken internal copy), proceed.\n- **Public newer `generated_at`** — public has changes the internal\n  doesn't. Importing is the safe move; ask the user to confirm.\n- **Internal newer `generated_at`** — internal has work the public\n  doesn't (in-progress polish, manual fixes). Importing would clobber\n  that. Stop and surface this to the user — they likely want to publish\n  the internal changes first.\n- **Either side missing `.printing-press.json`** — older or hand-imported.\n  Ask the user.\n\nWhen the user confirms overwrite, the backup step in Phase 3 captures\nthe current internal state.\n\n## Phase 3 — Import\n\n```bash\nSTAGING=$(mktemp -d)\n\n# Fetch (remote unless --from-clone was passed)\nif [[ -n \"${CLONE_PATH:-}\" ]]; then\n  bash \"$SCRIPTS_DIR\u002Fimport-fetch.sh\" \"$LIB_PATH\" \"$STAGING\" --clone \"$CLONE_PATH\"\nelse\n  bash \"$SCRIPTS_DIR\u002Fimport-fetch.sh\" \"$LIB_PATH\" \"$STAGING\"\nfi\n\n# Backup if anything is being clobbered. Prints zip path on stdout.\nif [[ -d \"$LIB_TARGET\" || -d \"$MAN_TARGET\" ]]; then\n  BACKUP_ZIP=$(bash \"$SCRIPTS_DIR\u002Fimport-backup.sh\" \"$API_SLUG\")\n  echo \"Backed up to: $BACKUP_ZIP\"\nfi\n\n# Reverse the publish-step module path rewrites.\nbash \"$SCRIPTS_DIR\u002Fimport-rewrite.sh\" \"$STAGING\" \"$API_SLUG\"\n\n# Atomically move staging into place.\nbash \"$SCRIPTS_DIR\u002Fimport-place.sh\" \"$STAGING\" \"$API_SLUG\"\n```\n\n## Phase 4 — Verify internal consistency\n\nAfter the move, confirm the imported CLI builds and is structurally\nintact. Treat any failure as a real problem — don't paper over it.\n\n```bash\ncd \"$LIB_TARGET\"\n\n# Module path is local form\ngrep -q \"^module ${API_SLUG}-pp-cli\\$\" go.mod \\\n  || { echo \"FAIL: go.mod still on public module path\"; exit 1; }\n\n# No public module path leaked into source\nif grep -rq \"github.com\u002Fmvanhorn\u002Fprinting-press-library\u002Flibrary\" \\\n   --include='*.go' --include='*.yaml' --include='*.yml' .; then\n  echo \"FAIL: source still references public module path\"\n  exit 1\nfi\n\n# Build\ngo build .\u002F... \\\n  || { echo \"FAIL: go build\"; exit 1; }\n\n# Doctor (self-check)\nmake doctor 2>\u002Fdev\u002Fnull \\\n  || .\u002Fbin\u002F${API_SLUG}-pp-cli doctor 2>\u002Fdev\u002Fnull \\\n  || true   # best-effort; not all CLIs have doctor wired the same way\n```\n\nReport the import outcome:\n\n- Source path (from registry: `\u003Ccategory>\u002F\u003Capi-slug>`)\n- Run ID (from `.printing-press.json`)\n- Manuscripts run-ids placed (count + names)\n- Backup zip path (if any)\n- Build status\n\n## Polish-side hint\n\nIf the user's request to import was triggered by a polish ask (e.g.,\nthey said \"polish notion in the public library\"), suggest:\n\n```\nImported $API_SLUG. To polish: \u002Fprinting-press-polish $API_SLUG\n```\n\nThe polish skill operates on the internal library, so import-then-polish\nis the right flow when starting from a published CLI.\n",{"name":5,"description":24,"allowed-tools":25},"Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for \u002Fprinting-press-polish or \u002Fprinting-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken\u002Flost internal copy. Trigger phrases: \"import the CLI\", \"bring it into my library\", \"fetch from public library\", \"I don't have it locally yet\".\n",[26,27,28,29,30],"Bash","Read","Glob","Grep","AskUserQuestion","main","e7b39d448c7d905feed2b044d3ccdf60822596ab","skills\u002Fprinting-press-import",0,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter","https:\u002F\u002Fgithub.com\u002Fbarkleesanders","barkleesanders.com","Stay Hungry, Stay Foolish","2026-11-06 08:47:06",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add barkleesanders\u002Fclaude-code-starter --skill printing-press-import",{"tool":46,"command":47},"bunx","bunx skills add barkleesanders\u002Fclaude-code-starter --skill printing-press-import",{"tool":49,"command":50},"pnpm","pnpm dlx skills add barkleesanders\u002Fclaude-code-starter --skill printing-press-import","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fprinting-press-import\u002FSKILL.md",true,[54,60,64,68],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fimport-backup.sh","SCRIPT","脚本",1404,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fprinting-press-import\u002Freferences\u002Fimport-backup.sh",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fimport-fetch.sh",1577,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fprinting-press-import\u002Freferences\u002Fimport-fetch.sh",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fimport-place.sh",1778,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fprinting-press-import\u002Freferences\u002Fimport-place.sh",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fimport-rewrite.sh",2114,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fprinting-press-import\u002Freferences\u002Fimport-rewrite.sh",[73,79,86,93,100,107],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AWV75B37B6YKG7ZKGZ783F","zi-search","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fzi-search\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AWTZA3JGK1T7V1HS543FG7","visualise","Render inline interactive visuals — SVG diagrams, HTML widgets, charts, and explainers — directly in the conversation. Use this skill whenever the user asks to visualize, diagram, chart, illustrate, or explain something visually, or when an explanation would genuinely benefit from a spatial\u002Finteractive diagram rather than text. Also triggers for: flowcharts, architecture diagrams, data visualizations, interactive explainers, comparison layouts, UI mockups, and any request containing 'show me', 'draw', 'map out', 'visualize', or 'diagram'. Even when the user doesn't explicitly ask for a visual, use this skill proactively when the topic has spatial, sequential, or systemic relationships that a diagram would clarify better than prose.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvisualise\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AWTR056C3P9R3VS8YVM2WX","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Runway,' 'Kling,' 'Pika,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social-content. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AWTHTWBMTYZPMHHEYX3TTG","manim-video","Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric\u002Fmathematical content.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002Fskills\u002Fmanim-video\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7AWTCXDJ9NWFQW51ENM8A2Z","video-use","Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7AWTA1D5FP895S33GHSA2G5","ui-improver","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fui-improver\u002FSKILL.md",[],[]]