agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/operations/vendor-invoice-categorization/SKILL.md

vendor-invoice-categorization

Skill0 starsChanged 4 months agoMITView on GitHub

Read a vendor invoice and log it to the right account so the books stay clean and tax time isn't a scramble. A vendor bill or receipt comes in and needs to land in the books under the correct category.

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:

    Every invoice has a right home in the books.

    line 16
  2. Distinctive:

    Read what the invoice is for, not just who it's from — a hardware-store receipt could be materials, tools, or an office supply, and the …

    line 20
  3. Distinctive:

    When the category is actually unclear, flag it for the owner instead of guessing — a wrong category quietly compounds into a tax-time mess.

    line 24

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

Categorize a Vendor Invoice

Every invoice has a right home in the books. Read what it's actually for, match it to the correct account, and log it with enough detail that it makes sense at tax time without a second look.

The technique

  • Read what the invoice is for, not just who it's from — a hardware-store receipt could be materials, tools, or an office supply, and the category depends on the line items.
  • Match it to the right account in the owner's chart of accounts. Use the categories that already exist; don't invent a new one for a one-off.
  • Split it when it's mixed — if one receipt covers materials and equipment, split the lines rather than dumping it all in one bucket.
  • Note the job or customer when it's billable, so it can be tied back to revenue later.
  • When the category is actually unclear, flag it for the owner instead of guessing — a wrong category quietly compounds into a tax-time mess.

Do this, not that

Do: "Supplier invoice $1,240: $1,100 shingles → Materials (job: Henderson, billable); $140 nail gun → Tools & Equipment. Split logged. The $90 'misc' line is unclear — flagged for you."

Don't: Dump the whole $1,240 into "Supplies" because it came from a supplier — mixing a capital tool purchase with billable job materials, which throws off both job costing and the deduction.

Why this works

Miscategorized invoices don't hurt today — they hurt in April, when the books don't reconcile and the deductions are wrong. Logging each one to the right account as it comes in keeps the books clean continuously, ties costs back to the jobs that earned the revenue, and means tax time is a review instead of a forensic reconstruction. Flagging the unclear ones beats a confident wrong guess that nobody catches for months.

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.