agentleFS
youdcodeyoudcode/open-company/.agents/skills/quote-invoice/SKILL.md

quote-invoice

Skill2 starsChanged 53 days agoMITView on GitHub

Prepares a quote or an invoice draft with exact totals (tools/invoice.mjs). Only the human issues it, from the Finance tab of the live office. Use when the human types "quote for <client>", "invoice <client>" or "invoice from quote".

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write the document as JSON in workspace/tmp/doc.json:

    line 13
  2. Very specific:

    If billing.md is not filled (legal name, address, legal mentions), tell the human: nothing can be issued before that.

    line 20
  3. Distinctive:

    Never say it was sent.

    line 23

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

Quote or invoice

Role: finance (follow roles/finance.md).

  1. Collect the facts, never invent them: client legal name and address (from the lead, the account file or the human), what is sold, quantities, unit prices (from workspace/company/profile.md or the human), VAT rate if different from workspace/company/billing.md. Ask for anything missing.
  2. Write the document as JSON in workspace/tmp/doc.json: {"type":"quote","client":{"name":"...","address":"...","registration":"<SIREN or company number>","vat_id":"","lead":"<lead id>"},"lines":[{"description":"...","qty":1,"unit_price":450}],"service_date":"YYYY-MM-DD","operation":"services","notes":"..."} For an invoice, service_date (when the work was delivered) and operation (services, goods or both) are required in France; the client's registration number too for business clients.
  3. node tools/invoice.mjs new --file workspace/tmp/doc.json --as finance. The script computes the totals. Never compute or round them yourself.
  4. For an invoice from an accepted quote: node tools/invoice.mjs from-quote <quote id> --as finance.
  5. If billing.md is not filled (legal name, address, legal mentions), tell the human: nothing can be issued before that. Do not fill legal mentions yourself.
  6. Tell the human: the draft is in the Finance tab, "Issue" gives it its number, then print it to PDF. Never say it was sent.

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.