[bryantgillespie]

Releases weren't getting tagged. Changesets v3's changeset git-tag prints Created git tags: - v0.2.0, and changesets/action only picks up New tag: name@version. So the action never pushed the tag or created the release, and the job still went green. v0.2.0 got tagged and released by hand.

What changed

• scripts/release.mjs now does the publish step (npm run release). It builds dist/, which holds one .tar.gz per skill (SKILL.md at the archive root) and an Agent Skills discovery v0.2.0 index.json with $schema, name, type, description (from frontmatter), url, and a sha256: digest. It then runs gh release create v<version> on HEAD with that version's CHANGELOG section and attaches those files. If the release already exists it does nothing, since the action runs publish on every push to main that has no pending changesets.
• Archives are built with git archive from HEAD, so a local dry run matches CI. If a release is left as a draft (failed upload), the script fails instead of skipping it.
• Archive URLs in the index are versioned (v0.2.0/directus.tar.gz), so a cached index can't point at a newer archive whose digest doesn't match.
• Workflow: createGithubReleases: false, and the job gets GH_TOKEN.
• README release section updated.

directus.com serves these files at /.well-known/agent-skills/ (directus/website PR, linked below).

How to test

• node scripts/release.mjs --dry-run, then check dist/index.json and tar -tzf dist/directus.tar.gz
• npm run validate passes
• After merge, the next "Version skills" merge should create the tag and release with 13 assets

[bryantgillespie]

Website side: https://github.com/directus/website/pull/270