[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TSPE2ERVCQZWPYP21W49G":3,"skill-same:01M75TSPE2ERVCQZWPYP21W49G":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75TSPE2ERVCQZWPYP21W49G","luna-upgrade",null,"Use when checking or upgrading one luna-second-brain vault to the current himmel template.","yotamleo-org\u002FHimmel","yotamleo-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F344898079?v=4","01M75TKGRE629BDM7G461ABVZP","01M75TKGS2GVCFR1A28MBMK997",15,"MIT","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fmarketplace\u002Fplugins\u002Fobsidian-triage\u002Fskills\u002Fluna-upgrade\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: luna-upgrade\ndescription: Use when checking or upgrading one luna-second-brain vault to the current himmel template.\n---\n\n# luna-upgrade — content-preserving vault\u002Ftemplate upgrade\n\nYou bring an EXISTING luna-second-brain vault up to the current himmel template\nwithout clobbering the user's own content. Vaults are scaffolded once and never\nre-read the template; this is the upgrade path. The engine that does all the\nwork is `templates\u002Fluna-second-brain\u002Fscripts\u002Fupgrade.sh` — this skill is the\nergonomic **dry-run → confirm → apply** surface around it. ALL classification,\n3-way merge, conflict handling, and fail-closed recovery logic lives in\n`upgrade.sh`; this runbook only orchestrates the preview\u002Fconfirm\u002Fapply sequence\nand surfaces the engine's output. Do NOT reimplement any merge logic here.\n\n## Invocation surfaces\n\n- **User prompt:** `\u002Fluna-upgrade [--vault \u003Cpath>] [--template-dir \u003Cpath>]` —\n  handled by the thin wrapper at `.claude\u002Fcommands\u002Fluna-upgrade.md` which\n  delegates here.\n- **Programmatic Skill-tool dispatch (no headless\n  claude):** `Skill { skill: \"obsidian-triage:luna-upgrade\", args: \"\u003Cflags...>\" }`.\n\nWherever this document references `$ARGUMENTS`, treat it as the literal arg\nstring supplied via either path.\n\n## Inputs\n\n`$ARGUMENTS` is `[--check] [--vault \u003Cpath>] [--template-dir \u003Cpath>]` (all optional).\n\n- `--check` — report whether an upgrade is available and stop (no plan, no\n  confirm, no changes). See \"Check-only mode\" below.\n- `--vault \u003Cpath>` — the vault to upgrade. Default: resolve from the current\n  session (see Step 1).\n- `--template-dir \u003Cpath>` — explicit himmel template root override. Default:\n  resolve the himmel checkout (see Step 0). The engine's own resolver order is\n  `--template-dir` > `$HIMMEL_DIR` > generic `$HOME`-relative candidate paths >\n  sibling scan, so on a normal layout you pass neither flag.\n\n## Check-only mode (`--check`)\n\nWhen `--check` is in `$ARGUMENTS`, do Steps 0 and 1 (locate himmel + the vault),\nthen run the engine in check mode and surface its single-line result verbatim —\ndo NOT run the dry-run\u002Fconfirm\u002Fapply sequence:\n\n```bash\nbash \"$UPGRADE\" --template-dir \"$TEMPLATE\" --vault-dir \"$VAULT\" --check\n```\n\nIt prints either `luna-second-brain: template vX.Y.Z available …` (an upgrade\nexists — tell the operator they can run `\u002Fluna-upgrade` to apply it) or\n`luna-second-brain: vault is current …`. It changes nothing and exits 0. STOP\nafter surfacing the line.\n\n## Step 0 — Locate himmel's upgrade.sh\n\nA vault scaffolded BEFORE this feature has no `scripts\u002Fupgrade.sh` of its own\nyet, so always invoke **himmel's** copy (the first upgrade then installs\n`upgrade.sh` into the vault — it is overwrite-class). Resolve the himmel\ncheckout the same way the engine resolves the template (explicit config wins,\nthen generic home-relative candidates):\n\n```bash\nHIMMEL=\"\"\nfor d in \"${HIMMEL_DIR:-}\" \"$HOME\u002Fgithub\u002Fhimmel\" \"$HOME\u002Fgithub\u002FHimmel\" \\\n         \"$HOME\u002FDocuments\u002Fgithub\u002Fhimmel\" \"$HOME\u002FDocuments\u002Fgithub\u002FHimmel\"; do\n  [ -n \"$d\" ] && [ -f \"$d\u002Ftemplates\u002Fluna-second-brain\u002Fscripts\u002Fupgrade.sh\" ] \\\n    && { HIMMEL=\"$d\"; break; }\ndone\n```\n\nIf `--template-dir \u003Cpath>` was passed, set `HIMMEL` so that\n`$HIMMEL\u002Ftemplates\u002Fluna-second-brain` equals that path (or pass the flag\nstraight through). If `HIMMEL` stays empty, stop and tell the operator to set\n`HIMMEL_DIR` or pass `--template-dir` — do NOT guess a path. Define:\n\n```bash\nTEMPLATE=\"$HIMMEL\u002Ftemplates\u002Fluna-second-brain\"\nUPGRADE=\"$TEMPLATE\u002Fscripts\u002Fupgrade.sh\"\n```\n\nThis probe is best-effort and only locates `upgrade.sh`; the engine re-resolves\nand re-validates the template itself (and warns if multiple checkouts match), so\nthe engine's resolution is authoritative — do not treat this snippet's result as\nfinal.\n\n## Step 1 — Resolve the vault root\n\nIf `--vault \u003Cpath>` was passed, use it. Otherwise resolve the current session's\nvault: walk up from `$PWD` to the nearest ancestor that contains a `.obsidian\u002F`\ndirectory or a `.vault-template.json` stamp; if none is found, use `$PWD`.\nConfirm the resolved `$VAULT` looks like a vault (it has `.obsidian\u002F` or\n`.vault-template.json`); if it clearly is not one, stop and ask the operator to\npass `--vault`.\n\n## Step 2 — Dry-run (preview)\n\nRun the engine in preview mode — it touches nothing:\n\n```bash\nbash \"$UPGRADE\" --template-dir \"$TEMPLATE\" --vault-dir \"$VAULT\" --dry-run\n```\n\n## Step 3 — Surface the plan\n\nShow the operator the engine's plan output verbatim (which files WRITE \u002F\nWRITE-NEW \u002F MERGE-JSON \u002F MERGE-3WAY \u002F REPORT, and the template-vs-vault\nversions). Call out explicitly if the plan includes:\n- a `MERGE-3WAY _CLAUDE.md` line (their operating manual may merge or conflict), or\n- a changed `.obsidian\u002FPLUGINS-SETUP.md` (the manual-install list reprints on apply).\n\nIf the dry-run reports the vault is already current (exit 0, \"already current\"),\nsay so and STOP — nothing to do.\n\n## Step 4 — Confirm\n\nAsk the operator to confirm they want to apply this plan to `$VAULT`. Wait for\nan explicit yes. If they decline, STOP — make no changes.\n\n## Step 5 — Apply\n\nOn confirmation, re-run the engine with `--yes` (same resolution, no prompt):\n\n```bash\nbash \"$UPGRADE\" --template-dir \"$TEMPLATE\" --vault-dir \"$VAULT\" --yes\n```\n\n## Step 6 — Surface the result\n\nReport the engine's outcome, preserving its loud signals:\n- **Success (exit 0):** \"Upgrade complete — vault is now vX.Y.Z.\"\n- **`_CLAUDE.md` conflict \u002F write failure (non-zero exit):** the engine did NOT\n  write the version stamp (fail-closed) and printed the reason. Surface that\n  loud alert verbatim — on a `_CLAUDE.md` conflict the original is kept and the\n  conflicted 3-way merge is in `_CLAUDE.md.template-merge`; the operator\n  resolves it by hand, deletes the sidecar, and re-runs (writes are idempotent).\n- **PLUGINS-SETUP reprint:** if the engine reprinted the manual-install table,\n  pass it through so the operator can install\u002Fupdate the AGPL\u002Fproprietary\n  plugins (Charts, Templater, …) that cannot be bundled.\n\nDo NOT attempt to resolve a conflict or re-run automatically — the\ncontent-preserving contract is the engine's; your job is to surface its result.\n\n## Step 7 — Offer to commit (single-writer vaults only)\n\n`upgrade.sh` writes template files but never commits — and the vault's\n`vault-autosync.sh` is opt-in (default OFF) and wired to no trigger, so a fresh\nupgrade leaves a dirty working tree that silently never lands (the \"N uncommitted\nchanges after \u002Fluna-upgrade\" surprise). On a **successful apply (exit 0)**, close\nthat gap:\n\n```bash\n# only if the vault commits straight to main by design AND has pending changes\n[ -f \"$VAULT\u002F.single-writer\" ] && [ -n \"$(git -C \"$VAULT\" status --porcelain)\" ] && echo offer\n```\n\nIf both hold, OFFER to commit (operator confirms — do not auto-commit):\n\n```bash\ngit -C \"$VAULT\" add -A && git -C \"$VAULT\" commit -m \"chore: luna vault upgrade → template vX.Y.Z\"\n```\n\nIf the vault is not single-writer (no `.single-writer`), do NOT offer — those\nvaults gate vault writes through a PR lane; just tell the operator the upgrade\nleft uncommitted changes to review. (`\u002Fhimmel-doctor` C3 is the standing backstop\nthat flags a dirty single-writer vault later.)\n\n## Exit codes (from the engine)\n\n- `0` — applied (or dry-run completed, or already current).\n- `1` — a partial upgrade: write failure or `_CLAUDE.md` conflict — stamp NOT\n  written, re-run after resolving.\n- `3` — needs reconcile: every other file was applied, but local edits were\n  withheld (no write failure) — stamp NOT written. Stdout carries one stable\n  `upgrade: NEEDS-RECONCILE — …` line. Reconcile each withheld file: take the\n  template copy, or re-run with `--keep \u003Crel>` (repeatable) to\n  explicitly keep the vault's content — this records which template version\n  the decision was made against, so a later run that finds the template\n  unchanged for that file does not re-prompt, but a later run where the\n  template changes it again does. Then re-run. A run that also has a write\n  failure or `_CLAUDE.md` conflict is still `1`.\n- `2` — env\u002Fusage error (e.g. template not located, vault dir missing, unknown\n  flag, unreadable marketplace.json, missing python3\u002Fgit\u002Fsha256sum). On \"could\n  not locate the himmel template\", set `HIMMEL_DIR` or pass `--template-dir`.\n\n## Notes\n\n- The build of this skill was autonomous; its USE is interactive (the confirm\n  in Step 4 is the load-bearing safety gate).\n- Never edit user content. The engine only ever enumerates template-owned files;\n  this skill never writes vault files directly.\n","# luna-upgrade — content-preserving vault\u002Ftemplate upgrade\n\nYou bring an EXISTING luna-second-brain vault up to the current himmel template\nwithout clobbering the user's own content. Vaults are scaffolded once and never\nre-read the template; this is the upgrade path. The engine that does all the\nwork is `templates\u002Fluna-second-brain\u002Fscripts\u002Fupgrade.sh` — this skill is the\nergonomic **dry-run → confirm → apply** surface around it. ALL classification,\n3-way merge, conflict handling, and fail-closed recovery logic lives in\n`upgrade.sh`; this runbook only orchestrates the preview\u002Fconfirm\u002Fapply sequence\nand surfaces the engine's output. Do NOT reimplement any merge logic here.\n\n## Invocation surfaces\n\n- **User prompt:** `\u002Fluna-upgrade [--vault \u003Cpath>] [--template-dir \u003Cpath>]` —\n  handled by the thin wrapper at `.claude\u002Fcommands\u002Fluna-upgrade.md` which\n  delegates here.\n- **Programmatic Skill-tool dispatch (no headless\n  claude):** `Skill { skill: \"obsidian-triage:luna-upgrade\", args: \"\u003Cflags...>\" }`.\n\nWherever this document references `$ARGUMENTS`, treat it as the literal arg\nstring supplied via either path.\n\n## Inputs\n\n`$ARGUMENTS` is `[--check] [--vault \u003Cpath>] [--template-dir \u003Cpath>]` (all optional).\n\n- `--check` — report whether an upgrade is available and stop (no plan, no\n  confirm, no changes). See \"Check-only mode\" below.\n- `--vault \u003Cpath>` — the vault to upgrade. Default: resolve from the current\n  session (see Step 1).\n- `--template-dir \u003Cpath>` — explicit himmel template root override. Default:\n  resolve the himmel checkout (see Step 0). The engine's own resolver order is\n  `--template-dir` > `$HIMMEL_DIR` > generic `$HOME`-relative candidate paths >\n  sibling scan, so on a normal layout you pass neither flag.\n\n## Check-only mode (`--check`)\n\nWhen `--check` is in `$ARGUMENTS`, do Steps 0 and 1 (locate himmel + the vault),\nthen run the engine in check mode and surface its single-line result verbatim —\ndo NOT run the dry-run\u002Fconfirm\u002Fapply sequence:\n\n```bash\nbash \"$UPGRADE\" --template-dir \"$TEMPLATE\" --vault-dir \"$VAULT\" --check\n```\n\nIt prints either `luna-second-brain: template vX.Y.Z available …` (an upgrade\nexists — tell the operator they can run `\u002Fluna-upgrade` to apply it) or\n`luna-second-brain: vault is current …`. It changes nothing and exits 0. STOP\nafter surfacing the line.\n\n## Step 0 — Locate himmel's upgrade.sh\n\nA vault scaffolded BEFORE this feature has no `scripts\u002Fupgrade.sh` of its own\nyet, so always invoke **himmel's** copy (the first upgrade then installs\n`upgrade.sh` into the vault — it is overwrite-class). Resolve the himmel\ncheckout the same way the engine resolves the template (explicit config wins,\nthen generic home-relative candidates):\n\n```bash\nHIMMEL=\"\"\nfor d in \"${HIMMEL_DIR:-}\" \"$HOME\u002Fgithub\u002Fhimmel\" \"$HOME\u002Fgithub\u002FHimmel\" \\\n         \"$HOME\u002FDocuments\u002Fgithub\u002Fhimmel\" \"$HOME\u002FDocuments\u002Fgithub\u002FHimmel\"; do\n  [ -n \"$d\" ] && [ -f \"$d\u002Ftemplates\u002Fluna-second-brain\u002Fscripts\u002Fupgrade.sh\" ] \\\n    && { HIMMEL=\"$d\"; break; }\ndone\n```\n\nIf `--template-dir \u003Cpath>` was passed, set `HIMMEL` so that\n`$HIMMEL\u002Ftemplates\u002Fluna-second-brain` equals that path (or pass the flag\nstraight through). If `HIMMEL` stays empty, stop and tell the operator to set\n`HIMMEL_DIR` or pass `--template-dir` — do NOT guess a path. Define:\n\n```bash\nTEMPLATE=\"$HIMMEL\u002Ftemplates\u002Fluna-second-brain\"\nUPGRADE=\"$TEMPLATE\u002Fscripts\u002Fupgrade.sh\"\n```\n\nThis probe is best-effort and only locates `upgrade.sh`; the engine re-resolves\nand re-validates the template itself (and warns if multiple checkouts match), so\nthe engine's resolution is authoritative — do not treat this snippet's result as\nfinal.\n\n## Step 1 — Resolve the vault root\n\nIf `--vault \u003Cpath>` was passed, use it. Otherwise resolve the current session's\nvault: walk up from `$PWD` to the nearest ancestor that contains a `.obsidian\u002F`\ndirectory or a `.vault-template.json` stamp; if none is found, use `$PWD`.\nConfirm the resolved `$VAULT` looks like a vault (it has `.obsidian\u002F` or\n`.vault-template.json`); if it clearly is not one, stop and ask the operator to\npass `--vault`.\n\n## Step 2 — Dry-run (preview)\n\nRun the engine in preview mode — it touches nothing:\n\n```bash\nbash \"$UPGRADE\" --template-dir \"$TEMPLATE\" --vault-dir \"$VAULT\" --dry-run\n```\n\n## Step 3 — Surface the plan\n\nShow the operator the engine's plan output verbatim (which files WRITE \u002F\nWRITE-NEW \u002F MERGE-JSON \u002F MERGE-3WAY \u002F REPORT, and the template-vs-vault\nversions). Call out explicitly if the plan includes:\n- a `MERGE-3WAY _CLAUDE.md` line (their operating manual may merge or conflict), or\n- a changed `.obsidian\u002FPLUGINS-SETUP.md` (the manual-install list reprints on apply).\n\nIf the dry-run reports the vault is already current (exit 0, \"already current\"),\nsay so and STOP — nothing to do.\n\n## Step 4 — Confirm\n\nAsk the operator to confirm they want to apply this plan to `$VAULT`. Wait for\nan explicit yes. If they decline, STOP — make no changes.\n\n## Step 5 — Apply\n\nOn confirmation, re-run the engine with `--yes` (same resolution, no prompt):\n\n```bash\nbash \"$UPGRADE\" --template-dir \"$TEMPLATE\" --vault-dir \"$VAULT\" --yes\n```\n\n## Step 6 — Surface the result\n\nReport the engine's outcome, preserving its loud signals:\n- **Success (exit 0):** \"Upgrade complete — vault is now vX.Y.Z.\"\n- **`_CLAUDE.md` conflict \u002F write failure (non-zero exit):** the engine did NOT\n  write the version stamp (fail-closed) and printed the reason. Surface that\n  loud alert verbatim — on a `_CLAUDE.md` conflict the original is kept and the\n  conflicted 3-way merge is in `_CLAUDE.md.template-merge`; the operator\n  resolves it by hand, deletes the sidecar, and re-runs (writes are idempotent).\n- **PLUGINS-SETUP reprint:** if the engine reprinted the manual-install table,\n  pass it through so the operator can install\u002Fupdate the AGPL\u002Fproprietary\n  plugins (Charts, Templater, …) that cannot be bundled.\n\nDo NOT attempt to resolve a conflict or re-run automatically — the\ncontent-preserving contract is the engine's; your job is to surface its result.\n\n## Step 7 — Offer to commit (single-writer vaults only)\n\n`upgrade.sh` writes template files but never commits — and the vault's\n`vault-autosync.sh` is opt-in (default OFF) and wired to no trigger, so a fresh\nupgrade leaves a dirty working tree that silently never lands (the \"N uncommitted\nchanges after \u002Fluna-upgrade\" surprise). On a **successful apply (exit 0)**, close\nthat gap:\n\n```bash\n# only if the vault commits straight to main by design AND has pending changes\n[ -f \"$VAULT\u002F.single-writer\" ] && [ -n \"$(git -C \"$VAULT\" status --porcelain)\" ] && echo offer\n```\n\nIf both hold, OFFER to commit (operator confirms — do not auto-commit):\n\n```bash\ngit -C \"$VAULT\" add -A && git -C \"$VAULT\" commit -m \"chore: luna vault upgrade → template vX.Y.Z\"\n```\n\nIf the vault is not single-writer (no `.single-writer`), do NOT offer — those\nvaults gate vault writes through a PR lane; just tell the operator the upgrade\nleft uncommitted changes to review. (`\u002Fhimmel-doctor` C3 is the standing backstop\nthat flags a dirty single-writer vault later.)\n\n## Exit codes (from the engine)\n\n- `0` — applied (or dry-run completed, or already current).\n- `1` — a partial upgrade: write failure or `_CLAUDE.md` conflict — stamp NOT\n  written, re-run after resolving.\n- `3` — needs reconcile: every other file was applied, but local edits were\n  withheld (no write failure) — stamp NOT written. Stdout carries one stable\n  `upgrade: NEEDS-RECONCILE — …` line. Reconcile each withheld file: take the\n  template copy, or re-run with `--keep \u003Crel>` (repeatable) to\n  explicitly keep the vault's content — this records which template version\n  the decision was made against, so a later run that finds the template\n  unchanged for that file does not re-prompt, but a later run where the\n  template changes it again does. Then re-run. A run that also has a write\n  failure or `_CLAUDE.md` conflict is still `1`.\n- `2` — env\u002Fusage error (e.g. template not located, vault dir missing, unknown\n  flag, unreadable marketplace.json, missing python3\u002Fgit\u002Fsha256sum). On \"could\n  not locate the himmel template\", set `HIMMEL_DIR` or pass `--template-dir`.\n\n## Notes\n\n- The build of this skill was autonomous; its USE is interactive (the confirm\n  in Step 4 is the load-bearing safety gate).\n- Never edit user content. The engine only ever enumerates template-owned files;\n  this skill never writes vault files directly.\n",{"name":5,"description":7},"main","2a00f5c1203047a27ae79f5626e1ae4d34f03c79","marketplace\u002Fplugins\u002Fobsidian-triage\u002Fskills\u002Fluna-upgrade",2,"https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel","https:\u002F\u002Fyotamleo-org.github.io\u002FHimmel\u002F","https:\u002F\u002Fgithub.com\u002Fyotamleo-org","2026-11-15 05:10:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add yotamleo-org\u002FHimmel --skill luna-upgrade",{"tool":37,"command":38},"bunx","bunx skills add yotamleo-org\u002FHimmel --skill luna-upgrade",{"tool":40,"command":41},"pnpm","pnpm dlx skills add yotamleo-org\u002FHimmel --skill luna-upgrade","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fmarketplace\u002Fplugins\u002Fobsidian-triage\u002Fskills\u002Fluna-upgrade\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M75TY3C1HJV3PACB8R2FTAX7","medic","Use inside a Salus medical vault to FILE a medical item into its structured place (skin photo → photo archive + capture note; lesion\u002Fsymptom note; lab\u002FPDF → 00-Sources) and auto-commit, OR to QUERY the vault for a health follow-up (grounded answer + flagged, non-diagnostic morphology read). Triggers on \"file this photo \u002F note \u002F lab\", \"log this into the medical vault\", \"ask the medic\", or any health follow-up while cwd = the medical vault. Organize & surface only — never diagnose (posture-A).","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Ftemplates\u002Fluna-second-brain\u002F_profiles\u002Fsalus\u002F.claude\u002Fskills\u002Fmedic\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75TY1AV2E5DECQFSGZ01FQ3","stuck-playbook","fixture skill, invoked in the basic transcript fixture","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Ftool-usage\u002Fskills\u002F.claude\u002Fskills\u002Fstuck-playbook\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75TY05TH00N1KX4H0W1AASQ","never-used-skill","fixture skill, never invoked in any fixture transcript","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Ftool-usage\u002Fskills-config\u002Fskills\u002Fnever-used-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M75TXV4XKHHV36JKHPXK0QAN","used-skill","fixture skill invoked via a Skill tool_use in the fixture transcript","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Fdead-parts\u002Fbasic-repo\u002F.claude\u002Fskills\u002Fused-skill\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75TXJYNA5BQWC5WWZN4HY95","dead-skill","fixture skill never invoked and never referenced","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Fdead-parts\u002Fbasic-repo\u002F.claude\u002Fskills\u002Fdead-skill\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75TXAB3RCTMWB02GEKDT17Q","jira-transition","Move\u002Ftransition a Jira issue status (\"move PROJ-46 to In Progress\"). Needs key + target status. Not PR status changes.","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fplugins\u002Fhimmel-jira\u002Fskills\u002Fjira-transition\u002FSKILL.md",[],[]]