v0.8.0 — add the Antigravity agent target — v0.8.0; no target refuses now
RFC-0013 is rewritten, not amended: its premise was false. It designed a
plugin-bundle emitter on the belief that Antigravity had no agents
directory. Its own docs list two — ~/.gemini/config/agents/.md
global, .agents/agents/.md workspace — with plugin bundles as a
third option, not the only one. Keeping that draft would have sent
someone down a bundle build to deliver two markdown files.
That is three for three. Kiro, Codex and Antigravity were each filed as
blocked on an unconfirmed fact; all three facts were published and I had
not looked. The survey generalised from the first layout it found each
time. Recorded in the RFC so the pattern is visible rather than repeated.
The emitter is markdown with rewritten frontmatter: subagent: true is
added unconditionally (without it the agent exists but invoke_subagent
cannot reach it — a silent failure), tools map Read/Grep/Bash to
view_file/grep_search/run_command, and model passes through when it is
one of inherit|flash|pro, which the shipped agents already are.
Glob is named and dropped, not mapped to list_dir. They are different
operations and a wrong tool is invisible where a missing one is not.
Frontmatter verified well-formed: quoted scalars parse, embedded quotes
and em-dashes survive, body is the system prompt, nothing leaks across
the delimiter.
Every surveyed tool with an agent format now installs by command. Only
Cursor is absent, and only because it has no such format.
npx skilldrop-cli@0.8.0 install --pack solution-architect