agentleFS
Sign inStart free
ozkilimozkilim/runway/skill/SKILL.md

runway

Skill2 starsChanged 3 months agoMITView on GitHub

Show current cloud credit and spend numbers - how much credit was granted, how much is used, how much is left, when it expires, and where the money went. Use whenever the user asks about cloud spend, cloud costs, credits, AWS/Azure/GCP spend, "how much have I spent", "how much is left", "what's my burn", "what's my runway", "am I running out of credits", or invokes /runway. Pulls live from the cloud billing APIs - never answer these from memory or from earlier numbers in the conversation, they go stale.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. JustinPerea/nebula-nodes★ 23same name
    2. udaysharmadev/Skills★ 12same name
    3. WellApp-ai/skills★ 8same name
    4. s3ntin3l8/runway-ai-usage-tracker★ 3same name
    5. aalishan001/opencockpit★ 2same name
    6. runapi-ai/runway★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use that interpreter by absolute path — it is the project venv with the cloud SDKs installed.

    line 16
  2. Distinctive:

    Add at most one line underneath, and only when something genuinely warrants it:

    line 34
  3. Very specific:

    Never invent a runway figure unless asked.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

runway

Pulls live credit and spend facts from configured cloud providers and presents them.

Run it

{{RUNWAY_PYTHON}} {{RUNWAY_REPO}}/runway.py

Use that interpreter by absolute path — it is the project venv with the cloud SDKs installed; the system python may lack them. Never shell out to aws, az, or gcloud; the SDKs are used deliberately.

Flags:

  • (none) — formatted table. This is what you show the user.
  • --json — raw payload. Use when the user asks a follow-up you need to compute from (per-service totals, month-over-month comparisons, "what changed").
  • --check — credentials smoke test, no cost data.
  • --provider aws — limit to one provider (aws, azure, or gcp).

Presenting the result

Show the output and stop. The user wants numbers, not narration. Do not restate figures that are already on screen, do not summarise the table back, do not add a preamble. The script emits facts only — no runway estimates, no burn rate, no thresholds, no verdicts — and that terseness is deliberate at both layers.

Add at most one line underneath, and only when something genuinely warrants it:

  • cash > $0 in any month — credits ran short and real money was charged.
  • A month far outside the others — an outlier against the baseline. Name the service responsible from by_service_90d.
  • warning field set — e.g. credits_as_of predates billing-data retention, so the balance may be overstated.

Otherwise say nothing. Refunds and tax in other are already marked inline in the table and need no comment.

Never invent a runway figure unless asked. If asked, give a range and state the assumption — burn is volatile.

Config

~/.runway/config.yaml, mode 600. Holds credentials plus, per provider: credits (grant total), credits_as_of (the date that figure was true), expires.

credits_as_of is load-bearing: remaining is computed as credits − drawdown since credits_as_of. Getting it wrong silently produces a wrong balance. No cloud exposes a remaining-credit balance via API, so credits and expires are typed in from the console's Credits page. If the user says their grant changed, update that file rather than adjusting numbers by hand.

Setup / adding a provider

Per-provider walkthroughs live in {{RUNWAY_REPO}}/docs/setup/ (aws.md, azure.md, gcp.md). If the user wants to hook up a new cloud account, follow the relevant doc step by step. Providers render as not configured until enabled and never block the others.

Errors

Failures are per-provider and never abort the run. Known causes are reported with a hint attached. Secrets are scrubbed from all error output — keep it that way.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free