google-skills
google’s 149 skills for its own products, opened only when one matches.
- status
- optional ships with colonizer, off until you switch it on.
- version
- 2026.10.02-1d77046
- pinned
- commit 1d77046 (no upstream tags) · archive sha256 6af0ed4e
- licence
- apache-2.0
- source
- google/skills ↗
what it does for you
google-skills holds google's skills for its products. claude code discovers exactly one skill, a finder; the other 149 sit in a local catalog, outside skills/, with upstream's directory shape, and only the skill that matches is opened.
what it needs
- the claude code settler
how to turn it on
settings → skillsets: switch on google-skills. an org workspace can switch it for its own colonies.
how far it has been tested
real claude code has loaded it on real hardware, against a stub gateway; it has not run in a colony yet.
how colonizer runs it
- pinned by sha256 in vendor.lock (commit 1d77046, dated 2026.10.02; upstream has no tags)
- mounted read-only at /opt/colonizer/plugins/google-skills, outside the colony worktree
- the finder is colonizer's copy of upstream's (vendor/google-skills/finding-google-skills/SKILL.md): it filters the local index.json, whose entrypoints are rewritten from raw.githubusercontent.com urls to paths relative to the plugin root, and reads only the matching SKILL.md
- it has no network steps and copies nothing into the working directory, where the copy would land in the pull request; upstream's plugins/ (mcp servers) is not staged
what it costs
7.0 mb staged; no download or memory figure is recorded beyond that.