[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M748FBTJSP0C46BAF8C2KCFS":3,"skill-same:01M748FBTJSP0C46BAF8C2KCFS":52},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M748FBTJSP0C46BAF8C2KCFS","akm-migrate",null,"Use when upgrading to akm-cli 0.9.7 through 0.9.14, covering removed improve strategies, packed curation, lint repair, scheduler reconciliation, and the critical 0.9.14 index-v23 compatibility boundary.","itlackey\u002Fakm-eval","itlackey","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6414031?v=4","01M6D08NHES2CPRGY5HCPJECD6","IT Lackey","01M71W0ZJQ3686SNJSCQZM3X4E",0,"MPL-2.0","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fnightly\u002Fassets\u002Flibrary\u002Fskills\u002Fakm-migrate\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\ntype: skill\nname: akm-migrate\ndescription: Use when upgrading to akm-cli 0.9.7 through 0.9.14, covering\n  removed improve strategies, packed curation, lint repair, scheduler\n  reconciliation, and the critical 0.9.14 index-v23 compatibility boundary.\nupdated: 2026-08-31\nwhen_to_use: Use when upgrading akm-cli to versions 0.9.7 through 0.9.14 and\n  needing to handle migration tasks, index schema changes, or strategy\n  deprecations.\ngenerated:\n  by: akm\u002F0.9.12\n  at: 2026-09-07T07:15:22.405Z\nverified:\n  - by: akm\u002F0.9.12\n    at: 2026-09-07T07:15:22.405Z\n---\n\n# AKM Migration Guide (0.9.7 – 0.9.14)\n\nUse this guide after upgrading the executable to a version between 0.9.7 and 0.9.14. From 0.9.6 there is no required source rewrite, database migration, or index rebuild for the base 0.9.7 release. The reviewable work involves checking removed improve strategy names, newly visible lint findings, and any old scheduler rows that previous releases could not reconcile. If the previous install predates 0.9.6, complete the conditional legacy actions in section 6 as well. If upgrading to 0.9.14 or later, you must also address the index-v23 compatibility boundary described in section 9. `akm migrate` remains task-source specific — it is not a general config or database migrator.\n\n## 1. Confirm the release and protect active work\n\n```bash\nakm --version\nakm info\nakm workflow list --active\n```\n\nIf the previous install predates 0.9.2, also read `akm help migrate 0.9.2`. That is the built-in durable-plan\u002Ftask-source cutover note; no separate `akm help migrate 0.9.7` page is shipped.\n\nWorkflow plans remain at `irVersion: 5` and `hashVersion: 7` in 0.9.7. A plan frozen before the 0.9.2 cutover is readable but cannot resume or advance. Inspect and restart it from current authored source:\n\n```bash\nakm workflow status \u003Crun-id>\nakm workflow abandon \u003Crun-id>\nakm workflow run \u003Cworkflow-ref>\n```\n\nDo not downgrade below 0.9.2 after the state database has received current task-history rows. The 0.9.7 upgrade adds no new task-history vocabulary.\n\n## 2. Review newly enforced reference integrity\n\nRun a report-only lint first:\n\n```bash\nakm lint\n```\n\n0.9.7 now validates legacy `type:slug` xrefs and resolves `\u003Cname>.derived.md` memories. A belief edge to a memory archived by AKM's prune flow resolves through its tombstone and is not an error. A `supersededBy` or `contradictedBy` target with neither a live file nor a tombstone is genuinely dangling. Repair those only after reviewing the plain lint report:\n\n```bash\nakm lint --prune-dangling-edges\n```\n\nThis flag is deliberately separate from `--fix`: dropping an edge removes a belief-graph assertion. It does not prune ordinary `xrefs`. If the last edge on a channel is removed, review any `beliefState` that still names that channel.\n\nA corrupt derived `index.db` now deletes and rebuilds itself on open, including its WAL\u002FSHM sidecars. Do not apply that recovery logic to `state.db`, which is durable and is never automatically removed.\n\n## 3. Migrate task sources and reconcile scheduler state\n\nTask source v4 remains the authored grammar. AKM 0.9.7 auto-reads a deterministically convertible v2\u002Fv3 source as v4 in memory, emits a one-line deprecation warning, and does not rewrite it. Use the migrator to make the upgrade durable and silence that warning:\n\n```bash\nakm migrate status\nakm migrate apply --dry-run\nakm migrate apply\n```\n\nEach source is reported as `changed`, `skipped`, or `blocked`. A blocked file does not stop convertible siblings from migrating; repair it instead of inventing a force flag. The command has no `--config`, `--diff`, storage, or restore interface.\n\nPreview scheduler reconciliation before applying it. 0.9.7 recognizes pre-0.9.2 crontab rows that lack `--scheduler-context`, so the first sync may finally update rows that had been stuck behind an install collision. It also accepts a truly immutable package-local AKM launcher; writable project or `npx` installs remain ineligible:\n\n```bash\nakm task sync --dry-run\nakm task sync\nakm task doctor\n```\n\nThen inspect unreachable scheduler entries. `prune` defaults to a zero-write preview and never targets an entry that still resolves to a live bundle:\n\n```bash\nakm task prune\nakm task prune --id \u003Cbinding-id>     # optional narrowed preview\nakm task prune --yes                 # remove the printed orphan candidates\n```\n\nIf a v2\u002Fv3 source cannot convert, `TASK_SCHEMA_VERSION_UNSUPPORTED` now names the blocking reason. A human decision is required; rerunning `migrate apply` without changing the source does not bypass it.\n\n## 4. Replace removed improve strategies\n\nThe built-in strategy set is now `default`, `quick`, `thorough`, `graph-refresh`, `consolidate`, `catchup`, `reflect-distill`, and `proactive-maintenance`. `frequent` and `memory-focus` were removed. Find them in config, task sources, and automation:\n\n```bash\nrg -n 'frequent|memory-focus' ~\u002F.config\u002Fakm \"$(akm info --format json | jq -r .bundleDir)\"\n```\n\nUse `reflect-distill` for the shipped hourly learning-pass behavior. For memory-only work, define an explicit custom strategy instead of relying on the removed `memory-focus` preset. A user strategy still named `frequent` or `memory-focus` now merges over `default`, not the former built-in, so make every relied-on process and sync value explicit.\n\n`thorough` and `catchup` now use judged promotion with caps (25 and 100 accepts respectively, `maxDiffLines: 200`). The autonomy gate demotes promotion back to queue mode unless `experimental.improveAutonomy` is enabled, so the default remains review-only.\n\n## 5. Adopt the new read and source features\n\nUse `curate --pack \u003Ctokens>` when the caller needs the selected local assets' content immediately:\n\n```bash\nakm curate \"\u003Ctask>\" --limit 5 --pack 8000 --format json\n```\n\nThe budget applies to the combined result. AKM drops lower-ranked whole assets first and truncates only when the highest-ranked asset alone exceeds the budget. Registry hits are never packed. A `ref#fragment` packs only that section through the same resolution path as `akm show`.\n\nWhen `akm bundle add` receives an origin-root website URL, 0.9.7 probes `\u002Fllms.txt` and uses its same-origin links as the crawl frontier when available. Specific-page URLs and sites without `llms.txt` keep the existing crawl behavior; off-origin manifest entries are ignored.\n\n## 6. Complete conditional pre-0.9.6 work\n\nIf the previous install predates 0.9.5, rebuild the index once because old search impressions inflated stored utility scores:\n\n```bash\nakm index --full\n```\n\nThat rebuild also repopulates embeddings with token-budgeted batches. If the install already ran the 0.9.6 migration, no full rebuild is required for 0.9.7.\n\nKnown older `configVersion` documents are upgraded in memory with a warning; the next `akm config set` or other config write persists the current version. The 0.9.1-era `extraParams.reasoning_effort`, `temperature`, `maxTokens`, and `enableThinking` workarounds are likewise lifted to their first-class engine fields when unambiguous. Conflicting old\u002Fnew values still fail closed — choose one value explicitly rather than relying on precedence.\n\nSearch consumers may now see additive `matchStage: \"exact\" | \"prefix\" | \"relaxed\"` on normal\u002Ffull and agent-shaped local hits. It is absent for pure-semantic contributions and registry hits. A `searchMode` of `fts-fallback` means semantic search was attempted live and lexical results were returned with a sanitized warning.\n\nTask-history `target.kind` is unchanged from 0.9.2: `command`, `shell`, `script`, `workflow`, or `unknown`. Consumers must not branch on the retired `prompt` value.\n\n## 7. Verify authored workflows and tasks\n\nEvery task lives at `tasks\u002F\u003Cid>.yml`, begins with `version: 4`, selects exactly one target (`uses:` or `run:`), and may omit `schedule:` for manual-only use. `with:` is valid only for `uses: akm\u002Fcommand`; `enabled` belongs to each schedule binding. Validate resolution without executing:\n\n```bash\nakm task explain tasks\u002F\u003Cid>\nakm workflow plan workflows\u002F\u003Cname>\nakm lint --type workflows\n```\n\nThe workflow source contract and durable plan versions did not change between 0.9.2 and 0.9.7.\n\n## 8. Scan and complete the upgrade\n\n```bash\nBUNDLE_DIR=\"$(akm info --format json | jq -r .bundleDir)\"\n\nrg -n --glob '*.md' --glob '*.yml' \\\n  'akm (vault|reflect|distill|extract|tasks|add|list|remove|update|save|events|wiki|propose|proposals|accept|reject|diff|revert)\\b|--auto-accept|--profile |--strategy (frequent|memory-focus)\\b|\\b(?:skill|knowledge|memory|workflow|command|agent|script|env|secret|lesson|task|vault|wiki):[A-Za-z0-9_\u002F-]+' \\\n  \"$BUNDLE_DIR\"\n\nfind \"$BUNDLE_DIR\u002Ftasks\" -name '*.md' -print\nrg -L '^version: 4$' \"$BUNDLE_DIR\u002Ftasks\" -g '*.yml'\n\nakm lint\nakm task sync --dry-run\nakm task doctor\nakm health --format json\n```\n\nTreat a `plugin-version` advisory as actionable: update a stale Claude plugin, or install one whose declared range admits 0.9.7 if `admitted` is false.\n\n## 9. Handle the 0.9.14 index-v23 compatibility boundary\n\nIf you are upgrading to 0.9.14 or later, the search index schema changes to v23. This is a breaking change for the local index file. Unlike the 0.9.7 changes which were additive or in-memory, index-v23 requires a physical rebuild of the index database to ensure compatibility with the new query engine and embedding storage format.\n\n1.  **Check current index version:**\n    ```bash\n    akm index status\n    ```\n    If the reported version is less than 23, a rebuild is mandatory before search functionality will work correctly.\n\n2.  **Rebuild the index:**\n    ```bash\n    akm index --full\n    ```\n    This command will discard the old index structure and rebuild it from the current asset store. This process may take longer than a standard incremental update, especially for large bundles with many embedded assets.\n\n3.  **Verify search integrity:**\n    After the rebuild, run a sample search to ensure results are returned and that `matchStage` and `searchMode` fields are populated as expected in the JSON output.\n    ```bash\n    akm search \"test query\" --format json\n    ```\n\n    If the index was not rebuilt, searches may return empty results or throw schema mismatch errors. Do not attempt to manually edit the `index.db` file; always use the `akm index` command to manage schema transitions.\n\n## Completion checklist\n\n- Removed improve strategy names are absent or backed by explicit custom strategy definitions.\n- A full index rebuild completed if (and only if) the prior migration required the pre-0.9.5 score reset OR if upgrading to 0.9.14+ (index-v23).\n- `akm migrate apply --dry-run` reports no unexplained legacy task sources.\n- Every executable task passes `akm task explain`; scheduler reconciliation and prune previews contain only understood changes.\n- Each workflow passes `akm workflow plan` and `akm lint --type workflows`.\n- `akm lint` and `akm health --format json` have no unexplained failures or plugin compatibility warnings.\n- Packed-curate CLI consumers expect a bare JSON array of `{ ref, tokens, content }` items (or concatenated `## \u003Cref>` sections in text mode); ordinary curate\u002Fsearch and task-history consumers retain their existing contracts.\n- If on 0.9.14+, `akm index status` reports version 23 and search queries return valid results.\n","# AKM Migration Guide (0.9.7 – 0.9.14)\n\nUse this guide after upgrading the executable to a version between 0.9.7 and 0.9.14. From 0.9.6 there is no required source rewrite, database migration, or index rebuild for the base 0.9.7 release. The reviewable work involves checking removed improve strategy names, newly visible lint findings, and any old scheduler rows that previous releases could not reconcile. If the previous install predates 0.9.6, complete the conditional legacy actions in section 6 as well. If upgrading to 0.9.14 or later, you must also address the index-v23 compatibility boundary described in section 9. `akm migrate` remains task-source specific — it is not a general config or database migrator.\n\n## 1. Confirm the release and protect active work\n\n```bash\nakm --version\nakm info\nakm workflow list --active\n```\n\nIf the previous install predates 0.9.2, also read `akm help migrate 0.9.2`. That is the built-in durable-plan\u002Ftask-source cutover note; no separate `akm help migrate 0.9.7` page is shipped.\n\nWorkflow plans remain at `irVersion: 5` and `hashVersion: 7` in 0.9.7. A plan frozen before the 0.9.2 cutover is readable but cannot resume or advance. Inspect and restart it from current authored source:\n\n```bash\nakm workflow status \u003Crun-id>\nakm workflow abandon \u003Crun-id>\nakm workflow run \u003Cworkflow-ref>\n```\n\nDo not downgrade below 0.9.2 after the state database has received current task-history rows. The 0.9.7 upgrade adds no new task-history vocabulary.\n\n## 2. Review newly enforced reference integrity\n\nRun a report-only lint first:\n\n```bash\nakm lint\n```\n\n0.9.7 now validates legacy `type:slug` xrefs and resolves `\u003Cname>.derived.md` memories. A belief edge to a memory archived by AKM's prune flow resolves through its tombstone and is not an error. A `supersededBy` or `contradictedBy` target with neither a live file nor a tombstone is genuinely dangling. Repair those only after reviewing the plain lint report:\n\n```bash\nakm lint --prune-dangling-edges\n```\n\nThis flag is deliberately separate from `--fix`: dropping an edge removes a belief-graph assertion. It does not prune ordinary `xrefs`. If the last edge on a channel is removed, review any `beliefState` that still names that channel.\n\nA corrupt derived `index.db` now deletes and rebuilds itself on open, including its WAL\u002FSHM sidecars. Do not apply that recovery logic to `state.db`, which is durable and is never automatically removed.\n\n## 3. Migrate task sources and reconcile scheduler state\n\nTask source v4 remains the authored grammar. AKM 0.9.7 auto-reads a deterministically convertible v2\u002Fv3 source as v4 in memory, emits a one-line deprecation warning, and does not rewrite it. Use the migrator to make the upgrade durable and silence that warning:\n\n```bash\nakm migrate status\nakm migrate apply --dry-run\nakm migrate apply\n```\n\nEach source is reported as `changed`, `skipped`, or `blocked`. A blocked file does not stop convertible siblings from migrating; repair it instead of inventing a force flag. The command has no `--config`, `--diff`, storage, or restore interface.\n\nPreview scheduler reconciliation before applying it. 0.9.7 recognizes pre-0.9.2 crontab rows that lack `--scheduler-context`, so the first sync may finally update rows that had been stuck behind an install collision. It also accepts a truly immutable package-local AKM launcher; writable project or `npx` installs remain ineligible:\n\n```bash\nakm task sync --dry-run\nakm task sync\nakm task doctor\n```\n\nThen inspect unreachable scheduler entries. `prune` defaults to a zero-write preview and never targets an entry that still resolves to a live bundle:\n\n```bash\nakm task prune\nakm task prune --id \u003Cbinding-id>     # optional narrowed preview\nakm task prune --yes                 # remove the printed orphan candidates\n```\n\nIf a v2\u002Fv3 source cannot convert, `TASK_SCHEMA_VERSION_UNSUPPORTED` now names the blocking reason. A human decision is required; rerunning `migrate apply` without changing the source does not bypass it.\n\n## 4. Replace removed improve strategies\n\nThe built-in strategy set is now `default`, `quick`, `thorough`, `graph-refresh`, `consolidate`, `catchup`, `reflect-distill`, and `proactive-maintenance`. `frequent` and `memory-focus` were removed. Find them in config, task sources, and automation:\n\n```bash\nrg -n 'frequent|memory-focus' ~\u002F.config\u002Fakm \"$(akm info --format json | jq -r .bundleDir)\"\n```\n\nUse `reflect-distill` for the shipped hourly learning-pass behavior. For memory-only work, define an explicit custom strategy instead of relying on the removed `memory-focus` preset. A user strategy still named `frequent` or `memory-focus` now merges over `default`, not the former built-in, so make every relied-on process and sync value explicit.\n\n`thorough` and `catchup` now use judged promotion with caps (25 and 100 accepts respectively, `maxDiffLines: 200`). The autonomy gate demotes promotion back to queue mode unless `experimental.improveAutonomy` is enabled, so the default remains review-only.\n\n## 5. Adopt the new read and source features\n\nUse `curate --pack \u003Ctokens>` when the caller needs the selected local assets' content immediately:\n\n```bash\nakm curate \"\u003Ctask>\" --limit 5 --pack 8000 --format json\n```\n\nThe budget applies to the combined result. AKM drops lower-ranked whole assets first and truncates only when the highest-ranked asset alone exceeds the budget. Registry hits are never packed. A `ref#fragment` packs only that section through the same resolution path as `akm show`.\n\nWhen `akm bundle add` receives an origin-root website URL, 0.9.7 probes `\u002Fllms.txt` and uses its same-origin links as the crawl frontier when available. Specific-page URLs and sites without `llms.txt` keep the existing crawl behavior; off-origin manifest entries are ignored.\n\n## 6. Complete conditional pre-0.9.6 work\n\nIf the previous install predates 0.9.5, rebuild the index once because old search impressions inflated stored utility scores:\n\n```bash\nakm index --full\n```\n\nThat rebuild also repopulates embeddings with token-budgeted batches. If the install already ran the 0.9.6 migration, no full rebuild is required for 0.9.7.\n\nKnown older `configVersion` documents are upgraded in memory with a warning; the next `akm config set` or other config write persists the current version. The 0.9.1-era `extraParams.reasoning_effort`, `temperature`, `maxTokens`, and `enableThinking` workarounds are likewise lifted to their first-class engine fields when unambiguous. Conflicting old\u002Fnew values still fail closed — choose one value explicitly rather than relying on precedence.\n\nSearch consumers may now see additive `matchStage: \"exact\" | \"prefix\" | \"relaxed\"` on normal\u002Ffull and agent-shaped local hits. It is absent for pure-semantic contributions and registry hits. A `searchMode` of `fts-fallback` means semantic search was attempted live and lexical results were returned with a sanitized warning.\n\nTask-history `target.kind` is unchanged from 0.9.2: `command`, `shell`, `script`, `workflow`, or `unknown`. Consumers must not branch on the retired `prompt` value.\n\n## 7. Verify authored workflows and tasks\n\nEvery task lives at `tasks\u002F\u003Cid>.yml`, begins with `version: 4`, selects exactly one target (`uses:` or `run:`), and may omit `schedule:` for manual-only use. `with:` is valid only for `uses: akm\u002Fcommand`; `enabled` belongs to each schedule binding. Validate resolution without executing:\n\n```bash\nakm task explain tasks\u002F\u003Cid>\nakm workflow plan workflows\u002F\u003Cname>\nakm lint --type workflows\n```\n\nThe workflow source contract and durable plan versions did not change between 0.9.2 and 0.9.7.\n\n## 8. Scan and complete the upgrade\n\n```bash\nBUNDLE_DIR=\"$(akm info --format json | jq -r .bundleDir)\"\n\nrg -n --glob '*.md' --glob '*.yml' \\\n  'akm (vault|reflect|distill|extract|tasks|add|list|remove|update|save|events|wiki|propose|proposals|accept|reject|diff|revert)\\b|--auto-accept|--profile |--strategy (frequent|memory-focus)\\b|\\b(?:skill|knowledge|memory|workflow|command|agent|script|env|secret|lesson|task|vault|wiki):[A-Za-z0-9_\u002F-]+' \\\n  \"$BUNDLE_DIR\"\n\nfind \"$BUNDLE_DIR\u002Ftasks\" -name '*.md' -print\nrg -L '^version: 4$' \"$BUNDLE_DIR\u002Ftasks\" -g '*.yml'\n\nakm lint\nakm task sync --dry-run\nakm task doctor\nakm health --format json\n```\n\nTreat a `plugin-version` advisory as actionable: update a stale Claude plugin, or install one whose declared range admits 0.9.7 if `admitted` is false.\n\n## 9. Handle the 0.9.14 index-v23 compatibility boundary\n\nIf you are upgrading to 0.9.14 or later, the search index schema changes to v23. This is a breaking change for the local index file. Unlike the 0.9.7 changes which were additive or in-memory, index-v23 requires a physical rebuild of the index database to ensure compatibility with the new query engine and embedding storage format.\n\n1.  **Check current index version:**\n    ```bash\n    akm index status\n    ```\n    If the reported version is less than 23, a rebuild is mandatory before search functionality will work correctly.\n\n2.  **Rebuild the index:**\n    ```bash\n    akm index --full\n    ```\n    This command will discard the old index structure and rebuild it from the current asset store. This process may take longer than a standard incremental update, especially for large bundles with many embedded assets.\n\n3.  **Verify search integrity:**\n    After the rebuild, run a sample search to ensure results are returned and that `matchStage` and `searchMode` fields are populated as expected in the JSON output.\n    ```bash\n    akm search \"test query\" --format json\n    ```\n\n    If the index was not rebuilt, searches may return empty results or throw schema mismatch errors. Do not attempt to manually edit the `index.db` file; always use the `akm index` command to manage schema transitions.\n\n## Completion checklist\n\n- Removed improve strategy names are absent or backed by explicit custom strategy definitions.\n- A full index rebuild completed if (and only if) the prior migration required the pre-0.9.5 score reset OR if upgrading to 0.9.14+ (index-v23).\n- `akm migrate apply --dry-run` reports no unexplained legacy task sources.\n- Every executable task passes `akm task explain`; scheduler reconciliation and prune previews contain only understood changes.\n- Each workflow passes `akm workflow plan` and `akm lint --type workflows`.\n- `akm lint` and `akm health --format json` have no unexplained failures or plugin compatibility warnings.\n- Packed-curate CLI consumers expect a bare JSON array of `{ ref, tokens, content }` items (or concatenated `## \u003Cref>` sections in text mode); ordinary curate\u002Fsearch and task-history consumers retain their existing contracts.\n- If on 0.9.14+, `akm index status` reports version 23 and search queries return valid results.\n",{"name":5,"type":24,"updated":25,"verified":26,"generated":30,"description":7,"when_to_use":31},"skill",1788134400000,[27],{"at":28,"by":29},1788765322405,"akm\u002F0.9.12",{"at":28,"by":29},"Use when upgrading akm-cli to versions 0.9.7 through 0.9.14 and needing to handle migration tasks, index schema changes, or strategy deprecations.","main","b293a8475fcbb20683373dc9735a2ecf0ca7889d","evals\u002Fnightly\u002Fassets\u002Flibrary\u002Fskills\u002Fakm-migrate","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval","https:\u002F\u002Fgithub.com\u002Fitlackey","2026-11-13 11:49:12",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add itlackey\u002Fakm-eval --skill akm-migrate",{"tool":44,"command":45},"bunx","bunx skills add itlackey\u002Fakm-eval --skill akm-migrate",{"tool":47,"command":48},"pnpm","pnpm dlx skills add itlackey\u002Fakm-eval --skill akm-migrate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fnightly\u002Fassets\u002Flibrary\u002Fskills\u002Fakm-migrate\u002FSKILL.md",true,[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M748G6310YQEN9SEY8E69V7F","tax-filing-checklist","Walk through the steps and documents needed to file an individual federal income tax return","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Ftax-filing-checklist\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M748G3C1CSMBM33KP2CCK7TB","patient-vitals-charting","Record patient vital signs consistently and flag values outside the normal reference range","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fpatient-vitals-charting\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M748G05H68QFB8YVQKDHF66B","pasta-from-scratch","Make fresh egg pasta dough from scratch, roll it, and cut it into shapes","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fpasta-from-scratch\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M748FXAQVJRX98HP8STRTD9P","knife-sharpening","Sharpen and hone kitchen knives to keep an edge safe and effective","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fknife-sharpening\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M748FTJEZ0P6BXNERTHZ9KB3","first-aid-response","Respond to a first aid emergency using a scene-safety-first, ABC-based (airway, breathing, circulation) approach","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Ffirst-aid-response\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M748FQESZPA3ZW5SWKJNKMD0","contract-review-basics","Review a contract draft for missing terms, ambiguous language, and risky clauses before signing","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fcontract-review-basics\u002FSKILL.md",[],[]]