agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/vendor-renewals/SKILL.md

vendor-renewals

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 “Vendor Renewals”. A useful skill states the six fields from Skills and routines. Invoices, renewal notices, and vendor asks need a dated work list from mail and Drive — follow-ups stay unsent. Every row has a source link. No mail was sent. No invoice was marked paid. Unknown amounts are labeled unknown, not guessed. Work list grouped new / overdue /…

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 the work list to /workspace/vendor-inbox.md.

    line 26
  2. Distinctive:

    Every row has a source link.

    line 30
  3. Distinctive:

    Do not send chases. Do not pay invoices.

    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

Vendor Renewals

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Vendor Renewals”.

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

1. When to use it

Invoices, renewal notices, and vendor asks need a dated work list from mail and Drive — follow-ups stay unsent.

2. Required inputs and access

  • Gmail finance or vendor labels
  • Google Drive vendor or AP folder
  • Last week's vendor list if it exists in /workspace

3. Sequence of work

  1. Scan the window for invoices, renewal notices, and vendor payment asks. Skip newsletters.
  2. Extract vendor, amount, currency, due date, and a source link. Amounts not in the source stay unknown.
  3. Diff against last week's list into new, unchanged, overdue, and renewed-since-last-run.
  4. Draft one follow-up per overdue or missing-info vendor. Label DRAFT. Do not send.
  5. Write the work list to /workspace/vendor-inbox.md.

4. How to validate the result

Every row has a source link. No mail was sent. No invoice was marked paid. Unknown amounts are labeled unknown, not guessed.

5. What to return

Work list grouped new / overdue / upcoming, unsent follow-up drafts, action log of mail and Drive scanned.

6. What requires approval

Do not send chases. Do not pay invoices. Do not auto-renew or sign terms.

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.

Check your setup, free