SKILLEMALL.ai
GitHub ↗ RU Sign in

AC antigravity-cli

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

NousResearch/hermes-agent Hermes author: NousResearch MIT 2 files body ≈ 2 276 tokens Open the sourcegithub.com↗ analyzed 2 d ago

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

As a process C 56/100 · Has gaps — weak spots: when it triggers, failures and branches, running it twice

IntegrationSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
89
Run on models
none yet
Process rating
C
56/100
Has gaps
Failures and branches w 10
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1

    ✓ Guard found no suspicious behaviour. 1 matches are attack strings quoted in this security skill's own documentation.

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 56/100

    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 60Consistency. The Hermes dialect needs category and tags
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 70 steps, 2 vague phrases
    • 100Execution cost. Instruction body is 2276 tokens
    • 100Progress reporting. Reports progress
    • low 13 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (6 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Description length 58: 120–800 characters recommended
    • +2Single-language instructions
    • +4Structure: 28 headings
    • +3Step-by-step instructions: 70 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.