Install footprint: 1.1GB in ~/.claude/skills (739MB node_modules + 21MB .git) and connect-chrome duplicates open-gstack-browser

Two packaging observations from a routine setup audit of a gstack install (v1.58.x):

**1. Install size.** The gstack skill directory is a full git clone weighing ~1.1GB inside `~/.claude/skills/gstack`: 739MB `node_modules`, 151MB `browse`, ~61MB each for `design`/`bin`/`make-pdf`, plus a 21MB `.git`. For a skills directory that agents scan every session, a slimmer release artifact (pruned dev dependencies, shallow/no .git, optional heavy modules downloaded on first use) would help.

**2. Duplicate skill registration.** `connect-chrome/` ships byte-identical to `open-gstack-browser/`, so both register as separate skills with the same content. Deleting one locally works until `/gstack-upgrade` restores it — probably worth deduplicating at the packaging level (alias or single skill).

Start by tracing how the gstack install populates ~/.claude/skills/gstack and how /gstack-upgrade restores it. Inspect the connect-chrome/ and open-gstack-browser/ skill directories alongside node_modules and .git. Done means a slimmer install artifact and one non-duplicated skill registration, verified by repeating the setup audit and upgrade flow.

Written by the indexing model from the issue text.