1eebca388e
The verbose action-to-tool tables and skill-loading explainers in the per-harness reference files restated guidance modern agents already follow. Trim each file to the harness-specific notes that still carry weight (subagent dispatch, task tracking, instructions-file paths), and delete claude-code-tools.md and copilot-tools.md, which had nothing left that wasn't generic.
1.5 KiB
Antigravity CLI (agy) Tool Mapping
Skills speak in actions ("dispatch a subagent", "create a todo", "read a file"). On the Antigravity CLI (agy) these resolve to the tools below.
| Action skills request | Antigravity CLI equivalent |
|---|---|
Dispatch a subagent (Subagent (general-purpose): template) |
invoke_subagent with a built-in TypeName — self for full-capability work, research for read-only (see Subagent support) |
| Task tracking ("create a todo", "mark complete") | a task artifact — write_to_file with IsArtifact: true and ArtifactType: "task" (see Task tracking). Not manage_task, which manages background processes. |
Task tracking
Antigravity has no todo tool (manage_task manages background
processes — list/kill/status/send_input — it is not a checklist). When a
skill says to create a todo list or track tasks, maintain a task artifact: a
markdown checklist saved with write_to_file (IsArtifact: true,
ArtifactMetadata.ArtifactType: "task"), edited with replace_file_content /
multi_replace_file_content as you go.
At the start of any multi-step task, create the task artifact listing every step of
your plan. As you complete each step, edit the artifact to mark it done (- [x]).
If the plan changes, update the checklist. Keep it current — it is your source of
truth for what remains; once the conversation gets long, re-read it before starting
each step.