Files
zeekay ad95ed6ca2 State a dependency version once
A version written into a manifest is written into every manifest that wants
the package, and the copies drift. The catalog moves the number out of the
manifest: a manifest names the package, the workspace names the version.

Only names that already resolve to exactly one version move, so nothing
installs differently -- 1424 resolutions are unchanged. Three kinds stay
where they are: a name used at two specifiers, because the catalog would
pick a winner; a name an override already decides, because pnpm records the
overridden specifier; and a name whose one specifier resolved to two
versions, because one entry would unify them.
2026-09-08 23:21:56 -07:00
..
2026-08-09 09:16:43 -07:00
2026-08-09 09:16:43 -07:00
2026-09-08 23:21:56 -07:00

Insights AI

Skills

Agent skills live in products/*/skills/ as Markdown or Jinja2 templates. The build system renders them into dist/skills/ (human-readable) and packages them into dist/skills.zip. Both are gitignored — CI builds the ZIP from source and publishes it as a GitHub release.

Commands

insightscli build:skills          # Build skills to dist/skills/ and dist/skills.zip
insightscli build:skills --list   # List discovered skills
insightscli lint:skills           # Validate skill sources without rendering
insightscli init:skill --product <product> --name <name>       # Scaffold a new skill
insightscli init:skill --product <product> --name <name> --j2  # Scaffold as Jinja2 template

Workflow

  1. Edit skill sources in products/*/skills/
  2. Push to master — CI builds the ZIP and creates a GitHub release (agent-skills-latest + versioned)