[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0QJA34AECG26WDF40WSQV":3,"skill-same:01M7F0QJA34AECG26WDF40WSQV":58},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F0QJA34AECG26WDF40WSQV","spark-memory-thermal-ops",null,"Manage unified memory and thermals during long-running ML jobs on NVIDIA DGX Spark. Use when planning memory headroom for a training run on GB10, when a job OOMs on unified memory, or when monitoring temperature and power during multi-hour training.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdgx-spark-ops\u002Fskills\u002Fspark-memory-thermal-ops\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: spark-memory-thermal-ops\ndescription: Manage unified memory and thermals during long-running ML jobs on NVIDIA DGX Spark. Use when planning memory headroom for a training run on GB10, when a job OOMs on unified memory, or when monitoring temperature and power during multi-hour training.\n---\n\n# Spark Memory & Thermal Ops\n\nDGX Spark's GB10 chip has one 128GB unified\nmemory (UMA) pool shared by CPU and GPU, and a\nsustained power ceiling well below its rated\nfigure. Both break discrete-GPU assumptions:\nheadroom isn't what `nvidia-smi` reports, and a\nrun that starts fast will slow down mid-job\nwith nothing misconfigured. This skill covers\nplanning memory headroom, working an actual\nOOM, and watching thermals across a long job.\nFor launch-time failure modes (ABI mismatches,\nflash-attn, playbook breakage), see\n`spark-training-gotchas` — this skill assumes\nthe job starts.\n\n## Common Issues Quick Reference\n\n| Situation | Do this |\n|---|---|\n| Planning headroom before launch | Budget against `free -g`, not `nvidia-smi` — see UMA Memory Model |\n| Job OOMs on unified memory | Work the OOM Ladder in order: flush, then batch\u002Fpack, then method downgrade |\n| Throughput drops mid-run | Check the power\u002Ftemp log before assuming a config bug — see Thermal Monitoring |\n| Trainer + inference server both wanted | Run one at a time — see Concurrent Workloads |\n\n## When to Use This Skill\n\n- Sizing a training run against the 128GB pool\n  before launch — will this model, method, and\n  batch\u002Fpack combination fit.\n- A run OOMs mid-load or mid-step and the\n  remediation order matters — what to try first,\n  second, third.\n- Watching temperature and power during a\n  multi-hour job, deciding whether a slowdown is\n  thermal throttling or something else.\n- Planning to run a trainer alongside an\n  inference server (vLLM, Ollama) on the same box.\n\n## UMA Memory Model\n\nSpark has no separate GPU VRAM — the GPU and\nCPU share one 128GB pool. Two consequences:\n\n- **`nvidia-smi` and `cudaMemGetInfo`\n  underreport pressure — or report nothing at\n  all.** Both report CUDA-allocator-visible\n  memory, not the pool's actual state — a box can\n  show headroom in `nvidia-smi` and still OOM,\n  because page-cache and mmap'd pages the\n  allocator doesn't see consume the same pool. On\n  some driver\u002Fsetups, the memory query returns\n  `[N\u002FA], [N\u002FA]` outright instead of a number — a\n  script grepping for a numeric value there gets\n  nothing, not a misleading undercount (see\n  `spark-training-gotchas` gotcha G3).\n\n- **Model load is a transient peak, not the\n  steady state.** Loading safetensors weights\n  mmaps the file, then copies into CUDA\n  tensors — for a window during load, both the\n  mmap'd pages and the CUDA copy count against\n  the pool at once. A model that fits while\n  training can still OOM during load if headroom\n  was sized for the post-load footprint instead\n  of this doubled transient.\n\nPlan and diagnose with `free -g`, not\n`nvidia-smi`:\n\n```bash\nfree -g | awk 'NR==2 {print \"free:\", $4, \"GB\"}'\n```\n\nRule of thumb: take that free figure, subtract a\nfew GB for OS\u002Fdriver overhead, and budget against\nthe result — not the 128GB spec number.\nThe worksheet in `references\u002Fuma-accounting.md`\naccepts parameter count, dtype, and method as\ninput, and returns a memory estimate to compare\nagainst known anchors.\n\n### Planning Sequence\n\nBefore launch, work through these in order:\n\n1. Read `free -g`; subtract OS\u002Fdriver overhead\n   for the budget.\n2. Estimate weights + optimizer + gradients +\n   activations from `references\u002Fuma-accounting.md`.\n3. Compare against the closest anchor (70B\n   QLoRA, 27B LoRA, 9B full FT), not the\n   estimate alone.\n4. If the estimate is close to the budget, start\n   with shorter packing or a smaller batch —\n   cheaper than hitting the OOM Ladder mid-run.\n\n### Example: Sizing a 70B QLoRA Run\n\nA sanity check of the worksheet formula against\nthe ≈40GB anchor:\n\n```python\nparams = 70e9\nweights_gb = params * 0.5 \u002F 1e9      # NF4, step 1\nadapter_gb = 0.5                     # step 5, negligible\ntotal_gb = weights_gb + adapter_gb   # + activations\nprint(f\"{total_gb:.0f}GB before activations\")\n```\n\nWeights alone land near the ≈40GB anchor — a plan\nestimating far above that for the same model\nclass is a signal to recheck dtype and method.\n\n## The OOM Ladder\n\nWhen a job OOMs on unified memory, work this\nladder in order. Each step is more disruptive\nthan the last — don't skip ahead:\n**reducing batch size is never step 1.**\n\n1. **Flush the buffer cache.** Page cache from a\n   previous run or a large dataset read often\n   accounts for GB of the \"missing\" headroom.\n   This costs nothing but a rerun and doesn't\n   touch the job's configuration:\n\n   ```bash\n   sync; echo 3 > \u002Fproc\u002Fsys\u002Fvm\u002Fdrop_caches\n   ```\n\n   Needs root; a between-run reset, not a\n   mid-training step. See\n   `spark-training-gotchas` (gotcha G3) for the\n   full diagnostic behind this step.\n\n2. **Reduce batch size or packing length.** Only\n   after a flush fails to free enough headroom,\n   cut batch size or packing length — the first\n   step that changes what the run does. Prefer\n   packing length first; it drives activation\n   footprint more directly at long context.\n\n3. **Downgrade the method: bf16 LoRA before\n   QLoRA.** If flushing and shrinking batch\u002Fpack\n   still OOM, drop the method a tier — bf16 LoRA\n   is next, not the reverse. QLoRA's bitsandbytes\n   dequantization buffers are transient CUDA-side\n   allocations that can OOM before an equivalent\n   bf16 LoRA run would, even though QLoRA's\n   steady-state footprint is smaller. A QLoRA OOM\n   is not proof the model doesn't fit.\n\nFall back further (smaller model, multi-Spark)\nonly after all three steps and the job still\nwon't fit.\n\n## Thermal Monitoring\n\nMulti-hour runs push into Spark's sustained\npower ceiling, well under the rated figure —\nexpected platform behavior, not a symptom to\nexplain away:\n\n- Sample temperature and power alongside the\n  training logs, not after a slowdown is\n  noticed — every 30-60 seconds correlates a\n  throughput drop with a thermal event. Keep\n  the CSV output format `assets\u002Fthermal-sample.sh`\n  writes, so timestamps line up against the log:\n\n  ```bash\n  bash assets\u002Fthermal-sample.sh 30 thermal.log\n  ```\n\n- **A sustained ~100W power draw is the platform\n  cap, not a configuration bug.** Don't re-tune\n  batch size or precision to \"fix\" a plateau\n  that's the box behaving normally under load.\n  If temperature climbs while power stays flat\n  under the rated 240W figure, that's the\n  signature to recognize.\n\n- Log throttle events explicitly instead of\n  letting a run silently slow down unrecorded. A\n  run whose per-step time doubles two hours in\n  should show that in the log, correlated against\n  the thermal sample at that timestamp. Full\n  throttling diagnostics: `spark-training-gotchas`\n  (gotcha G4).\n\n## Concurrent Workloads\n\nBecause the 128GB pool is global, eviction\nhappens without either process's logs showing\nan OOM:\n\n- The one-heavy-job rule applies to **uncapped or\n  near-capacity** workloads — an uncapped trainer\n  and inference server (vLLM, Ollama) compete for\n  the same pool. A small, capped workload doesn't:\n  a \u003C4GB LoRA fine-tune coexists fine alongside\n  vLLM capped at `gpu-memory-utilization\u003C=0.5` —\n  check the other process's cap, not just its\n  presence, before stopping it.\n\n- Inference servers evict trainer pages silently\n  under uncapped\u002Fnear-capacity contention, and\n  vice versa — neither logs an error, so a slow\n  run or lost KV cache is a contention symptom to\n  check for. Stop unrelated *uncapped* servers\n  before a long or full-pool run.\n\nCheck for GPU-resident processes first:\n\n```bash\nps aux | grep -E 'vllm|ollama|trl|axolotl' | grep -v grep\n```\n\nThis procedure complements `spark-training-gotchas`\n(gotchas G3, G4, G6) — that skill covers launch-time\nfailures; this one, the running job.\n\nMemory math worksheets:\n`references\u002Fuma-accounting.md`.\n","# Spark Memory & Thermal Ops\n\nDGX Spark's GB10 chip has one 128GB unified\nmemory (UMA) pool shared by CPU and GPU, and a\nsustained power ceiling well below its rated\nfigure. Both break discrete-GPU assumptions:\nheadroom isn't what `nvidia-smi` reports, and a\nrun that starts fast will slow down mid-job\nwith nothing misconfigured. This skill covers\nplanning memory headroom, working an actual\nOOM, and watching thermals across a long job.\nFor launch-time failure modes (ABI mismatches,\nflash-attn, playbook breakage), see\n`spark-training-gotchas` — this skill assumes\nthe job starts.\n\n## Common Issues Quick Reference\n\n| Situation | Do this |\n|---|---|\n| Planning headroom before launch | Budget against `free -g`, not `nvidia-smi` — see UMA Memory Model |\n| Job OOMs on unified memory | Work the OOM Ladder in order: flush, then batch\u002Fpack, then method downgrade |\n| Throughput drops mid-run | Check the power\u002Ftemp log before assuming a config bug — see Thermal Monitoring |\n| Trainer + inference server both wanted | Run one at a time — see Concurrent Workloads |\n\n## When to Use This Skill\n\n- Sizing a training run against the 128GB pool\n  before launch — will this model, method, and\n  batch\u002Fpack combination fit.\n- A run OOMs mid-load or mid-step and the\n  remediation order matters — what to try first,\n  second, third.\n- Watching temperature and power during a\n  multi-hour job, deciding whether a slowdown is\n  thermal throttling or something else.\n- Planning to run a trainer alongside an\n  inference server (vLLM, Ollama) on the same box.\n\n## UMA Memory Model\n\nSpark has no separate GPU VRAM — the GPU and\nCPU share one 128GB pool. Two consequences:\n\n- **`nvidia-smi` and `cudaMemGetInfo`\n  underreport pressure — or report nothing at\n  all.** Both report CUDA-allocator-visible\n  memory, not the pool's actual state — a box can\n  show headroom in `nvidia-smi` and still OOM,\n  because page-cache and mmap'd pages the\n  allocator doesn't see consume the same pool. On\n  some driver\u002Fsetups, the memory query returns\n  `[N\u002FA], [N\u002FA]` outright instead of a number — a\n  script grepping for a numeric value there gets\n  nothing, not a misleading undercount (see\n  `spark-training-gotchas` gotcha G3).\n\n- **Model load is a transient peak, not the\n  steady state.** Loading safetensors weights\n  mmaps the file, then copies into CUDA\n  tensors — for a window during load, both the\n  mmap'd pages and the CUDA copy count against\n  the pool at once. A model that fits while\n  training can still OOM during load if headroom\n  was sized for the post-load footprint instead\n  of this doubled transient.\n\nPlan and diagnose with `free -g`, not\n`nvidia-smi`:\n\n```bash\nfree -g | awk 'NR==2 {print \"free:\", $4, \"GB\"}'\n```\n\nRule of thumb: take that free figure, subtract a\nfew GB for OS\u002Fdriver overhead, and budget against\nthe result — not the 128GB spec number.\nThe worksheet in `references\u002Fuma-accounting.md`\naccepts parameter count, dtype, and method as\ninput, and returns a memory estimate to compare\nagainst known anchors.\n\n### Planning Sequence\n\nBefore launch, work through these in order:\n\n1. Read `free -g`; subtract OS\u002Fdriver overhead\n   for the budget.\n2. Estimate weights + optimizer + gradients +\n   activations from `references\u002Fuma-accounting.md`.\n3. Compare against the closest anchor (70B\n   QLoRA, 27B LoRA, 9B full FT), not the\n   estimate alone.\n4. If the estimate is close to the budget, start\n   with shorter packing or a smaller batch —\n   cheaper than hitting the OOM Ladder mid-run.\n\n### Example: Sizing a 70B QLoRA Run\n\nA sanity check of the worksheet formula against\nthe ≈40GB anchor:\n\n```python\nparams = 70e9\nweights_gb = params * 0.5 \u002F 1e9      # NF4, step 1\nadapter_gb = 0.5                     # step 5, negligible\ntotal_gb = weights_gb + adapter_gb   # + activations\nprint(f\"{total_gb:.0f}GB before activations\")\n```\n\nWeights alone land near the ≈40GB anchor — a plan\nestimating far above that for the same model\nclass is a signal to recheck dtype and method.\n\n## The OOM Ladder\n\nWhen a job OOMs on unified memory, work this\nladder in order. Each step is more disruptive\nthan the last — don't skip ahead:\n**reducing batch size is never step 1.**\n\n1. **Flush the buffer cache.** Page cache from a\n   previous run or a large dataset read often\n   accounts for GB of the \"missing\" headroom.\n   This costs nothing but a rerun and doesn't\n   touch the job's configuration:\n\n   ```bash\n   sync; echo 3 > \u002Fproc\u002Fsys\u002Fvm\u002Fdrop_caches\n   ```\n\n   Needs root; a between-run reset, not a\n   mid-training step. See\n   `spark-training-gotchas` (gotcha G3) for the\n   full diagnostic behind this step.\n\n2. **Reduce batch size or packing length.** Only\n   after a flush fails to free enough headroom,\n   cut batch size or packing length — the first\n   step that changes what the run does. Prefer\n   packing length first; it drives activation\n   footprint more directly at long context.\n\n3. **Downgrade the method: bf16 LoRA before\n   QLoRA.** If flushing and shrinking batch\u002Fpack\n   still OOM, drop the method a tier — bf16 LoRA\n   is next, not the reverse. QLoRA's bitsandbytes\n   dequantization buffers are transient CUDA-side\n   allocations that can OOM before an equivalent\n   bf16 LoRA run would, even though QLoRA's\n   steady-state footprint is smaller. A QLoRA OOM\n   is not proof the model doesn't fit.\n\nFall back further (smaller model, multi-Spark)\nonly after all three steps and the job still\nwon't fit.\n\n## Thermal Monitoring\n\nMulti-hour runs push into Spark's sustained\npower ceiling, well under the rated figure —\nexpected platform behavior, not a symptom to\nexplain away:\n\n- Sample temperature and power alongside the\n  training logs, not after a slowdown is\n  noticed — every 30-60 seconds correlates a\n  throughput drop with a thermal event. Keep\n  the CSV output format `assets\u002Fthermal-sample.sh`\n  writes, so timestamps line up against the log:\n\n  ```bash\n  bash assets\u002Fthermal-sample.sh 30 thermal.log\n  ```\n\n- **A sustained ~100W power draw is the platform\n  cap, not a configuration bug.** Don't re-tune\n  batch size or precision to \"fix\" a plateau\n  that's the box behaving normally under load.\n  If temperature climbs while power stays flat\n  under the rated 240W figure, that's the\n  signature to recognize.\n\n- Log throttle events explicitly instead of\n  letting a run silently slow down unrecorded. A\n  run whose per-step time doubles two hours in\n  should show that in the log, correlated against\n  the thermal sample at that timestamp. Full\n  throttling diagnostics: `spark-training-gotchas`\n  (gotcha G4).\n\n## Concurrent Workloads\n\nBecause the 128GB pool is global, eviction\nhappens without either process's logs showing\nan OOM:\n\n- The one-heavy-job rule applies to **uncapped or\n  near-capacity** workloads — an uncapped trainer\n  and inference server (vLLM, Ollama) compete for\n  the same pool. A small, capped workload doesn't:\n  a \u003C4GB LoRA fine-tune coexists fine alongside\n  vLLM capped at `gpu-memory-utilization\u003C=0.5` —\n  check the other process's cap, not just its\n  presence, before stopping it.\n\n- Inference servers evict trainer pages silently\n  under uncapped\u002Fnear-capacity contention, and\n  vice versa — neither logs an error, so a slow\n  run or lost KV cache is a contention symptom to\n  check for. Stop unrelated *uncapped* servers\n  before a long or full-pool run.\n\nCheck for GPU-resident processes first:\n\n```bash\nps aux | grep -E 'vllm|ollama|trl|axolotl' | grep -v grep\n```\n\nThis procedure complements `spark-training-gotchas`\n(gotchas G3, G4, G6) — that skill covers launch-time\nfailures; this one, the running job.\n\nMemory math worksheets:\n`references\u002Fuma-accounting.md`.\n",{"name":5,"description":7},"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdgx-spark-ops\u002Fskills\u002Fspark-memory-thermal-ops","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill spark-memory-thermal-ops",{"tool":38,"command":39},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill spark-memory-thermal-ops",{"tool":41,"command":42},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill spark-memory-thermal-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdgx-spark-ops\u002Fskills\u002Fspark-memory-thermal-ops\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Fthermal-sample.sh","SCRIPT","脚本",1017,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdgx-spark-ops\u002Fskills\u002Fspark-memory-thermal-ops\u002Fassets\u002Fthermal-sample.sh",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fuma-accounting.md","REFERENCE","参考文档",4407,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdgx-spark-ops\u002Fskills\u002Fspark-memory-thermal-ops\u002Freferences\u002Fuma-accounting.md",[59,65,72,79,86,93],{"skillNo":60,"name":61,"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":62,"categories":63,"keywords":64,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"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},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\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},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\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},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\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},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]