Skip to content
cccskills
FreePublished on GitHub

drawing-quantity-extract

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md4.0 KB
  • host-contract.json1.1 KB
  • README.md310 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

/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.

  1. 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.
  2. Read native evidence procedures. Extract text and coordinates using the native pdf_evidence.extract procedure; 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.
  3. 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.
  4. 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.
  5. Apply drawing_quantities.summarize with 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.
  6. 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.

The English summary is being prepared. Showing the original description.

AlpacaLabsLLC/skills-for-architects385Updated Oct 21, 2026

Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work.

The English summary is being prepared. Showing the original description.

AlpacaLabsLLC/skills-for-architects385Updated Oct 21, 2026

Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks. Use for color schemes or brand colors.

The English summary is being prepared. Showing the original description.

AlpacaLabsLLC/skills-for-architects385Updated Oct 21, 2026

Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.

The English summary is being prepared. Showing the original description.

AlpacaLabsLLC/skills-for-architects385Updated Oct 21, 2026

Research population, income, age, housing, and employment around a site. Use for census, demographic, or local-market questions tied to a location.

The English summary is being prepared. Showing the original description.

AlpacaLabsLLC/skills-for-architects385Updated Oct 21, 2026

Research climate, sun, flood, seismic, soil, contamination, and topography for a site. Use for environmental site analysis or hazard questions tied to a location.

The English summary is being prepared. Showing the original description.

AlpacaLabsLLC/skills-for-architects385Updated Oct 21, 2026

See all skills by AlpacaLabsLLC

Report a problem with this skill