agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/reconcile-expenses/SKILL.md

reconcile-expenses

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 “Reconcile Expenses”. A useful skill states the six fields from Skills and routines. A week's expenses must be matched to receipts and policy, with exception drafts — totals that reconcile back to the source. Summary total equals the source system total or the difference is explained. Every exception cites a policy section. Weekly summary, exception table with policy cites, unsent follow-up…

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Do not send follow-ups. Do not change reimbursements.

    line 39

≈ “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

Reconcile Expenses

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Reconcile Expenses”.

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

1. When to use it

A week's expenses must be matched to receipts and policy, with exception drafts — totals that reconcile back to the source.

2. Required inputs and access

  • Expense system export or connector
  • Finance inbox / attached receipts
  • Written expense policy (the signed one, not memory)

3. Sequence of work

  1. Total the source system. That number is the denominator.
  2. Match receipts. Flag missing categories and policy exceptions with policy citations.
  3. Draft one follow-up per owner. Do not send.
  4. Return summary, exceptions, drafts, and a reconciling total.

4. How to validate the result

Summary total equals the source system total or the difference is explained. Every exception cites a policy section.

5. What to return

Weekly summary, exception table with policy cites, unsent follow-up drafts, action log.

6. What requires approval

Do not send follow-ups. Do not change reimbursements. Do not approve spend.

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