SKILLEMALL.ai

AB agy-delegate

Delegate a coding task to the Google Antigravity CLI (`agy`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

amElnagdy/delegate-skills Agent Skills author: amElnagdy 6 files · 1 script body ≈ 2 487 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself.

As a process B 73/100 · Nearly there — weak spots: result and completion, running it twice

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
100/100
safety, quality, tests
Safety 60%
100
Quality 40%
100
Run on models
none yet
Process rating
B
73/100
Nearly there
Running it twice w 4
30
Result and completion w 14
40
Failures and branches w 10
50
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 · 0

    ✓ No critical or high findings

    Files scanned: 6. 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 73/100

    • 30Running it twice. 9 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 18 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2487 tokens
    • 100Progress reporting. Reports progress
    • low The response is described with custom markup (4 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

    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 549: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 18 items
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +3All 1 scripts are documented
    • +1License stated

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