[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F02DFAQFJ762XWJKTSGC84":3,"skill-same:01M7F02DFAQFJ762XWJKTSGC84":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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F02DFAQFJ762XWJKTSGC84","team-composition-patterns",null,"Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring the teammate display mode (in-process, auto, tmux, iterm2), or when building a custom team composition for a non-standard workflow such as a migration or security audit.","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\u002Fagent-teams\u002Fskills\u002Fteam-composition-patterns\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: team-composition-patterns\ndescription: Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring the teammate display mode (in-process, auto, tmux, iterm2), or when building a custom team composition for a non-standard workflow such as a migration or security audit.\nversion: 1.0.2\nlast_verified: 2026-10-27\n---\n\n# Team Composition Patterns\n\nBest practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.\n\n## When to Use This Skill\n\n- Deciding how many teammates to spawn for a task\n- Choosing between preset team configurations\n- Selecting the right agent type (subagent_type) for each role\n- Configuring the teammate display mode (in-process, auto, tmux, iterm2)\n- Building custom team compositions for non-standard workflows\n\n## Team Sizing Heuristics\n\n| Complexity   | Team Size | When to Use                                                 |\n| ------------ | --------- | ----------------------------------------------------------- |\n| Simple       | 1-2       | Single-dimension review, isolated bug, small feature        |\n| Moderate     | 2-3       | Multi-file changes, 2-3 concerns, medium features           |\n| Complex      | 3-4       | Cross-cutting concerns, large features, deep debugging      |\n| Very Complex | 4-5       | Full-stack features, comprehensive reviews, systemic issues |\n\n**Rule of thumb**: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.\n\n## Preset Team Compositions\n\n### Review Team\n\n- **Size**: 3 reviewers\n- **Agents**: 3x `team-reviewer`\n- **Default dimensions**: security, performance, architecture\n- **Use when**: Code changes need multi-dimensional quality assessment\n\n### Debug Team\n\n- **Size**: 3 investigators\n- **Agents**: 3x `team-debugger`\n- **Default hypotheses**: 3 competing hypotheses\n- **Use when**: Bug has multiple plausible root causes\n\n### Feature Team\n\n- **Size**: 2 implementers; the session is the lead\n- **Agents**: 2x `team-implementer`\n- **Use when**: Feature can be decomposed into parallel work streams\n\n### Fullstack Team\n\n- **Size**: 3 implementers; the session is the lead\n- **Agents**: 1x frontend `team-implementer` + 1x backend `team-implementer` + 1x test `team-implementer`\n- **Use when**: Feature spans frontend, backend, and test layers\n\n### Research Team\n\n- **Size**: 3 researchers\n- **Agents**: 3x `general-purpose`\n- **Default areas**: Each assigned a different research question, module, or topic\n- **Capabilities**: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch)\n- **Use when**: Need to understand a codebase, research libraries, compare approaches, or gather information from code and web sources in parallel\n\n### Security Team\n\n- **Size**: 4 reviewers\n- **Agents**: 4x `team-reviewer`\n- **Default dimensions**: OWASP\u002Fvulnerabilities, auth\u002Faccess control, dependencies\u002Fsupply chain, secrets\u002Fconfiguration\n- **Use when**: Comprehensive security audit covering multiple attack surfaces\n\n### Migration Team\n\n- **Size**: 3 (2 implementers + 1 reviewer); the session is the lead and writes the migration plan\n- **Agents**: 2x `team-implementer` + 1x `team-reviewer`\n- **Use when**: Large codebase migration (framework upgrade, language port, API version bump) requiring parallel work with correctness verification\n\n## Agent Type Selection\n\nWhen spawning teammates with the `Agent` tool, choose `subagent_type` based on what tools the teammate needs:\n\n| Agent Type                     | Tools Available                                      | Use For                                                    |\n| ------------------------------ | ---------------------------------------------------- | ---------------------------------------------------------- |\n| `general-purpose`              | All tools (Read, Write, Edit, Bash, etc.)            | Implementation, debugging, any task requiring file changes |\n| `Explore`                      | Read-only tools (Read, Grep, Glob)                   | Research, code exploration, analysis                       |\n| `Plan`                         | Read-only tools                                      | Architecture planning, task decomposition                  |\n| `agent-teams:team-reviewer`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Code review with structured findings               |\n| `agent-teams:team-debugger`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Hypothesis-driven investigation                    |\n| `agent-teams:team-implementer` | Read\u002FWrite\u002FEdit\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Building features within file ownership boundaries |\n| `agent-teams:team-lead`        | Read\u002Fsearch\u002FBash, Agent, Task tools, SendMessage     | The main session's role (`claude --agent agent-teams:team-lead`); never spawned as a teammate |\n\n**Key distinction**: Read-only agents (Explore, Plan) cannot modify files. Never assign implementation tasks to read-only agents.\n\n## Display Mode Configuration\n\nSet `teammateMode` in `~\u002F.claude\u002Fsettings.json`, or pass `claude --teammate-mode \u003Cmode>` for one session:\n\n```json\n{\n  \"teammateMode\": \"auto\"\n}\n```\n\n| Mode           | Behavior                                                         | Needs                         |\n| -------------- | ---------------------------------------------------------------- | ----------------------------- |\n| `\"in-process\"` | All teammates in your terminal; pick one in the agent panel (default) | Any terminal             |\n| `\"auto\"`       | Split panes inside tmux, or in iTerm2 with `it2`; in-process otherwise | Nothing extra            |\n| `\"tmux\"`       | Split panes; detects tmux or iTerm2 from the terminal            | tmux, or iTerm2 with `it2`    |\n| `\"iterm2\"`     | iTerm2 native split panes                                        | `it2` CLI and iTerm2's Python API |\n\nSplit panes don't work in VS Code's integrated terminal, Windows Terminal or Ghostty. Teammates never spawn in non-interactive mode (`claude -p`), whatever the mode.\n\n## Custom Team Guidelines\n\nWhen building custom teams:\n\n1. **The session is the coordinator** — Teammates can't spawn teammates, so the session that spawns them leads. Start it with `claude --agent agent-teams:team-lead` to give it the lead procedure\n2. **Match roles to agent types** — Use specialized agents (reviewer, debugger, implementer) when available\n3. **Avoid duplicate roles** — Two agents doing the same thing wastes resources\n4. **Define boundaries upfront** — Each teammate needs clear ownership of files or responsibilities\n5. **Keep it small** — 2-4 teammates is the sweet spot; 5+ requires significant coordination overhead\n\n## Troubleshooting\n\n**A teammate was spawned as `Explore` but needs to write files.**\n`Explore` and `Plan` are read-only agents. Change the `subagent_type` to `general-purpose` or an appropriate specialized agent type. Never assign implementation tasks to read-only agents.\n\n**The team is growing too large and coordination is slowing everything down.**\nEach additional teammate adds communication overhead. Consolidate roles: can one agent cover two dimensions? A 4-person team doing 6 independent tasks is usually better served by 3 agents covering 2 tasks each.\n\n**Split panes are not showing.**\nCheck `which tmux`, or for iTerm2 that the `it2` CLI is installed and the Python API is enabled. Under `\"auto\"`, split panes need you to already be inside tmux. `in-process` works in any terminal.\n\n**Two reviewers are flagging the same issues.**\nThe review dimensions overlap. Redefine each reviewer's focus area: one on correctness\u002Flogic, one on security, one on performance\u002Fscalability. Overlapping coverage wastes tokens and produces duplicate findings.\n\n**The lead is spawning teammates but they are not receiving tasks.**\nVerify that the lead is using the `Agent` tool to spawn teammates and passing complete context in the prompt. Teammates start fresh with no prior conversation history — they need all relevant information in their initial prompt.\n\n## Related Skills\n\n- [parallel-feature-development](..\u002Fparallel-feature-development\u002FSKILL.md) — Decompose work streams and assign file ownership once the team is composed\n- [team-communication-protocols](..\u002Fteam-communication-protocols\u002FSKILL.md) — Establish messaging norms and shutdown procedures for the assembled team\n","# Team Composition Patterns\n\nBest practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.\n\n## When to Use This Skill\n\n- Deciding how many teammates to spawn for a task\n- Choosing between preset team configurations\n- Selecting the right agent type (subagent_type) for each role\n- Configuring the teammate display mode (in-process, auto, tmux, iterm2)\n- Building custom team compositions for non-standard workflows\n\n## Team Sizing Heuristics\n\n| Complexity   | Team Size | When to Use                                                 |\n| ------------ | --------- | ----------------------------------------------------------- |\n| Simple       | 1-2       | Single-dimension review, isolated bug, small feature        |\n| Moderate     | 2-3       | Multi-file changes, 2-3 concerns, medium features           |\n| Complex      | 3-4       | Cross-cutting concerns, large features, deep debugging      |\n| Very Complex | 4-5       | Full-stack features, comprehensive reviews, systemic issues |\n\n**Rule of thumb**: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.\n\n## Preset Team Compositions\n\n### Review Team\n\n- **Size**: 3 reviewers\n- **Agents**: 3x `team-reviewer`\n- **Default dimensions**: security, performance, architecture\n- **Use when**: Code changes need multi-dimensional quality assessment\n\n### Debug Team\n\n- **Size**: 3 investigators\n- **Agents**: 3x `team-debugger`\n- **Default hypotheses**: 3 competing hypotheses\n- **Use when**: Bug has multiple plausible root causes\n\n### Feature Team\n\n- **Size**: 2 implementers; the session is the lead\n- **Agents**: 2x `team-implementer`\n- **Use when**: Feature can be decomposed into parallel work streams\n\n### Fullstack Team\n\n- **Size**: 3 implementers; the session is the lead\n- **Agents**: 1x frontend `team-implementer` + 1x backend `team-implementer` + 1x test `team-implementer`\n- **Use when**: Feature spans frontend, backend, and test layers\n\n### Research Team\n\n- **Size**: 3 researchers\n- **Agents**: 3x `general-purpose`\n- **Default areas**: Each assigned a different research question, module, or topic\n- **Capabilities**: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch)\n- **Use when**: Need to understand a codebase, research libraries, compare approaches, or gather information from code and web sources in parallel\n\n### Security Team\n\n- **Size**: 4 reviewers\n- **Agents**: 4x `team-reviewer`\n- **Default dimensions**: OWASP\u002Fvulnerabilities, auth\u002Faccess control, dependencies\u002Fsupply chain, secrets\u002Fconfiguration\n- **Use when**: Comprehensive security audit covering multiple attack surfaces\n\n### Migration Team\n\n- **Size**: 3 (2 implementers + 1 reviewer); the session is the lead and writes the migration plan\n- **Agents**: 2x `team-implementer` + 1x `team-reviewer`\n- **Use when**: Large codebase migration (framework upgrade, language port, API version bump) requiring parallel work with correctness verification\n\n## Agent Type Selection\n\nWhen spawning teammates with the `Agent` tool, choose `subagent_type` based on what tools the teammate needs:\n\n| Agent Type                     | Tools Available                                      | Use For                                                    |\n| ------------------------------ | ---------------------------------------------------- | ---------------------------------------------------------- |\n| `general-purpose`              | All tools (Read, Write, Edit, Bash, etc.)            | Implementation, debugging, any task requiring file changes |\n| `Explore`                      | Read-only tools (Read, Grep, Glob)                   | Research, code exploration, analysis                       |\n| `Plan`                         | Read-only tools                                      | Architecture planning, task decomposition                  |\n| `agent-teams:team-reviewer`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Code review with structured findings               |\n| `agent-teams:team-debugger`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Hypothesis-driven investigation                    |\n| `agent-teams:team-implementer` | Read\u002FWrite\u002FEdit\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Building features within file ownership boundaries |\n| `agent-teams:team-lead`        | Read\u002Fsearch\u002FBash, Agent, Task tools, SendMessage     | The main session's role (`claude --agent agent-teams:team-lead`); never spawned as a teammate |\n\n**Key distinction**: Read-only agents (Explore, Plan) cannot modify files. Never assign implementation tasks to read-only agents.\n\n## Display Mode Configuration\n\nSet `teammateMode` in `~\u002F.claude\u002Fsettings.json`, or pass `claude --teammate-mode \u003Cmode>` for one session:\n\n```json\n{\n  \"teammateMode\": \"auto\"\n}\n```\n\n| Mode           | Behavior                                                         | Needs                         |\n| -------------- | ---------------------------------------------------------------- | ----------------------------- |\n| `\"in-process\"` | All teammates in your terminal; pick one in the agent panel (default) | Any terminal             |\n| `\"auto\"`       | Split panes inside tmux, or in iTerm2 with `it2`; in-process otherwise | Nothing extra            |\n| `\"tmux\"`       | Split panes; detects tmux or iTerm2 from the terminal            | tmux, or iTerm2 with `it2`    |\n| `\"iterm2\"`     | iTerm2 native split panes                                        | `it2` CLI and iTerm2's Python API |\n\nSplit panes don't work in VS Code's integrated terminal, Windows Terminal or Ghostty. Teammates never spawn in non-interactive mode (`claude -p`), whatever the mode.\n\n## Custom Team Guidelines\n\nWhen building custom teams:\n\n1. **The session is the coordinator** — Teammates can't spawn teammates, so the session that spawns them leads. Start it with `claude --agent agent-teams:team-lead` to give it the lead procedure\n2. **Match roles to agent types** — Use specialized agents (reviewer, debugger, implementer) when available\n3. **Avoid duplicate roles** — Two agents doing the same thing wastes resources\n4. **Define boundaries upfront** — Each teammate needs clear ownership of files or responsibilities\n5. **Keep it small** — 2-4 teammates is the sweet spot; 5+ requires significant coordination overhead\n\n## Troubleshooting\n\n**A teammate was spawned as `Explore` but needs to write files.**\n`Explore` and `Plan` are read-only agents. Change the `subagent_type` to `general-purpose` or an appropriate specialized agent type. Never assign implementation tasks to read-only agents.\n\n**The team is growing too large and coordination is slowing everything down.**\nEach additional teammate adds communication overhead. Consolidate roles: can one agent cover two dimensions? A 4-person team doing 6 independent tasks is usually better served by 3 agents covering 2 tasks each.\n\n**Split panes are not showing.**\nCheck `which tmux`, or for iTerm2 that the `it2` CLI is installed and the Python API is enabled. Under `\"auto\"`, split panes need you to already be inside tmux. `in-process` works in any terminal.\n\n**Two reviewers are flagging the same issues.**\nThe review dimensions overlap. Redefine each reviewer's focus area: one on correctness\u002Flogic, one on security, one on performance\u002Fscalability. Overlapping coverage wastes tokens and produces duplicate findings.\n\n**The lead is spawning teammates but they are not receiving tasks.**\nVerify that the lead is using the `Agent` tool to spawn teammates and passing complete context in the prompt. Teammates start fresh with no prior conversation history — they need all relevant information in their initial prompt.\n\n## Related Skills\n\n- [parallel-feature-development](..\u002Fparallel-feature-development\u002FSKILL.md) — Decompose work streams and assign file ownership once the team is composed\n- [team-communication-protocols](..\u002Fteam-communication-protocols\u002FSKILL.md) — Establish messaging norms and shutdown procedures for the assembled team\n",{"name":5,"version":24,"description":7,"last_verified":25},"1.0.2",1793059200000,"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fagent-teams\u002Fskills\u002Fteam-composition-patterns","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill team-composition-patterns",{"tool":40,"command":41},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill team-composition-patterns",{"tool":43,"command":44},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill team-composition-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fteam-composition-patterns\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fagent-type-selection.md","REFERENCE","参考文档",3490,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fteam-composition-patterns\u002Freferences\u002Fagent-type-selection.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fpreset-teams.md",9331,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fteam-composition-patterns\u002Freferences\u002Fpreset-teams.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",[],[]]