Sharing code/deps between Agent Skills in monorepos

[hlineholm-teledyne]

I've been thinking about how teams share code and dependencies between Agent Skills in monorepos and would love practical tips.

Problem in one line

• Related skills often duplicate small shared utilities (env, API helpers, error handling). At scale this becomes a maintenance burden.

Common approaches

• Vendored copy per skill (portable, no setup)
• Org-scoped/private packages (centralized maintenance, requires auth/setup)
• Build-time bundling (CI/bundler complexity)
• MCP/registry experiments

Short questions

1. Do you publish org-scoped packages for skills? How was onboarding (auth, .npmrc)?
2. Repo layout: ./packages/ vs ./skills/packages/ — which worked for you?
3. Naming: how do you name packages to avoid clutter in org package lists?
4. Heuristics: simple thresholds (skill count / LOC / security) for when to extract?
5. Tooling: bundlers, CI patterns, or simple scripts you recommend?

Examples, links, or short anecdotes much appreciated — thank you!