agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/cloud-bill-note/SKILL.md

cloud-bill-note

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Cloud Bill Note”. A useful skill states the six fields from Skills and routines. A cloud invoice or usage notice arrived and the owner needs a note of what moved, with recommendations — not console edits. Period total matches the invoice or the gap is explained. No line item is invented. No console, budget, or reservation change happened. Bill note: total,…

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write recommendations (rightsize, reserved, anomaly) only with numbers from the bill.

    line 24
  2. Distinctive:

    Write the note to /workspace/cloud-spend.md.

    line 26
  3. Distinctive:

    Do not change cloud accounts, budgets, or reservations.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Cloud Bill Note

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Cloud Bill Note”.

A useful skill states the six fields from Skills and routines.

1. When to use it

A cloud invoice or usage notice arrived and the owner needs a note of what moved, with recommendations — not console edits.

2. Required inputs and access

  • Gmail invoices or billing notices
  • Google Drive cost export if attached
  • Last period's note if it exists in /workspace

3. Sequence of work

  1. Pull this period's invoice or export. The billed total is the denominator.
  2. Diff against the last note if present. Name services that moved and by how much.
  3. Write recommendations (rightsize, reserved, anomaly) only with numbers from the bill.
  4. Draft questions for the owner. Do not change the cloud account.
  5. Write the note to /workspace/cloud-spend.md.

4. How to validate the result

Period total matches the invoice or the gap is explained. No line item is invented. No console, budget, or reservation change happened.

5. What to return

Bill note: total, movers, recommendations, owner questions, action log.

6. What requires approval

Do not change cloud accounts, budgets, or reservations. Do not pay the invoice.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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.