Skip to content

DavidCho1999/archaiflow-skills / bundles/construction-admin/skills/doc-reader

doc-reader

Verified

Reads a non-drawing project PDF and answers questions about it: a specification, a code excerpt, a contract, a consultant report, or correspondence from an authority. Summarises, locates a clause, extracts values, or lists comments, and cites section and page for every claim it makes. Trigger on "read this spec", "what does this document say", "summarize this report", "find clause X", "what is the authority asking for", or a pasted path to a non-drawing project PDF. For drawing sheets use drawing-reader instead. Detects the document type, asks what is wanted before reading at length, and never answers from what a document of that kind usually says. Writes a per-read summary that points back at the source.

FileKindSize
SKILL.mdskill md9.3 KB
references/_provenance.mdmarkdown3.4 KB
references/document-types.mdmarkdown6.6 KB
references/read-patterns.mdmarkdown5.3 KB

references/read-patterns.md

View on GitHub
# User-Intent → Read-Pattern Mapping

When the user drops a non-drawing AEC PDF and states an intent, this file maps the intent to the right handling — direct vision read or delegation to a specialized archtmpl skill.

> **Format note**: This file is read by Claude after the user has stated their intent. The "Direct read" rows describe what to do inline; the "Delegate to" rows tell Claude to stop and recommend a specialized skill instead.

---

## Section / clause location ("find clause 3.10" / "show me §1006.2")

User asks: "Find AIA A201 §9.8", "Quote IBC §1006.2.1", "What's in CSI 08 14 16 Part 2".

**Direct read**:
1. Inventory the PDF (page count, TOC).
2. Use TOC to locate the requested section.
3. Render that page; quote the requested clause / section verbatim.
4. Cite: page number + native reference (AIA §X.Y.Z, IBC §X.Y.Z, CSI section + Part).
5. Confidence: `high` for verbatim text.

---

## Document summary ("summarize this spec / report")

User asks: "Summarize this spec section", "Give me a 5-bullet rundown of the geotech", "Brief me on this contract".

**Direct read**:
1. Read first 3 pages (cover, TOC, executive summary if present).
2. Sample 1–2 pages from each major section.
3. Output: 3–7 bullet summary covering scope, key findings, key requirements, key recommendations.
4. Cite: page number + section name for each bullet.

---

## Verbatim quote ("quote what the code says")

User asks: "Quote what IBC §1004.5 requires", "What does AIA A201 §3.10 say", "Read me the warranty clause".

**Direct read**:
1. Locate the section (using TOC or page-by-page scan).
2. Quote the section verbatim, with section header + body.
3. Cite: page number + native reference.
4. Confidence: `high`.

**Anti-pattern**: paraphrasing code or contract text. Always verbatim, or flag it.

---

## Numerical extraction ("what's the bearing capacity" / "what's the EUI")

User asks: "What's the soil bearing capacity from the geotech", "Pull the EUI from the energy report", "What's the seismic design category".

**Direct read**:
1. Locate the section containing the value (TOC + targeted scan).
2. Extract the value verbatim with units.
3. Cite: page number + table/figure number.
4. Confidence: `medium` (vision-approximated table cells).
5. Tell the user to verify against the source PDF for legally-binding values.

**Delegate to specialist when applicable**:
- Seismic design parameters → `seismic-design-category-tracker` (when shipped).
- Energy modeling output → may be input to `passive-house-tracker`.
- Code compliance values → may be input to `code-analysis-builder`.

---

## AHJ comment tabulation ("list every plan-check comment")

User asks: "Tabulate the AHJ comments", "What does NYC DOB want", "Make a tracking sheet from this letter".

**Direct read**:
1. Read the letter end-to-end.
2. Identify comments (numbered list or paragraph-by-paragraph).
3. Output a CSV: `comment_id, agency, comment_text, status, action_required, sheet_affected, due_date, source_page`.
4. Cite: page + comment number.
5. Confidence: `high` for verbatim comment text, `medium` for inferred status / sheet-affected.

---

## Scorecard / tracker input ("here's the LEED export, score it")

User pastes / drops a sustainability rating system scorecard export.

**Delegate based on rating system**:
- LEED export → `leed-tracker`.
- PHIUS portal export → `passive-house-tracker`.
- ADA scoping → `ada-tracker`.

Stop. Do not partially score inline.

---

## Spec section → submittal list ("what submittals does this spec require")

User asks: "What submittals does this spec section require", "Pull the Part 1 submittals article".

**Delegate to `submittal-log-builder`**.

If not shipped: do a direct read of Part 1 — Article on Submittals (typically `1.04` or `1.05`) and quote verbatim. Output a CSV: `submittal_id, type (shop drawing / product data / sample / mock-up / closeout), description, response_required (Action / Information), source_clause`.

---

## Plain-English translation ("translate this for the contractor")

User asks: "Make this spec readable for a contractor", "Translate this code section for a client", "Plain-English-ify this contract clause".

**Delegate to `client-translator`**. Stop.

If not installed: `npx archtmpl@latest --skill client-translator`.

---

## Compliance verification ("does this spec meet ADA")

User asks: "Does this spec meet ADA", "Is this contract clause GSA-compliant", "Verify code compliance".

**Out of scope**. The skill quotes; specialized trackers verify. Redirect:
- ADA compliance → `ada-tracker`.
- LEED / WELL / Passive House → corresponding trackers.
- IBC code analysis → `code-analysis-builder`.

---

## Compare versions ("AIA 2007 vs 2017")

User asks: "Compare this contract to the 2007 version", "What changed between IBC 2021 and 2024".

**Out of scope here**. Tell the user to supply BOTH versions; current skill handles one PDF at a time.

---

## Default — unrecognized intent

If the user's intent doesn't match any of the patterns above:

1. Ask the user to clarify what they want.
2. Offer 3 candidate handlings (e.g. "I can: (a) summarize the whole document, (b) quote a specific section, (c) extract key values. Which?").
3. Wait for confirmation before reading.

Never read 500 pages of a spec book without explicit user authorization — vision reads are token-heavy.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall