agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/operations/quote-drafting-from-notes/SKILL.md

quote-drafting-from-notes

Skill0 starsChanged 4 months agoMITView on GitHub

Turn rough notes — a photo, a voice memo, a few scribbled lines — into a clean, structured quote with scope, line items, and a total. The owner captured a job in the field — a quick note, a photo, a memo — and needs it turned into a quote they can send.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Use the owner's real pricing from the brain, not made-up numbers.

    line 22
  2. Distinctive:

    Add the terms: what's included, what's not, how long the quote holds, payment schedule.

    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

Draft a Quote From Messy Notes

Field notes are messy on purpose; the owner was busy. Turn them into a real quote: the scope in plain terms, line items with quantities and prices, a total, and the terms — structured so it's ready to send.

The technique

  • Pull the job out of the mess — what's being done, where, what condition things are in. Reconstruct the scope from the notes and photos.
  • Break it into line items: each piece of work with a quantity and a price the owner can stand behind.
  • Use the owner's real pricing from the brain, not made-up numbers. If a price is missing, flag it — don't invent it.
  • Add the terms: what's included, what's not, how long the quote holds, payment schedule.
  • Total it, write a one-line cover in the owner's voice, and stage it for the owner to check before it goes out.

Do this, not that

Do: From "roof, 20sq, some rot on the north side, customer wants gutters too" → a quote with tear-off (20 sq), decking replacement (north section, flagged: confirm sq footage), new gutters (linear ft), each priced from the owner's list, totaled, with a 'valid 30 days' line.

Don't: Either hand back the raw notes reformatted with no prices, or invent prices the owner never set — both leave the owner doing the actual quoting or, worse, sending a number they can't honor.

Why this works

The gap between a captured job and a sent quote is where deals go cold — the owner means to write it up tonight and it's still sitting there Friday. Turning the notes into a ready-to-send quote closes that gap. Pulling real prices from the brain (and flagging the ones you don't have) is what keeps it honest: a fast quote that quotes the wrong number is worse than a slow one.

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.