Plugin ships ~114 eagerly-listed skills (README says 30+) — please reconsider bundling the full catalog

Installing posthog@claude-plugins-official currently injects ~114 skills into every Claude Code session (the README still says "30+"), and the daily chore: sync skills workflow keeps growing that number by exporting what looks like your full internal catalog — including internal-facing skills like the signals-scout-* family and checking-deploy-timing ("for PostHog staff").

Skill names + descriptions are loaded eagerly into the system prompt (~100 tokens each per Anthropic's authoring docs), so the catalog costs roughly 11–15k tokens of every session, in every project, before PostHog is touched at all. Claude Code has no per-skill toggle, so the only remedy on our side is disabling the whole plugin.

A data point from our org: across 949 Claude Code session transcripts, posthog:* skills were invoked zero times, while the PostHog MCP tools were used 46 times. The skills aren't just unused — they dilute discovery for every other skill in the session, which is exactly what your own handbook warns about: "Skill count is a budgeted, shared resource, not a free axis to expand… a bloated set makes each individual skill less likely to fire." (https://posthog.com/handbook/engineering/ai/writing-skills)

Would you consider:

1. Splitting the plugin (core user-facing skills vs. scouts/staff-internal), or
2. Loading the long tail on demand via your skills-store MCP approach instead of bundling it, and
3. Updating the "30+ skills" README claim to match reality?

Thanks — the MCP side of the plugin is genuinely useful; it's the bundled catalog that's hard to justify keeping installed.

Start by reviewing the README's "30+ skills" claim and the daily "chore: sync skills" workflow, then trace how the plugin catalog is bundled and loaded. Done means reaching agreement on a core-versus-internal split or on-demand loading approach, implementing the selected design, and updating the README to reflect the actual catalog.