[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1VB228TMQHXP3456Z1D0P":3,"skill-same:01M7F1VB228TMQHXP3456Z1D0P":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},"01M7F1VB228TMQHXP3456Z1D0P","packing-docs",null,"Render the trip's packing documents — a one-page airport counter card of the binding allowances and bag weights, and a full per-bag packing list with tick boxes — as PDF via Typst and as Markdown, then deliver them by email, to cloud storage, into a static-site repo, or to disk. Use when the user asks for a packing list, a PDF, something to print, a page on their site, or to have the plan sent to them.","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-docs\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: packing-docs\ndescription: Render the trip's packing documents — a one-page airport counter card of the binding allowances and bag weights, and a full per-bag packing list with tick boxes — as PDF via Typst and as Markdown, then deliver them by email, to cloud storage, into a static-site repo, or to disk. Use when the user asks for a packing list, a PDF, something to print, a page on their site, or to have the plan sent to them.\nallowed-tools: Read, Write, Edit, Bash(typst *), Bash(uv run *), Bash(mkdir *), Bash(ls *), Bash(cp *), Bash(curl *), Bash(git status *), Bash(git add *), Bash(git commit *), Glob\n---\n\n# Packing Documents\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\nRenders `plan.yaml`, `allowances.yaml`, `bags.yaml` and `inventory.yaml` into two documents.\n\n**The counter card** is one A4 page: the binding limits in large type, each bag's projected\nweight against its allowance, the per-segment allowance table, and the excess-baggage prices.\nIt exists to be printed and read standing up, in a queue, with a bag on a scale. Its real job\nis to let a traveller check a claim at the desk against the carrier's own published figure —\nwhich is why every number on it carries the confidence and the date it was verified.\n\n**The packing list** is the working document: bag by bag, cube by cube, with a tick column,\ncarriage markers for the cabin-only and checked-only items, and the not-packed list at the end.\n\n## Rendering\n\nBoth renderers read the workspace YAML directly, so no number is transcribed by hand.\nTranscription is where totals go wrong, and these totals are read at a check-in desk.\n\n### PDF, with Typst\n\n**Typst refuses to compile a source file that sits outside `--root`**, and a symlink does not\nget around it. Never widen the root to `\u002F` or `$HOME` to reach the plugin: that lets a template\nread any file the user can. Copy the templates into the workspace instead, refreshing them on\nevery render so a plugin update reaches them, and root the compile at the workspace:\n\n```bash\nmkdir -p \"$TRIP\u002Foutput\" \"$TRIP\u002F.typst\"\ncp \"$TPA\"\u002Ftypst\u002F*.typ \"$TRIP\u002F.typst\u002F\"\n\ntypst compile --root \"$TRIP\" \"$TRIP\u002F.typst\u002Fcounter-card.typ\" \"$TRIP\u002Foutput\u002Fcounter-card.pdf\"\ntypst compile --root \"$TRIP\" \"$TRIP\u002F.typst\u002Fpacking-list.typ\" \"$TRIP\u002Foutput\u002Fpacking-list.pdf\"\n```\n\nThe templates read `itinerary.yaml`, `allowances.yaml`, `plan.yaml`, `bags.yaml` and\n`inventory.yaml` from the root by default, so no `--input` flags are needed. The workspace\n`.gitignore` ignores `.typst\u002F`. To hand a trip repo to someone without the plugin, remove that\nline so the templates are committed with it.\n\nIf `typst` is not installed, say so and give the install line for the user's platform rather\nthan silently producing only Markdown — the plain-text form is a fine substitute, but only if\nthey know that is what they got.\n\n### Markdown\n\n```bash\nuv run \"$TPA\u002Fscripts\u002Frender_markdown.py\" \"$TRIP\" --doc both --out-dir \"$TRIP\u002Foutput\"\n```\n\n`--doc counter-card | packing-list | both`, `--out FILE` for a single document, `--now ISO8601`\nto pin the timestamp. `--frontmatter key=value` (repeatable) emits a YAML frontmatter block,\nwhich is what a static site needs:\n\n```bash\nuv run \"$TPA\u002Fscripts\u002Frender_markdown.py\" \"$TRIP\" --doc counter-card \\\n  --frontmatter 'layout=..\u002F..\u002Flayouts\u002FWiki.astro' --title 'Counter card — BOS → TLV'\n```\n\n`title` and `generated` are added automatically whenever frontmatter is requested; keys you\npass win over them.\n\n### Both media must agree\n\nThe Typst templates and the Markdown renderer apply the same rule: where a bag has a scale\nreading heavier than its itemised projection, the **reading** governs, and headroom and status\nare recomputed against it rather than reprinted from `plan.yaml`. A bag can therefore show\n`OVER` in the documents while `plan.yaml` still says `tight` — that is deliberate, and the\ndocuments are the conservative view. If the PDF and the Markdown page ever disagree with each\nother, that is a bug, not a rounding difference.\n\nCheck the output exists and is non-trivial in size before reporting success. A Typst compile\nthat fails on a missing field exits non-zero; a compile that succeeds against an empty\n`plan.yaml` produces a valid, useless PDF.\n\n## Delivery\n\nRead `~\u002F.config\u002Ftravel-packing-assistant\u002Fdelivery.yaml` if it exists:\n\n```yaml\ndefault: local                 # local | email | drive | repo\nemail:\n  to: you@example.com\n  from: null                   # required by some providers\n  stage: null                  # optional, for large PDFs: a private bucket you own, e.g.\n                               #   { bucket: s3:\u002F\u002Fexample-private\u002Ftmp, expires_minutes: 15 }\ndrive:\n  folder: \"Travel\u002FPacking\"\nrepo:\n  path: ~\u002Fpath\u002Fto\u002Fsite         # an existing git working copy\n  docs_dir: src\u002Fpages\u002Fwiki\n  assets_dir: public\u002Ftravel    # null to skip the PDFs\n  format: markdown+pdf\n  frontmatter:\n    layout: ..\u002F..\u002Flayouts\u002FWiki.astro\n  commit: true\n  push: false\nprint: false\n```\n\nThat file lives outside the plugin and outside the workspace deliberately: it survives\n`\u002Fplugin update`, and it never gets committed to a trip repo. If it does not exist, save to\n`output\u002F` and offer to create it.\n\n**Local** — the default when nothing is configured. Save to `output\u002F`, report the absolute\npaths.\n\n**Email** — send to the configured address with both PDFs attached. Sending mail leaves this\nmachine and cannot be recalled, so show the recipient, the subject and the attached files, and\nask before sending. Attach inline (base64) by default. It costs context on a large PDF but\nkeeps the document out of third-party storage.\n\nA link instead of an attachment needs a store the user configured as `email.stage` in\n`delivery.yaml`. Never pick one, and never use a public bucket or a link-sharing service. These\ndocuments state when a home will be empty, and anyone holding the link can read them until it\nexpires. With `email.stage` set, ask before each staged send, then upload, presign a GET that\nexpires within `expires_minutes` (60 at most), send the link, and delete the staged object\nonce the mail is sent. If `email.stage` is not set, attach inline or save locally.\n\n**Drive \u002F cloud storage** — upload to the configured folder. Never write to the root of a\ndrive; if the configured folder does not exist, ask rather than picking one.\n\n**Repo** — copy the finished documents into an existing git working copy, typically a static\nsite, so the packing list becomes a page readable on a phone rather than a PDF that has to\nhave been downloaded. Markdown goes to `docs_dir`, PDFs to `assets_dir`, named\n`packing-\u003Ctrip-id>-counter-card.*` and `packing-\u003Ctrip-id>-list.*` so trips coexist and a\nre-render overwrites its own pages.\n\nWrite only into those two directories. Do not edit the site's index, navigation or README to\nlink the new page — say it needs linking and let the user do it. A delivery step that edits a\nsite's structure is a delivery step that breaks the site.\n\n**Pushing is publishing.** `push` defaults to `false`. A repo wired to a host builds on push,\nso a push is a deploy, and a deploy makes the document reachable by anyone who can reach the\nsite — a private repo is not the same as a private site. Confirm before every push, separately\neach time.\n\nThat caution is sharper for this document than for most: a packing list states the dates a home\nwill be empty and enumerates what is worth taking from it, and the counter card names the\nflights. Before the first push to any site, establish what actually guards it. If the answer is\nnothing, publish the counter card if the user wants and keep the packing list local.\n\n## Timing\n\nOffer to render at two moments and not otherwise:\n\n- When the plan is final, before packing starts — the list is for use while packing.\n- The evening before departure, after the last weigh-in — the counter card should carry the\n  actual final weights, not the projected ones.\n\nA counter card rendered from a provisional plan must say `PROVISIONAL` on it. The templates do\nthat automatically when `plan.yaml` carries warnings; do not strip the warnings to get a\ncleaner-looking document.\n","# Packing Documents\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\nRenders `plan.yaml`, `allowances.yaml`, `bags.yaml` and `inventory.yaml` into two documents.\n\n**The counter card** is one A4 page: the binding limits in large type, each bag's projected\nweight against its allowance, the per-segment allowance table, and the excess-baggage prices.\nIt exists to be printed and read standing up, in a queue, with a bag on a scale. Its real job\nis to let a traveller check a claim at the desk against the carrier's own published figure —\nwhich is why every number on it carries the confidence and the date it was verified.\n\n**The packing list** is the working document: bag by bag, cube by cube, with a tick column,\ncarriage markers for the cabin-only and checked-only items, and the not-packed list at the end.\n\n## Rendering\n\nBoth renderers read the workspace YAML directly, so no number is transcribed by hand.\nTranscription is where totals go wrong, and these totals are read at a check-in desk.\n\n### PDF, with Typst\n\n**Typst refuses to compile a source file that sits outside `--root`**, and a symlink does not\nget around it. Never widen the root to `\u002F` or `$HOME` to reach the plugin: that lets a template\nread any file the user can. Copy the templates into the workspace instead, refreshing them on\nevery render so a plugin update reaches them, and root the compile at the workspace:\n\n```bash\nmkdir -p \"$TRIP\u002Foutput\" \"$TRIP\u002F.typst\"\ncp \"$TPA\"\u002Ftypst\u002F*.typ \"$TRIP\u002F.typst\u002F\"\n\ntypst compile --root \"$TRIP\" \"$TRIP\u002F.typst\u002Fcounter-card.typ\" \"$TRIP\u002Foutput\u002Fcounter-card.pdf\"\ntypst compile --root \"$TRIP\" \"$TRIP\u002F.typst\u002Fpacking-list.typ\" \"$TRIP\u002Foutput\u002Fpacking-list.pdf\"\n```\n\nThe templates read `itinerary.yaml`, `allowances.yaml`, `plan.yaml`, `bags.yaml` and\n`inventory.yaml` from the root by default, so no `--input` flags are needed. The workspace\n`.gitignore` ignores `.typst\u002F`. To hand a trip repo to someone without the plugin, remove that\nline so the templates are committed with it.\n\nIf `typst` is not installed, say so and give the install line for the user's platform rather\nthan silently producing only Markdown — the plain-text form is a fine substitute, but only if\nthey know that is what they got.\n\n### Markdown\n\n```bash\nuv run \"$TPA\u002Fscripts\u002Frender_markdown.py\" \"$TRIP\" --doc both --out-dir \"$TRIP\u002Foutput\"\n```\n\n`--doc counter-card | packing-list | both`, `--out FILE` for a single document, `--now ISO8601`\nto pin the timestamp. `--frontmatter key=value` (repeatable) emits a YAML frontmatter block,\nwhich is what a static site needs:\n\n```bash\nuv run \"$TPA\u002Fscripts\u002Frender_markdown.py\" \"$TRIP\" --doc counter-card \\\n  --frontmatter 'layout=..\u002F..\u002Flayouts\u002FWiki.astro' --title 'Counter card — BOS → TLV'\n```\n\n`title` and `generated` are added automatically whenever frontmatter is requested; keys you\npass win over them.\n\n### Both media must agree\n\nThe Typst templates and the Markdown renderer apply the same rule: where a bag has a scale\nreading heavier than its itemised projection, the **reading** governs, and headroom and status\nare recomputed against it rather than reprinted from `plan.yaml`. A bag can therefore show\n`OVER` in the documents while `plan.yaml` still says `tight` — that is deliberate, and the\ndocuments are the conservative view. If the PDF and the Markdown page ever disagree with each\nother, that is a bug, not a rounding difference.\n\nCheck the output exists and is non-trivial in size before reporting success. A Typst compile\nthat fails on a missing field exits non-zero; a compile that succeeds against an empty\n`plan.yaml` produces a valid, useless PDF.\n\n## Delivery\n\nRead `~\u002F.config\u002Ftravel-packing-assistant\u002Fdelivery.yaml` if it exists:\n\n```yaml\ndefault: local                 # local | email | drive | repo\nemail:\n  to: you@example.com\n  from: null                   # required by some providers\n  stage: null                  # optional, for large PDFs: a private bucket you own, e.g.\n                               #   { bucket: s3:\u002F\u002Fexample-private\u002Ftmp, expires_minutes: 15 }\ndrive:\n  folder: \"Travel\u002FPacking\"\nrepo:\n  path: ~\u002Fpath\u002Fto\u002Fsite         # an existing git working copy\n  docs_dir: src\u002Fpages\u002Fwiki\n  assets_dir: public\u002Ftravel    # null to skip the PDFs\n  format: markdown+pdf\n  frontmatter:\n    layout: ..\u002F..\u002Flayouts\u002FWiki.astro\n  commit: true\n  push: false\nprint: false\n```\n\nThat file lives outside the plugin and outside the workspace deliberately: it survives\n`\u002Fplugin update`, and it never gets committed to a trip repo. If it does not exist, save to\n`output\u002F` and offer to create it.\n\n**Local** — the default when nothing is configured. Save to `output\u002F`, report the absolute\npaths.\n\n**Email** — send to the configured address with both PDFs attached. Sending mail leaves this\nmachine and cannot be recalled, so show the recipient, the subject and the attached files, and\nask before sending. Attach inline (base64) by default. It costs context on a large PDF but\nkeeps the document out of third-party storage.\n\nA link instead of an attachment needs a store the user configured as `email.stage` in\n`delivery.yaml`. Never pick one, and never use a public bucket or a link-sharing service. These\ndocuments state when a home will be empty, and anyone holding the link can read them until it\nexpires. With `email.stage` set, ask before each staged send, then upload, presign a GET that\nexpires within `expires_minutes` (60 at most), send the link, and delete the staged object\nonce the mail is sent. If `email.stage` is not set, attach inline or save locally.\n\n**Drive \u002F cloud storage** — upload to the configured folder. Never write to the root of a\ndrive; if the configured folder does not exist, ask rather than picking one.\n\n**Repo** — copy the finished documents into an existing git working copy, typically a static\nsite, so the packing list becomes a page readable on a phone rather than a PDF that has to\nhave been downloaded. Markdown goes to `docs_dir`, PDFs to `assets_dir`, named\n`packing-\u003Ctrip-id>-counter-card.*` and `packing-\u003Ctrip-id>-list.*` so trips coexist and a\nre-render overwrites its own pages.\n\nWrite only into those two directories. Do not edit the site's index, navigation or README to\nlink the new page — say it needs linking and let the user do it. A delivery step that edits a\nsite's structure is a delivery step that breaks the site.\n\n**Pushing is publishing.** `push` defaults to `false`. A repo wired to a host builds on push,\nso a push is a deploy, and a deploy makes the document reachable by anyone who can reach the\nsite — a private repo is not the same as a private site. Confirm before every push, separately\neach time.\n\nThat caution is sharper for this document than for most: a packing list states the dates a home\nwill be empty and enumerates what is worth taking from it, and the counter card names the\nflights. Before the first push to any site, establish what actually guards it. If the answer is\nnothing, publish the counter card if the user wants and keep the packing list local.\n\n## Timing\n\nOffer to render at two moments and not otherwise:\n\n- When the plan is final, before packing starts — the list is for use while packing.\n- The evening before departure, after the last weigh-in — the counter card should carry the\n  actual final weights, not the projected ones.\n\nA counter card rendered from a provisional plan must say `PROVISIONAL` on it. The templates do\nthat automatically when `plan.yaml` carries warnings; do not strip the warnings to get a\ncleaner-looking document.\n",{"name":5,"description":7,"allowed-tools":24},"Read, Write, Edit, Bash(typst *), Bash(uv run *), Bash(mkdir *), Bash(ls *), Bash(cp *), Bash(curl *), Bash(git status *), Bash(git add *), Bash(git commit *), Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Ftravel-packing-assistant\u002Fskills\u002Fpacking-docs","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-docs",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill packing-docs",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill packing-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fpacking-docs\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",[],[]]