Skip to content
Development
Skill

/agy-native

Run a supplied task in AGY Antigravity and collect its result. Use when: the caller selects AGY; never a fallback for native coding.

From plugin
agentops
43634 skills7 agents1 hook
Install
$ npx -y skills add boshu2/agentops --skill agy-native --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/agy-native

Context preview

The summary Claude sees to decide when to auto-load this skill.

Run a supplied task in AGY Antigravity and collect its result. Use when: the caller selects AGY; never a fallback for native coding.

SKILL.md

agy-native.SKILL.md
name: agy-native
description: 'Run a supplied task in AGY Antigravity and collect its result. Use when: the caller selects AGY; never a fallback for native coding.'
practices: [team-topologies, design-by-contract]
hexagonal_role: driving-adapter
consumes: [explicit-packet]
produces: [agy-run-evidence]
context_rel:
- kind: separate-ways
  with: codex-exec
skill_api_version: 1
user-invocable: true
metadata:
  tier: cross-vendor
  dependencies: []
  capabilities: [dispatch_explicit_packet, provide_fresh_context]
  effects: [start_agy_session]
  canonical_status: canonical
  disposition: keep_optional_adapter
output_contract: AGY runtime evidence

AGY Native

Use AGY only when the caller explicitly selects that runtime. Discover its live command surface with `agy --help` (and `agy models` for the current model set) before acting, and scope every session to the supplied workspace and packet.

Discovering the live command surface before acting works because AGY's CLI changes faster than any skill text: a remembered flag is a guess, while a freshly listed one is evidence.

Permission posture (disclose it; never assume it)

The posture a run gets is chosen by flags, so name it explicitly:

  • Default `agy` runs interactively and prompts for each tool permission.
  • `--dangerously-skip-permissions` auto-approves every tool call — use it only

when the packet's declared effects and the caller's authorization cover that blast radius.

  • `--sandbox` restricts the session's terminal access.
  • Print mode (`agy -p` / `--print`) is the sanctioned headless path and carries

a built-in `--print-timeout` (default 5m); a run that exceeds it is killed and reported as timed out, not as a result.

A reader who sets none of these gets AGY's interactive default, not a scoped run. Match the posture to the declared effects and disclose which one was used.

When AGY is unavailable

If `agy` is not installed or its command surface cannot be discovered, report the absence as a disclosed fact and stop. Do not fall back to another runtime, do not guess a command surface, and never route through `claude -p`.

Named failure mode — **wrapper drift**: invoking AGY through remembered syntax that silently changed, producing runs that look scoped but are not.

Anti-pattern: reusing one AGY session for both author and validator roles because starting a second session is slower. Corrective: keep the identities distinct; a shared session forfeits the fresh-judgment guarantee that makes the validator's evidence usable.

  • Keep author and validator sessions distinct when AGY supplies both roles.
  • Persist the runtime conversation/context identity and artifact references.
  • Validators remain read-only and hand judgment to Validate; they do not write

the core verdict directly.

  • AGY plugin, memory, permission, retry, and session state remain substrate facts

and never become AgentOps phase, queue, or completion state.

  • Never invoke `claude -p` through an AGY wrapper.

Return evidence to the caller and stop. Installation, plugin mutation, and recurring scheduling require separate explicit authorization.

Read more
Ships withagentops

AgentOps gives Claude Code and Codex reusable instructions, called skills, for investigating code, writing useful tests, and independently reviewing changes.

Get the whole plugin

Other skills on agentops.

cass
Skill

cass

Search agent session logs and cited episodes with CASS. Use when: past prompts, decisions or failures may answer a question; repeated text is not a proven…

@boshu2@boshu2View Skill
cc-hooks
Skill

cc-hooks

Configure Claude Code hooks and narrow enforcement guards. Use when: the caller requests hook installation, repair or policy changes; a hook is not required to…

@boshu2@boshu2View Skill