Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
57 changes: 30 additions & 27 deletions .agents/skills/orly-burst/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
---
name: orly-burst
description: |
Run requested burst lanes on AWS or E2E Networks, or on the current runner,
and manage their snapshots. Use on "run acceptance on a burst box" or
Run requested burst lanes on AWS or E2E Networks, and manage their
snapshots. Use on "run acceptance on a burst box" or
"capture a snapshot". Paid runs need explicit authorization; missing PR
evidence does not authorize a run. Never run from a gate or hook.
---

# orly-burst

This skill owns one `orly burst` run, from choosing the lanes to reporting
the evidence. The lanes, setup, warm-up, secrets and result paths are the
repository's, declared in `.orly/orly.json`. One-time setup, settings and
costs are in orly's `.orly/docs/BURST.md`.
the evidence. Lanes, setup, secrets, results, region and image are the
repository's `burst` settings in `.orly/orly.json`. Setup and costs:
https://github.com/agentsfleet/orly/blob/main/docs/BURST.md

## When

Expand All @@ -24,32 +24,35 @@ costs are in orly's `.orly/docs/BURST.md`.

## Steps

1. **List the lanes.** Run `orly burst`. It prints the declared lanes and exits
2; pick only lanes it lists.
1. **List the lanes.** Run `orly burst`; pick only lanes it lists.
2. **Pick the provider.** Use `aws-spot` or `e2e` where outbound SSH on port
22 works, and the repository's burst workflow from an HTTP-only session.
Inside a CI job, `--provider here` runs the lane on the runner itself.
3. **Warm once.** A repository with no snapshot starts every lane cold from a
base image. Run `orly burst snapshot --provider <P>` after setup changes,
and `orly burst snapshot --prune --provider <P>` to keep the newest two.
4. **Run.** Run `orly burst <lane>... --provider <P>`, with `--ref <branch>`
for a ref other than the current branch. Lanes run in parallel, one machine
each. `--keep` leaves machines running for inspection, and they keep
billing.
5. **Report.** Quote every `orly burst: lane=…` summary line and the `total`
line verbatim, with the evidence directory. Only a numeric `exit=` is
evidence. `exit=interrupted`, `deadline`, `cancelled`, `unlaunched` or
`not_run` proves nothing about the code; report that lane as not run.
22 works and the caller stays on one network for the run. From an
HTTP-only session, start the repository's burst workflow instead.
3. **Warm once.** Capture `orly burst snapshot --provider <P>` after setup
changes, and prove a new provider with one capture before any lane.
`orly burst snapshot --prune --provider <P>` keeps the newest one.
4. **Run.** `orly burst <lane>... --provider <P> [--ref <branch>]`. Record
orly's PID from `$!`, and stop it only with `kill -INT <pid>`, so it
deletes what it rented.
5. **Report.** Quote every `lane=` line and the `total` line verbatim. Only a
numeric `exit=` is evidence; any other value means the lane did not run.

For a numeric failure, read `<evidence>/run.log` and name the failing step
and test. Name any 🔴 line's resource as left to delete by hand.

## Progress

Before a run, print one line: lanes or snapshot, provider, region, image, ref
and hourly price. Relay each `orly burst:` line as it arrives. After it,
print the result lines and what was deleted.

## Credentials

- Never print a credential, pass one as a command-line argument, or write one
to a file.
- `burst.secrets` holds `op://` references. orly uses a value already in the
environment, or reads it with `op read`, on the caller. The value reaches
the machine only over the SSH session's standard input.
- `burst.secrets` holds `op://` references, read on the caller. A value
reaches the machine only over the SSH session's standard input, and never
reaches a snapshot.
- AWS credentials come from the caller's `aws` configuration or the job's
cloud login step. E2E credentials are a TIR API token's `E2E_API_KEY`,
`E2E_AUTH_TOKEN` and `E2E_PROJECT_ID` in the environment; MyAccount keys do
not work.
- A snapshot never receives a secret: setup and warm run without one.
login step. E2E needs a TIR API token's `E2E_API_KEY`, `E2E_AUTH_TOKEN` and
`E2E_PROJECT_ID`; MyAccount keys do not work.
57 changes: 30 additions & 27 deletions .claude/skills/orly-burst/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
---
name: orly-burst
description: |
Run requested burst lanes on AWS or E2E Networks, or on the current runner,
and manage their snapshots. Use on "run acceptance on a burst box" or
Run requested burst lanes on AWS or E2E Networks, and manage their
snapshots. Use on "run acceptance on a burst box" or
"capture a snapshot". Paid runs need explicit authorization; missing PR
evidence does not authorize a run. Never run from a gate or hook.
---

# orly-burst

This skill owns one `orly burst` run, from choosing the lanes to reporting
the evidence. The lanes, setup, warm-up, secrets and result paths are the
repository's, declared in `.orly/orly.json`. One-time setup, settings and
costs are in orly's `.orly/docs/BURST.md`.
the evidence. Lanes, setup, secrets, results, region and image are the
repository's `burst` settings in `.orly/orly.json`. Setup and costs:
https://github.com/agentsfleet/orly/blob/main/docs/BURST.md

## When

Expand All @@ -24,32 +24,35 @@ costs are in orly's `.orly/docs/BURST.md`.

## Steps

1. **List the lanes.** Run `orly burst`. It prints the declared lanes and exits
2; pick only lanes it lists.
1. **List the lanes.** Run `orly burst`; pick only lanes it lists.
2. **Pick the provider.** Use `aws-spot` or `e2e` where outbound SSH on port
22 works, and the repository's burst workflow from an HTTP-only session.
Inside a CI job, `--provider here` runs the lane on the runner itself.
3. **Warm once.** A repository with no snapshot starts every lane cold from a
base image. Run `orly burst snapshot --provider <P>` after setup changes,
and `orly burst snapshot --prune --provider <P>` to keep the newest two.
4. **Run.** Run `orly burst <lane>... --provider <P>`, with `--ref <branch>`
for a ref other than the current branch. Lanes run in parallel, one machine
each. `--keep` leaves machines running for inspection, and they keep
billing.
5. **Report.** Quote every `orly burst: lane=…` summary line and the `total`
line verbatim, with the evidence directory. Only a numeric `exit=` is
evidence. `exit=interrupted`, `deadline`, `cancelled`, `unlaunched` or
`not_run` proves nothing about the code; report that lane as not run.
22 works and the caller stays on one network for the run. From an
HTTP-only session, start the repository's burst workflow instead.
3. **Warm once.** Capture `orly burst snapshot --provider <P>` after setup
changes, and prove a new provider with one capture before any lane.
`orly burst snapshot --prune --provider <P>` keeps the newest one.
4. **Run.** `orly burst <lane>... --provider <P> [--ref <branch>]`. Record
orly's PID from `$!`, and stop it only with `kill -INT <pid>`, so it
deletes what it rented.
5. **Report.** Quote every `lane=` line and the `total` line verbatim. Only a
numeric `exit=` is evidence; any other value means the lane did not run.

For a numeric failure, read `<evidence>/run.log` and name the failing step
and test. Name any 🔴 line's resource as left to delete by hand.

## Progress

Before a run, print one line: lanes or snapshot, provider, region, image, ref
and hourly price. Relay each `orly burst:` line as it arrives. After it,
print the result lines and what was deleted.

## Credentials

- Never print a credential, pass one as a command-line argument, or write one
to a file.
- `burst.secrets` holds `op://` references. orly uses a value already in the
environment, or reads it with `op read`, on the caller. The value reaches
the machine only over the SSH session's standard input.
- `burst.secrets` holds `op://` references, read on the caller. A value
reaches the machine only over the SSH session's standard input, and never
reaches a snapshot.
- AWS credentials come from the caller's `aws` configuration or the job's
cloud login step. E2E credentials are a TIR API token's `E2E_API_KEY`,
`E2E_AUTH_TOKEN` and `E2E_PROJECT_ID` in the environment; MyAccount keys do
not work.
- A snapshot never receives a secret: setup and warm run without one.
login step. E2E needs a TIR API token's `E2E_API_KEY`, `E2E_AUTH_TOKEN` and
`E2E_PROJECT_ID`; MyAccount keys do not work.
57 changes: 30 additions & 27 deletions .opencode/skills/orly-burst/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
---
name: orly-burst
description: |
Run requested burst lanes on AWS or E2E Networks, or on the current runner,
and manage their snapshots. Use on "run acceptance on a burst box" or
Run requested burst lanes on AWS or E2E Networks, and manage their
snapshots. Use on "run acceptance on a burst box" or
"capture a snapshot". Paid runs need explicit authorization; missing PR
evidence does not authorize a run. Never run from a gate or hook.
---

# orly-burst

This skill owns one `orly burst` run, from choosing the lanes to reporting
the evidence. The lanes, setup, warm-up, secrets and result paths are the
repository's, declared in `.orly/orly.json`. One-time setup, settings and
costs are in orly's `.orly/docs/BURST.md`.
the evidence. Lanes, setup, secrets, results, region and image are the
repository's `burst` settings in `.orly/orly.json`. Setup and costs:
https://github.com/agentsfleet/orly/blob/main/docs/BURST.md

## When

Expand All @@ -24,32 +24,35 @@ costs are in orly's `.orly/docs/BURST.md`.

## Steps

1. **List the lanes.** Run `orly burst`. It prints the declared lanes and exits
2; pick only lanes it lists.
1. **List the lanes.** Run `orly burst`; pick only lanes it lists.
2. **Pick the provider.** Use `aws-spot` or `e2e` where outbound SSH on port
22 works, and the repository's burst workflow from an HTTP-only session.
Inside a CI job, `--provider here` runs the lane on the runner itself.
3. **Warm once.** A repository with no snapshot starts every lane cold from a
base image. Run `orly burst snapshot --provider <P>` after setup changes,
and `orly burst snapshot --prune --provider <P>` to keep the newest two.
4. **Run.** Run `orly burst <lane>... --provider <P>`, with `--ref <branch>`
for a ref other than the current branch. Lanes run in parallel, one machine
each. `--keep` leaves machines running for inspection, and they keep
billing.
5. **Report.** Quote every `orly burst: lane=…` summary line and the `total`
line verbatim, with the evidence directory. Only a numeric `exit=` is
evidence. `exit=interrupted`, `deadline`, `cancelled`, `unlaunched` or
`not_run` proves nothing about the code; report that lane as not run.
22 works and the caller stays on one network for the run. From an
HTTP-only session, start the repository's burst workflow instead.
3. **Warm once.** Capture `orly burst snapshot --provider <P>` after setup
changes, and prove a new provider with one capture before any lane.
`orly burst snapshot --prune --provider <P>` keeps the newest one.
4. **Run.** `orly burst <lane>... --provider <P> [--ref <branch>]`. Record
orly's PID from `$!`, and stop it only with `kill -INT <pid>`, so it
deletes what it rented.
5. **Report.** Quote every `lane=` line and the `total` line verbatim. Only a
numeric `exit=` is evidence; any other value means the lane did not run.

For a numeric failure, read `<evidence>/run.log` and name the failing step
and test. Name any 🔴 line's resource as left to delete by hand.

## Progress

Before a run, print one line: lanes or snapshot, provider, region, image, ref
and hourly price. Relay each `orly burst:` line as it arrives. After it,
print the result lines and what was deleted.

## Credentials

- Never print a credential, pass one as a command-line argument, or write one
to a file.
- `burst.secrets` holds `op://` references. orly uses a value already in the
environment, or reads it with `op read`, on the caller. The value reaches
the machine only over the SSH session's standard input.
- `burst.secrets` holds `op://` references, read on the caller. A value
reaches the machine only over the SSH session's standard input, and never
reaches a snapshot.
- AWS credentials come from the caller's `aws` configuration or the job's
cloud login step. E2E credentials are a TIR API token's `E2E_API_KEY`,
`E2E_AUTH_TOKEN` and `E2E_PROJECT_ID` in the environment; MyAccount keys do
not work.
- A snapshot never receives a secret: setup and warm run without one.
login step. E2E needs a TIR API token's `E2E_API_KEY`, `E2E_AUTH_TOKEN` and
`E2E_PROJECT_ID`; MyAccount keys do not work.
2 changes: 1 addition & 1 deletion .orly/orly.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"schema_version": 1,
"orly_version": "0.50.0",
"orly_version": "0.60.1",
"packs": [],
"commands": {
"conform": [
Expand Down
Loading
Loading