antigravity-cli

Operate the Antigravity CLI (agy): plugins, auth, sandbox.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/autonomous-ai-agents/antigravity-cli/SKILL.md

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, highly actionable operator guide: executable commands with flags and paths, a real verification checklist, and explicit pitfalls. Its main weaknesses are mild verbosity (duplicated cross-references and an abstract orchestration-boundary paragraph) and significant content overlap between SKILL.md and references/cli-docs.md.

Suggestions

Deduplicate the slash-command, auth, sandbox, and plugin lists against references/cli-docs.md — keep a short inline summary and defer the full enumerations to the reference.

Tighten the 'Orchestration boundary' paragraph to two or three directive sentences, and state the codex/claude-code pattern reuse once instead of three times.

Consider moving the full 'Install flags' and 'Plugin subcommands' lists into the reference file, keeping only the most-used commands in the Quick Reference.

Dimension	Reasoning	Score
Conciseness	The body is dense with command lists, exact flags, and file paths, and never explains concepts Claude already knows. Minor trimmable padding exists: repeated 'the same pattern the codex / claude-code skills use' references, the somewhat philosophical 'Orchestration boundary' paragraph, and quick-reference lists duplicated in references/cli-docs.md.	4 / 5
Actionability	Fully executable guidance throughout: copy-paste-ready `terminal(command="agy -p '...' --model '...' ", workdir=..., timeout=...)` invocations, exact settings keys, exact paths under ~/.gemini/antigravity-cli/, and concrete plugin subcommands. Common cases (version check, help, plugin list, one-shot review) are all covered with runnable examples.	5 / 5
Workflow Clarity	The 'Verification' section is an explicit numbered 7-step checklist (version, help, plugin list, settings, logs), 'Pitfalls' provides error-recovery direction ('First place to look for failures: cli-*.log'), and delegation patterns are sequenced one-shot → bounded background → interactive PTY → parallel worktrees with poll/collect follow-ups. Validation checkpoints and feedback loops are present.	5 / 5
Progressive Disclosure	Sections are well organized and references/cli-docs.md is a real, one-level-deep file clearly signaled under 'Support files'. However, a substantial portion of the reference file's content (slash commands, auth behavior, sandbox settings, plugin notes, paths) is duplicated inline in SKILL.md, which is a minor organization gap against anchor 5's 'content appropriately split'.	4 / 5
	Total	18 / 20 Passed

Description

65%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, distinct, and names the exact tool, but it omits any explicit 'when to use' trigger guidance and uses one generic verb over three topic areas rather than concrete actions. Adding a Use-when clause and specific verbs would raise it substantially.

Suggestions

Append a trigger clause, e.g. 'Use when the user mentions Antigravity, agy, or asks to install, configure, or drive the Antigravity CLI.'

Replace the generic verb 'Operate' with concrete actions, e.g. 'Installs and updates the agy binary, runs non-interactive agy --print one-shots, manages plugins, and debugs auth/sandbox/permissions'.

Include natural synonyms users may say, such as 'Gemini Antigravity' or 'agy commands', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Operate the Antigravity CLI (agy): plugins, auth, sandbox" names the domain and three capability areas, but "Operate" is a single generic verb over topic nouns rather than concrete actions like 'install plugins' or 'read logs'. It matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' and falls short of anchor 4's 'several specific actions'.	3 / 5
Completeness	The 'what' is present and tool-specific, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and unambiguous.	3 / 5
Trigger Term Quality	"Antigravity CLI (agy)", "plugins", "auth", and "sandbox" are natural terms a user would say when needing this skill. A few natural variants are missing (e.g. 'Gemini CLI', 'command line', 'agent'), keeping it below anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Naming the specific, unique tool "Antigravity CLI (agy)" establishes a clear niche with minimal overlap risk; no other skill would trigger on these terms.	5 / 5
	Total	15 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/autonomous-ai-agents/antigravity-cli/SKILL.md
Commit: 68fa7e9

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.