CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-mate-antigravity

Run Antigravity CLI non-interactively for coding tasks. Use when the user asks to delegate work to Antigravity.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A lean, highly actionable instruction-only skill: concrete commands, explicit success/failure semantics, and genuine validation checkpoints including diff inspection for workspace edits. The only soft spots are slight redundancy in the closing example paragraph and the unnamed success status value in the JSON result.

Suggestions

Name the actual success status value (e.g., `status: "SUCCESS"`) so success detection is unambiguous without guessing.

Trim the closing example paragraph, which restates earlier guidance on parsing `response`/`error` and inspecting the diff, down to just the scenario-specific detail (touching only named files).

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational facts Claude would not know (the 5m `--print-timeout` default, permission-mode inheritance, the exact `authentication failed or timed out` error), with no padding of known concepts. The closing 'Example' paragraph partially restates earlier guidance ("parse the `response` and any reported `error`, and inspect the resulting diff"), so minor trimming is possible — anchor 4 rather than 5.

4 / 5

Actionability

It provides a copy-paste command (`agy -p "<prompt>" --output-format json`), a concrete availability check (`command -v agy`), and explicit failure semantics ("anything other than a success status is a failure", "Treat unparseable output as failure too"). The actual success status value is never named, a minor gap that keeps it below fully executable anchor 5.

4 / 5

Workflow Clarity

A clear numbered sequence with explicit validation checkpoints — availability check, JSON `status` parsing, unparseable-output handling, and "inspect the diff afterward" — plus error-recovery paths (auth failure → stop and ask the user). The destructive-operation cap does not apply because validation steps are present, so the anchor-5 match holds.

5 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no external references needed, organized into two clear sections (Run, Authentication And Permissions); under the rubric's simple-skill exception this scores 5, and no dangling file references exist since no bundle files are present.

5 / 5

Total

18

/

20

Passed

Description

73%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.

A concise, third-person description that explicitly covers both what the skill does and when to use it, with a distinctive named-tool trigger. Its main weakness is limited specificity — only one concrete action is stated — and a narrow single trigger phrase.

Suggestions

Add 1-2 concrete actions to broaden specificity, e.g., "Run Antigravity CLI non-interactively for coding tasks: send a prompt, capture JSON output, and report failures".

Expand the 'Use when' clause with natural trigger variations such as "delegate work to Antigravity, hand tasks off to Antigravity, or ask for changes via the Antigravity CLI".

Mention common task types (edits, fixes, refactors) in the description so users can recognize the skill from task language, not just the tool name.

DimensionReasoningScore

Specificity

"Run Antigravity CLI non-interactively for coding tasks" names the domain (Antigravity CLI) and one concrete action (run non-interactively), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because no list of several specific actions (e.g., what kinds of coding tasks it handles) is given.

3 / 5

Completeness

It answers both what ("Run Antigravity CLI non-interactively for coding tasks") and when ("Use when the user asks to delegate work to Antigravity") explicitly. It is not a 5 because the 'when' is a single, self-referential trigger phrase rather than a set of concrete trigger variations.

4 / 5

Trigger Term Quality

"delegate work to Antigravity" and "coding tasks" are natural phrases a user would say, giving good keyword coverage; a few natural variants (e.g., "hand off", "ask Antigravity") are missing, so it falls just below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The named third-party CLI ("Antigravity") plus its explicit trigger ("delegate work to Antigravity") defines a clear niche with minimal risk of triggering for the wrong skill, matching the anchor for distinct triggers better than the 4 anchor's 'minor overlap risk with closely related skills'.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

CherryHQ/cherry-studio

Path

resources/code-cli-skills/code-mate-antigravity/SKILL.md

Reviewed

Table of Contents

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.