drawing-quantity-extract
Skill390 starsChanged 54 days agoMITView on GitHub
Extract countable FF&E or luminaire instances from supplied drawings with position-level evidence. Use for plan quantities or symbol counts; not area takeoffs, product specs or cross-source reconciliation.
In this repository63 other files it gives its agents.
- docs/agents.mdAGENTS.md
- skills/project/templates/AGENTS.mdAGENTS.md
- skills/project/templates/CLAUDE.mdCLAUDE.md
- agreementSkill
- architecture-knowledgeSkill
- color-palette-generatorSkill
- csv-to-sifSkill
- demographics-analysisSkill
- environmental-analysisSkill
- epd-compareSkill
- epd-parserSkill
- epd-researchSkill
- epd-to-specSkill
- ffe-spec-bookSkill
- invoiceSkill
- learnSkill
- lighting-report-extractSkill
- master-scheduleSkill
- meeting-minutesSkill
- mobility-analysisSkill
- normaSkill
- norma-supportSkill
- nyc-acrisSkill
- nyc-bsaSkill
- nyc-dob-permitsSkill
- nyc-dob-violationsSkill
- nyc-hpdSkill
- nyc-landmarksSkill
- nyc-property-reportSkill
- occupancy-calculatorSkill
- product-auditSkill
- product-cut-sheetSkill
- product-data-cleanupSkill
- product-data-importSkill
- product-enrichSkill
- product-image-processorSkill
- product-librarySkill
- product-matchSkill
- product-pairSkill
- product-researchSkill
- product-spec-bulk-fetchSkill
- product-spec-pdf-parserSkill
- product-url-clipSkill
- projectSkill
- proposalSkill
- receiveSkill
- resize-imagesSkill
- schedule-quantity-reconcileSkill
- sif-to-csvSkill
- site-historySkill
- site-visit-reportSkill
- skill-makerSkill
- slide-deck-generatorSkill
- spec-writerSkill
- studio-feedbackSkill
- studioSkill
- tasklistSkill
- timetrackerSkill
- tool-catalogSkill
- workplace-programmerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Before acting, read the host contract and declaration (skill:drawing-quantity-extract), using only referenced profiles from the catalog.
- Distinctive: line 19
Use the host adapter and available native tools or ordinary task-specific code.
- Distinctive: line 25
Verify actual source access.
- Very specific: line 28
Read native evidence procedures.
- Distinctive: line 37
Keep observed label counts and any evidenced revised allocation distinct.
≈ “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.
Files
/as:drawing-quantity-extract — Count drawing instances
Before acting, read the host contract and
declaration (skill:drawing-quantity-extract), using only referenced profiles
from the catalog. Requirements do not grant access.
<!-- architecture-studio:harness-compatibility -->Use the host adapter and available native tools or ordinary task-specific code. Operation names identify semantic procedures, not installed functions. No Arch Studio runner, package installation or executable reconstruction is required. Existing exact authorization persists; ask only for material missing information or permission.
Input: exact supplied drawing files/revisions, building/floor/phase scope and requested tags/types. Output: unadopted instance ledger, scoped counts and coverage/exclusion evidence. No record owner is changed. Read owning instructions for project work; one-off files do not require initialization.
- Verify actual source access. Freeze document hashes and physical page list; record printed sheet IDs separately. Keep drawing types/revisions distinct. Missing access calls a real host grant or produces a precise handoff; never substitute another workspace.
- Read native evidence procedures. Extract text and
coordinates using the native
pdf_evidence.extractprocedure; use host OCR/visual inspection for image-only labels. Save page-sized checkpoints. A legend index is local to its drawing, not a global type ID. - Build one ledger row per candidate label/symbol at its document/page/bounding box. Classify each as instance, legend, note or unresolved. Count repeated identical tags at distinct positions; inspect duplicate text/OCR layers and overlapping boxes before excluding any. Preserve exclusions and reasons. Associate rooms only using visible boundaries or explicit schedule evidence, not nearest-label proximity.
- Inspect each scoped page against the ledger. Reconcile revision callouts and same-page schedules; never count note text as furniture or silently relabel instances because a revision note proposes it. Keep observed label counts and any evidenced revised allocation distinct. If methods disagree, report unresolved counts and the source regions; an approximate number is not verified quantity.
- Apply
drawing_quantities.summarizewith native computation under the complete evidence procedure. It counts supplied classified instances only. Retain the actual result plus the host's per-page coverage and visual evidence; neither a successful command nor unique-tag count proves full extraction. - Return counts by exact tag and scope, source locators, excluded/unresolved instances and pages not
inspected. Save only requested derived outputs, fresh-read them and preserve originals. Route
comparison with inventories or other drawings to
/as:schedule-quantity-reconcile; route adopted record changes to/as:master-schedule, under its authorization. Never certify procurement totals.
Current document placement
Save only authorized derived outputs and verify their actual content, source hashes and complete requested scope. Inline answers and one-off files need no project setup or adoption. For a requested registered project report, resolve confirmed coordinates using the receive-owned native documents.resolve/register semantics in the workspace model, including its complete document/register mutation sequence. Find existing records with documents.query; never guess a folder. This conditional handoff does not authorize schedule or library changes.
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
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.

