Two New Skills — Maintain Splash Pages, Chroma Agent Skills (Submodule)

Why Care?

Two additions to the Lossless skills tree, landed together in commit 3a18388:

1. A first-party skill that turns an emerging Lossless convention — repo-level splash pages at <repo>/splash/ — into something an agent will recognize and apply consistently.
2. A vendored upstream skill collection from the Chroma team, pinned as a git submodule, that gives any agent loading our skills the same Chroma-integration guidance the Chroma maintainers ship to their own users.

Together they exercise two different discoveries this repo is built around: codify what we already do well (splash pages), and read upstream code, don’t paraphrase from training data (Chroma).

What’s New?

maintain-splash-pages/ — Draft

A new first-party skill at maintain-splash-pages/. Codifies the repo-level splash pattern after three confirmed reference implementations:

• memopop-site — the original
• content-farm/splash
• lfm/splash — the most recent and currently-canonical reference

The skill covers the proven shape:

• Small Astro site lives at <repo>/splash/
• Ships to GitHub Pages on push to main
• Renders the repo’s own changelog/ and context-v/ alongside curated marketing copy
• Stays isolated from any package the repo also publishes (the discipline that makes splashes safe to add to repos that also ship to JSR / npm)

It also includes a reasoning step before scaffolding — does this repo deserve a splash? — so agents don’t reflex-add one to every repo they touch. The convention is “every important repo,” and that word is doing work.

The skill is marked Draft in its own frontmatter and pairs with a sibling habit titled “Maintain a Github Splash Page for each Repo” that explains the why; the skill is canonical for the how.

chroma-agent-skills/ — Submodule from chroma-core/agent-skills

A new git submodule at chroma-agent-skills/, pulling from chroma-core/agent-skills — the official Chroma team’s Agent Skills repo. It ships two skills:

• chroma-local — open source / self-hosted Chroma
• chroma-cloud — Chroma Cloud (CloudClient, Schema, Search, cloud CLI workflows)

Vendoring upstream as a submodule rather than re-implementing means agents loading the Lossless skills tree get the maintainers’ current guidance, updated on the maintainers’ cadence, and we inherit improvements without paraphrase drift.

This is the study-repos-first discipline applied to skills themselves: when authoritative upstream guidance exists, pin it instead of restating it.

How It Works

The two additions sit at different layers:

context-v/skills/
├── maintain-splash-pages/      # first-party — our own SKILL.md
│   └── SKILL.md
└── chroma-agent-skills/        # submodule — upstream's SKILL.md tree
    └── skills/
        ├── chroma-local/
        └── chroma-cloud/

Agent loaders that walk the skills tree pick both up the same way. The submodule pin means a git submodule update --remote refreshes Chroma’s guidance when the upstream team ships changes.

What’s Next

• Promote maintain-splash-pages from Draft once one more repo gets a splash following the skill (rather than ahead of it) — that’s the fourth data point that confirms the pattern is teachable.
• Surface both skills in the README’s Skills table — deferred for a later sweep so the README change lands separately from this changelog.
• Watch the upstream chroma-core/agent-skills repo for new skills (cloud CLI workflows, schema patterns) and bump the submodule pin when they ship.

Related

• Previous entry: First Aggregator Feedstock
• maintain-splash-pages/SKILL.md — the skill itself
• chroma-agent-skills/ — vendored submodule
• study-repos-first/ — the discipline that argues for vendoring upstream over paraphrasing
• Commit 3a18388 — new(skills): add new skills - custom splash-pages skill, add chroma-agent-skills as submodule