agentleFS
allenlee0430allenlee0430/allenlee-lab-skills/.claude/skills/build-reimbursement-packets/SKILL.md

build-reimbursement-packets

Skill0 starsChanged 5 months agoMITView on GitHub

Extract, reconcile, and package lab receipts, invoices, purchase orders, travel expenses, and grant-expenditure evidence into checked spreadsheets and ordered PDF packets. Use for University of Toronto reimbursements, vendor reconciliation, expense reports, PO matching, missing-document audits, and expenditure reporting.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never guess unreadable amounts.

    line 11
  2. Distinctive:

    Use the spreadsheet skill to build a ledger with formulas and subtotals.

    line 13
  3. Distinctive:

    Verify arithmetic, currency conversion source and date, tax treatment, duplicates, and packet completeness.

    line 14
  4. Very specific:

    Read references/ledger-schema.md before creating the workbook.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Build reimbursement packets

  1. Confirm claimant, trip or purchase purpose, date range, funding source, currency policy, and required institutional template.
  2. Inventory source files without mixing 60_Personal_Legal_Finance into lab expenses.
  3. Extract vendor, date, description, subtotal, tax, total, currency, payment method, invoice or receipt number, PO, and source filename.
  4. Never guess unreadable amounts. Flag OCR uncertainty and duplicate-looking charges.
  5. Match PO, invoice, proof of payment, and reimbursement row. Identify missing links.
  6. Use the spreadsheet skill to build a ledger with formulas and subtotals. Use the PDF skill to order source documents to match ledger rows.
  7. Verify arithmetic, currency conversion source and date, tax treatment, duplicates, and packet completeness.
  8. Deliver the ledger, ordered packet, exception list, and totals by funding source.

Read references/ledger-schema.md before creating the workbook.

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.