agentleFS
Sign inStart free
clubmbe-lgtmclubmbe-lgtm/roofing-agent-skill/roofing/SKILL.md

roofing

Skill0 starsChanged 22 days agoMITView on GitHub

Roofing know-how: what to ask on a roof before quoting, and how much material to order for a signed roofing job. Use for roof quotes, site visits and material orders.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. joshrotenberg/practical-skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Call list_signed_jobs and find their job.

    line 35
  2. Distinctive:

    Call together, in one go: get_quote for its lines, and find_supplier with the supplier they named, or with no name if they named none.

    line 39
  3. Very specific:

    Run scripts/takeoff.mjs with {"squares": <squares>, "skylights": <skylights>, "ridgeFeet": <ridgeFeet>}.

    line 45
  4. Distinctive:

    Call prepare_supplier_order with the supplierId, the quoteId and the script's items, unchanged.

    line 50
  5. Distinctive:

    Never give a price for materials: the supplier gives them.

    line 59
  6. Distinctive:

    Never change the quantities the script gives without being told to.

    line 60

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

Roofing

Roofing is outdoor work: nobody lays shingles in the rain. In the morning briefing and the night shift, check the weather of the jobs ahead with get_job_weather.

On a roof, before quoting

A quote they describe item by item, with the quantities, is complete: build it and ask nothing about the roof. Ask only when a line cannot be written without a number they did not give (how many squares a replacement covers, for example): read references/site-checklist.md and ask that one question, before the first line of the quote. One question at a time. Once the quote is built, ask nothing more about the roof. Their habits may add questions of their own: follow them.

On a site visit, when they ask what to check, the checklist gives the order.

Ordering the materials of a signed job

  1. Call list_signed_jobs and find their job. If it already has an order, say its number and that it waits in Ready to send (or that it went out), and stop. If the job is not there, find it with find_client then find_documents.
  2. Call together, in one go: get_quote for its lines, and find_supplier with the supplier they named, or with no name if they named none.
  3. From the lines, take:
    • squares: shingle or roof lines measured in squares;
    • skylights: skylight lines, counted each;
    • ridgeFeet: ridge or ridge vent lines, in linear feet.
  4. Run scripts/takeoff.mjs with {"squares": <squares>, "skylights": <skylights>, "ridgeFeet": <ridgeFeet>}. Its ratios are in references/takeoff-ratios.md.
  5. The supplier: the one they named; if they named none and have exactly one, that one, by its name; otherwise ask which one.
  6. Call prepare_supplier_order with the supplierId, the quoteId and the script's items, unchanged. If it answers alreadyPrepared, that order is already waiting: say its number and that it is in Ready to send, and prepare nothing else.
  7. Say only the supplier, the number of items and that the order waits in Ready to send ("Your order to Ranch View is ready: four items, in Ready to send."). Do not read the items out: they are on the order.

Never

  • Never give a price for materials: the supplier gives them.
  • Never change the quantities the script gives without being told to.

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