[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1VHPQWXSWEW8CEWV1KBPD":3,"skill-same:01M7F1VHPQWXSWEW8CEWV1KBPD":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F1VHPQWXSWEW8CEWV1KBPD","packing-inventory",null,"Build or update the inventory of what is being carried — items, quantities, weights, carriage restrictions, and how replaceable each thing is at the destination. Use when the user is listing what they have packed or intend to pack, dictating the contents of a bag, or asking what is in their luggage. Writes inventory.yaml, which the solver and the leave-behind ranking both read.","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\u002Ftravel-packing-assistant\u002Fskills\u002Fpacking-inventory\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: packing-inventory\ndescription: Build or update the inventory of what is being carried — items, quantities, weights, carriage restrictions, and how replaceable each thing is at the destination. Use when the user is listing what they have packed or intend to pack, dictating the contents of a bag, or asking what is in their luggage. Writes inventory.yaml, which the solver and the leave-behind ranking both read.\nallowed-tools: Read, Write, Edit, Bash(uv run *), Bash(ls *), Grep, Glob\n---\n\n# Packing Inventory\n\n`$TPA` below is this plugin's `new-workspace` skill directory — the folder holding its `SKILL.md`,\n`scripts\u002F`, `schema\u002F`, `typst\u002F` and `template\u002F`. Find it by name in your tool's skills folder (some\ntools prefix it, e.g. `travel-packing-assistant__new-workspace`) and set `TPA` once per session.\n\nThe inventory is the input everything else depends on. A plan built on a half-inventory is a\nplan for a bag that does not exist.\n\nIt does not have to be complete to be useful — `\u002Ftravel-packing-assistant:weigh` reconciles the itemised\ntotal against the actual scale reading and reports the gap, so a partial inventory is honest\nrather than wrong. What it must not be is *silently* partial.\n\n## Capture modes\n\nOffer whichever fits what the user is doing right now. Do not force a mode.\n\n**Dictation.** The user talks through a bag; you write items as they go. Fastest for a bag\nalready packed. Batch back a confirmation every ten items or so rather than after each one.\n\n**Photograph.** The user lays the contents out and photographs them. Open the image, list\nwhat you can identify, and ask about anything ambiguous. Good for clothing, poor for weights —\neverything from a photo is `weight_source: estimated`.\n\n**Category sweep.** For packing not yet done: walk the categories in\n`$TPA\u002Fdata\u002Fpacking-categories.md` and ask what is going in each. Slower, but it is the only mode\nthat catches the thing they have not thought of yet.\n\n**Import.** A previous trip's `inventory.yaml` is the best starting point a repeat traveller\nhas. If the user names an earlier trip workspace, read its inventory, carry over the items and\ntheir measured weights, and ask only what changed.\n\n## Weights\n\nAsk how much of the inventory can be weighed. In descending order of usefulness:\n\n1. **Measured** — a kitchen scale, in grams. Ten minutes of weighing the heavy end of the list\n   (shoes, chargers, books, toiletries, outerwear) removes most of the uncertainty, because\n   weight distribution in luggage is strongly top-heavy: a small number of items usually\n   account for the majority of the mass.\n2. **Vendor \u002F catalogue** — a published spec weight for electronics and hardware. Usually\n   accurate, usually excludes the cable and the case, so weigh those separately.\n3. **Estimated** — from `$TPA\u002Fdata\u002Ftypical-weights.md`. Fine for socks, not for a laptop.\n\nRecord which, per item, in `weight_source`. That field is what lets `reconcile.py` tell the\ndifference between \"the inventory is missing items\" and \"the estimates are drifting\".\n\nWeigh **containers separately**: a bag's `tare_kg` and each packing cube's `tare_kg` belong in\n`bags.yaml`, not as inventory items. Double-counting an empty suitcase is the classic way to\nproduce a plan that is 4 kg pessimistic.\n\n## The fields people skip and later need\n\n- **`carriage`** — anything that cannot travel in an arbitrary bag. Power banks and spare\n  lithium batteries are cabin-only in essentially every jurisdiction; liquids over 100 ml\n  cannot go through the cabin security check; sharps, tools and some aerosols are\n  checked-only or barred. See `$TPA\u002Fdata\u002Fcarriage-rules.md`. Set `carriage_reason` every time; the\n  solver treats these as hard constraints and the reason is what the traveller reads when they\n  wonder why the plan put a heavy thing in the small bag.\n- **`tier`** — essential \u002F useful \u002F nice-to-have \u002F expendable. Assign it as you capture, not\n  later. Ranking forty items under time pressure at a check-in desk does not work; ranking\n  them at home does.\n- **`replaceable_at_destination`** — can it be bought at the other end, and roughly for how\n  much. This is the field that makes the leave-behind list sensible: a 900 g bottle of shampoo\n  that costs $4 to replace is the correct thing to abandon, and no weight-only ranking can\n  know that.\n- **`value`** — replacement cost. Used with weight to rank; also the honest answer to whether\n  something belongs in a checked bag at all.\n\n## Procedure\n\n1. Read `inventory.yaml` and `bags.yaml`. If bags are not defined yet, define them first —\n   an item cannot be assigned to a bag that does not exist.\n2. Capture in the mode the user chose. Assign stable ids (`I001`…) and never renumber; the\n   plan, the PDFs and the conversation all reference them.\n3. Fill `carriage`, `tier` and `replaceable_at_destination` as you go.\n4. Validate: `uv run $TPA\u002Fscripts\u002Fvalidate.py . --json`.\n5. Report: item count, itemised total in kg, the split by `weight_source`, and the ten heaviest\n   items. The heavy-ten list is the single most useful thing to show a traveller — it is where\n   every kilogram of headroom is going to come from.\n\n## Pinning\n\nIf the user says something must stay in a particular bag — documents in the cabin bag,\na gift that must not be crushed — set `assigned_bag` and `pinned: true`. The solver will\nplace it first and refuse to move it, and will report an error rather than quietly relocating\nit if the pin makes the pack infeasible.\n","# Packing Inventory\n\n`$TPA` below is this plugin's `new-workspace` skill directory — the folder holding its `SKILL.md`,\n`scripts\u002F`, `schema\u002F`, `typst\u002F` and `template\u002F`. Find it by name in your tool's skills folder (some\ntools prefix it, e.g. `travel-packing-assistant__new-workspace`) and set `TPA` once per session.\n\nThe inventory is the input everything else depends on. A plan built on a half-inventory is a\nplan for a bag that does not exist.\n\nIt does not have to be complete to be useful — `\u002Ftravel-packing-assistant:weigh` reconciles the itemised\ntotal against the actual scale reading and reports the gap, so a partial inventory is honest\nrather than wrong. What it must not be is *silently* partial.\n\n## Capture modes\n\nOffer whichever fits what the user is doing right now. Do not force a mode.\n\n**Dictation.** The user talks through a bag; you write items as they go. Fastest for a bag\nalready packed. Batch back a confirmation every ten items or so rather than after each one.\n\n**Photograph.** The user lays the contents out and photographs them. Open the image, list\nwhat you can identify, and ask about anything ambiguous. Good for clothing, poor for weights —\neverything from a photo is `weight_source: estimated`.\n\n**Category sweep.** For packing not yet done: walk the categories in\n`$TPA\u002Fdata\u002Fpacking-categories.md` and ask what is going in each. Slower, but it is the only mode\nthat catches the thing they have not thought of yet.\n\n**Import.** A previous trip's `inventory.yaml` is the best starting point a repeat traveller\nhas. If the user names an earlier trip workspace, read its inventory, carry over the items and\ntheir measured weights, and ask only what changed.\n\n## Weights\n\nAsk how much of the inventory can be weighed. In descending order of usefulness:\n\n1. **Measured** — a kitchen scale, in grams. Ten minutes of weighing the heavy end of the list\n   (shoes, chargers, books, toiletries, outerwear) removes most of the uncertainty, because\n   weight distribution in luggage is strongly top-heavy: a small number of items usually\n   account for the majority of the mass.\n2. **Vendor \u002F catalogue** — a published spec weight for electronics and hardware. Usually\n   accurate, usually excludes the cable and the case, so weigh those separately.\n3. **Estimated** — from `$TPA\u002Fdata\u002Ftypical-weights.md`. Fine for socks, not for a laptop.\n\nRecord which, per item, in `weight_source`. That field is what lets `reconcile.py` tell the\ndifference between \"the inventory is missing items\" and \"the estimates are drifting\".\n\nWeigh **containers separately**: a bag's `tare_kg` and each packing cube's `tare_kg` belong in\n`bags.yaml`, not as inventory items. Double-counting an empty suitcase is the classic way to\nproduce a plan that is 4 kg pessimistic.\n\n## The fields people skip and later need\n\n- **`carriage`** — anything that cannot travel in an arbitrary bag. Power banks and spare\n  lithium batteries are cabin-only in essentially every jurisdiction; liquids over 100 ml\n  cannot go through the cabin security check; sharps, tools and some aerosols are\n  checked-only or barred. See `$TPA\u002Fdata\u002Fcarriage-rules.md`. Set `carriage_reason` every time; the\n  solver treats these as hard constraints and the reason is what the traveller reads when they\n  wonder why the plan put a heavy thing in the small bag.\n- **`tier`** — essential \u002F useful \u002F nice-to-have \u002F expendable. Assign it as you capture, not\n  later. Ranking forty items under time pressure at a check-in desk does not work; ranking\n  them at home does.\n- **`replaceable_at_destination`** — can it be bought at the other end, and roughly for how\n  much. This is the field that makes the leave-behind list sensible: a 900 g bottle of shampoo\n  that costs $4 to replace is the correct thing to abandon, and no weight-only ranking can\n  know that.\n- **`value`** — replacement cost. Used with weight to rank; also the honest answer to whether\n  something belongs in a checked bag at all.\n\n## Procedure\n\n1. Read `inventory.yaml` and `bags.yaml`. If bags are not defined yet, define them first —\n   an item cannot be assigned to a bag that does not exist.\n2. Capture in the mode the user chose. Assign stable ids (`I001`…) and never renumber; the\n   plan, the PDFs and the conversation all reference them.\n3. Fill `carriage`, `tier` and `replaceable_at_destination` as you go.\n4. Validate: `uv run $TPA\u002Fscripts\u002Fvalidate.py . --json`.\n5. Report: item count, itemised total in kg, the split by `weight_source`, and the ten heaviest\n   items. The heavy-ten list is the single most useful thing to show a traveller — it is where\n   every kilogram of headroom is going to come from.\n\n## Pinning\n\nIf the user says something must stay in a particular bag — documents in the cabin bag,\na gift that must not be crushed — set `assigned_bag` and `pinned: true`. The solver will\nplace it first and refuse to move it, and will report an error rather than quietly relocating\nit if the pin makes the pack infeasible.\n",{"name":5,"description":7,"allowed-tools":24},"Read, Write, Edit, Bash(uv run *), Bash(ls *), Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Ftravel-packing-assistant\u002Fskills\u002Fpacking-inventory","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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill packing-inventory",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill packing-inventory",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill packing-inventory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fpacking-inventory\u002FSKILL.md",true,[],[48,54,61,68,75,82],{"skillNo":49,"name":50,"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":51,"categories":52,"keywords":53,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[]]