Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 41341–41370 of 43669 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| drawing-diffDavidCho1999/archaiflow-skillsCompares two revisions of the same sheet or drawing set and reports what actually changed. Trigger on "what changed between these revisions", "compare Rev C and Rev D", "diff these drawings", "did they change anything", "check this against the last issue", or two pasted PDF paths of the same sheet or set. Matches pages by the sheet number printed in the title block rather than by page order, diffs extracted text to catch dimension, note, and tag edits, overlays the rendered pages to find linework that moved, then reads the changed regions to describe them. Flags changes carrying no revision cloud, and clouds carrying no change. Writes one report per comparison to `docs/drawing-diffs/`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| drawing-logDavidCho1999/archaiflow-skillsMaintains a drawing issue log in docs/drawings/log.md: every sheet in the set, its current revision, and every dated issuance with its purpose. Trigger on "drawing log", "issue log", "sheet log", "revision log", "what rev is", "when did we issue", "drawing register", "drawing-log", or a request to record that a set went out. The sheet list can be seeded from a drawing-set-bookmarker index or typed; revisions and issue dates come from you, never from a guess. Superseded sheets are marked, not deleted, so the log answers what was in force on any past date. It records what was issued to whom; the cover sheet for a package is create-transmittal's job, and what changed inside a sheet is drawing-diff's. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| drawing-readerDavidCho1999/archaiflow-skillsReads an architectural drawing PDF and answers questions about it: a single sheet, a full set, a redline, a record drawing, a shop drawing, or a detail. Summarises, finds a sheet, explains a detail, lists disciplines, or pulls a callout. Trigger on "read this drawing", "what is in this set", "summarize this drawing", "show me sheet X", "what is on this sheet", or a pasted path to a drawing PDF. For specifications, codes, contracts, and reports use doc-reader instead. Detects the drawing type, asks what is wanted before reading at length, and hands off to schedule-extractor, drawing-set-bookmarker, or drawing-checklist when one of those fits better. Never reports a dimension or a note it did not read off the sheet. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| drawing-set-bookmarkerDavidCho1999/archaiflow-skillsThis skill should be used when the user has a multi-sheet architectural drawing-set PDF (typically 50–300 sheets) with no bookmarks or a flat/incorrect bookmark tree, and wants a properly bookmarked PDF plus a CSV sheet index. Trigger on "bookmark this drawing set", "add bookmarks to this PDF", "tabulate sheets", "make a sheet index", or a pasted path to a multi-sheet drawing PDF. Reads each page's title block via vision, extracts sheet number/name/discipline, groups by discipline per US National CAD Standard, and writes the bookmarked PDF + index to `docs/drawing-sets/`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| drawing-standards-auditDavidCho1999/archaiflow-skillsSweeps a whole drawing set for the conventions that decide whether it can be read: whether the sheet index matches the sheets, whether every reference lands on something that exists, whether the title block is complete and consistent, whether symbols and abbreviations are used as the legend defines them, and whether the same information appears twice with two answers. Reports by frequency so the systematic problems separate from the isolated ones. Trigger on "drawing standards audit", "check the set for consistency", "do the references resolve", "title block check", "is this set ready to issue", "drawing-standards-audit", or a set handed over before issue. Carries no office standard, no layer convention and no line weight table; the standard comes from your office or the project's own set. It reviews conventions rather than content — `drawing-checklist` covers what a phase should contain and `spec-review` covers the book. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| markup-readerDavidCho1999/archaiflow-skillsReads a marked-up drawing — a redline, a scanned sketch over a print, a PDF with comments, a photograph of a drawing somebody wrote on — and turns it into a numbered list of what each mark asks for, who it is for, and whether it can be acted on as drawn. Separates the marks that instruct from the marks that ask, and flags every mark whose meaning cannot be determined, because a guessed markup is worse than an unread one. Trigger on "read this redline", "they marked up the drawing", "what does this markup say", "turn these comments into a list", "markup-reader", or a marked drawing handed over. Carries no conventions: what a colour or a symbol means is the office's or the marker's, and it is asked rather than assumed. `drawing-diff` compares two issued revisions; this reads what somebody wrote on one. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| model-health-auditDavidCho1999/archaiflow-skillsAudits a building model for the practices that decide whether it stays usable: what the model is actually for and whether it is being built to that, whether geometry is modeled or drafted over, whether the data the project committed to deliver is present and consistent, what is warning or duplicated, and whether the file can be shared with consultants without an explanation. Reports by frequency and separates what will get worse from what is merely untidy. Trigger on "model health check", "audit this Revit model", "why is the model so slow", "is the model ready to share", "BIM standards audit", "model-health-audit", or a model handed over before an exchange. Carries no software-specific counts, no thresholds and no office BIM standard; the standard and the delivery requirements come from your BEP or your office. It reviews practice rather than drawings — `drawing-standards-audit` reads the sheets. It does not replace the BIM manager or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| photo-readerDavidCho1999/archaiflow-skillsReads any photograph an architect ends up with — a site visit, an existing building, a defect somebody wants explained, a phone picture from a client, a product on a shelf — and separates what is visible from what is inferred, because a photograph is the most persuasive and least complete document on a project. Establishes when and where it was taken and which way the camera faced before reading anything, since a photograph with no location is evidence of nothing. Trigger on "read this photo", "what am I looking at here", "the client sent a picture", "is this a problem", "photo-reader", or an image handed over with a question. Carries no dimensions and measures nothing from an image. It diagnoses nothing: a photograph of a stain is not a diagnosis, and `leak-triage` takes it from there. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| punch-listDavidCho1999/archaiflow-skillsMaintains a project punch list in docs/construction/punch-list.md. Trigger on "punch list", "punch item", "snag list", "deficiency list", "defect list", "punch walk", "punch-list", or a pasted site visit report whose observations should become tracked items. Each item carries a location, a description, the responsible trade, the date raised, its source, and a status that separates completed from verified, because a contractor marking work done is not the same as the architect seeing it done. The skill never invents an item, a responsible party, or a completion; what it was not told stays open. Feeds on create-site-visit-report output. It does not decide substantial completion and does not certify anything; those are contract acts. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| rfi-trackerDavidCho1999/archaiflow-skillsKeeps one dated RFI log and reads what the log says that no single RFI does: every RFI with who owns it, when it arrived, when the contract required an answer, when the answer went, and how it was classified, plus the running counts that reveal a pattern — a sheet generating a stream of questions, a contractor sending already-answered ones, a consultant consistently late, a set of clarifications quietly accumulating into a change. Trigger on "RFI log", "RFI tracker", "how many RFIs are open", "are we late on RFI responses", "which drawings are generating RFIs", "rfi-tracker", or an RFI register handed over to keep. Carries no response periods and no classifications of its own; the contract sets the turnaround and each RFI's class comes from whoever answered it. It does not answer RFIs — `/draft-rfi-response` does — and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| rfi-writerDavidCho1999/archaiflow-skillsThis skill should be used when the user provides an informal construction-site question — drawing/spec discrepancies, dimension conflicts, missing details — and needs a formal Request for Information (RFI) document filed in the project. Trigger on phrases like "make an RFI", "draft an RFI", "send this as an RFI", or pasted site questions implying transmittal to design consultants. Generates a numbered RFI markdown file in `docs/rfis/` and updates the project's RFI log. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| schedule-builderDavidCho1999/archaiflow-skillsBuilds a drawing schedule of any type — door, window, finish, room, wall type, equipment — by settling the column set before any row is filled, since the columns are what the schedule is and adding one later means revisiting every row. Takes the items from your drawings or model, fills only what you supply, marks every gap rather than defaulting it, and checks the finished schedule against the plans for items scheduled but not drawn and drawn but not scheduled. Trigger on "build a door schedule", "window schedule", "finish schedule", "room data sheet", "wall type schedule", "make a schedule from these drawings", "schedule-builder", or a request to assemble any drawing schedule. Carries no default column sets, no hardware sets, no fire ratings and no product data; the columns come from your office standard and every value comes from you. For extracting a schedule that already exists in a PDF use `schedule-extractor`. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| schedule-extractorDavidCho1999/archaiflow-skillsThis skill should be used when the user has a drawing-set PDF containing one or more tabular schedules (door schedule, window schedule, room finish schedule, equipment schedule) and wants the rows pulled out as a normalized CSV for cross-checking, takeoff, or import into Excel/Revit. Trigger on "extract the door schedule", "pull the finish schedule", "tabulate this schedule", "schedule to CSV", or a pasted PDF path with mention of a schedule type. Reads schedule pages via vision, normalizes columns to the AIA / NCS Section A6 conventions, and writes CSV + markdown preview to `docs/schedules/`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| schedule-reviewDavidCho1999/archaiflow-skillsReads a contractor's construction schedule from the design team's side rather than as a planner: finds every activity that depends on the architect, the consultants or the owner and checks whether the durations allowed match the contract, traces the critical path to see what actually controls the end date, looks for the logic that makes a delay claim inevitable, and separates what is a genuine concern from what is only unfamiliar. Trigger on "review the contractor's schedule", "CPM schedule review", "is this baseline reasonable", "submittal durations in the schedule", "schedule update review", "schedule-review", or a programme submitted for comment. Carries no durations, no productivity rates and no float conventions; the contract sets the review periods and the schedule specification sets the rules. It is not planning software, does not re-plan the work, does not opine on means and methods, and does not replace the scheduler or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| set-readerDavidCho1999/archaiflow-skillsReads a complete drawing set rather than a drawing: works out what phase it actually is regardless of what the title block claims, what is in it and what is missing for that phase, which disciplines are present and at what revision, how the set is organised, and what somebody receiving it would have to ask about first. Built for the set that arrives from somewhere else — a previous architect, a client, a design-build partner, a project you are taking over. Trigger on "read this set", "what have we been given", "we are taking over this project", "is this set complete", "set-reader", or a whole set handed over. Carries no standards and no phase definitions; completeness is judged against what the set itself claims to be. `drawing-reader` reads one sheet, `plan-review` reads a plan, `drawing-standards-audit` sweeps for conventions. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| spec-outline-builderDavidCho1999/archaiflow-skillsBuilds a specification's section list from the drawings rather than from the last project's table of contents: walks the set for every material, system and scope shown, maps each to a section, then runs the check in both directions — work drawn with no section, and sections carried forward with no work. Marks each section's status so the book's real completeness is visible rather than implied by a full-looking contents page. Trigger on "what spec sections do we need", "build the table of contents", "spec outline", "do we have a section for this", "spec-outline-builder", or a drawing set handed over before the book is written. Carries no section numbers, no titles and no master list; numbering comes from the format your office uses and `/lookup-csi` finds one number. For auditing a book that exists use `spec-review`; for one paragraph use `/draft-spec-snippet`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| spec-reviewDavidCho1999/archaiflow-skillsThis skill should be used when the user shares a project specification — full spec book, individual CSI MasterFormat sections, or specs paired with drawings — and wants it audited for division completeness, drawing-spec coordination, prescriptive vs performance balance, basis-of-design products, reference-standard currency, AHJ amendments, section-internal completeness, and OPR alignment. Trigger on 'spec review', 'spec audit', 'CSI review', 'check this spec section', 'are the specs and drawings coordinated', 'reference standards', 'basis of design', 'or equal language', or pasted spec content with completeness intent. Generates a structured review markdown in `docs/spec-reviews/` and appends to the project spec-review index. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| submittal-log-builderDavidCho1999/archaiflow-skillsReads a project specification section by section, pulls out every submittal each one calls for, classifies it, and assembles a submittal log ready to issue. Trigger on "build submittal log", "submittal log", "extract submittals from spec", "shop drawing log", "submittal register", "submittal-log-builder", or a pasted specification section list. Works with any specification format and any contract. The user supplies the spec text by pasting it, naming files to read, or pointing at an indexed PDF, and supplies the review durations from their own contract. The skill never invents a submittal, never carries a list of typical submittals, and never assumes a review duration: every row traces to a line in the user's spec, and anything it could not find is listed as a gap rather than filled in. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| submittal-reviewDavidCho1999/archaiflow-skillsThis skill should be used during construction administration when the user shares a contractor submittal — shop drawings, product data, samples, or mockup documentation — and wants it reviewed for conformance with the contract documents. Trigger on 'review this submittal', 'shop drawing review', 'check this product data', 'submittal log', 'is this approved', 'spec compliance check', 'AIA G712', or pasted submittal content paired with CA-phase context. Generates a structured submittal-review markdown in `docs/submittals/` and appends to the project submittal log. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| value-engineering-advisorDavidCho1999/archaiflow-skillsSorts a cost-cutting list against an issued design into accept, accept with an alternate, and block, with the reasoning written out per item across design intent, performance, lifecycle cost, schedule, risk transfer, and reversibility. Trigger on "VE review", "value engineering", "review this VE list", "where can we cut", "cost reduction options", "VE round 2", or a pasted contractor proposal with substitutions and savings figures. Works with any contract and any specification format. Performance requirements come from the user's own specification and contract; the skill supplies the sorting method and never a code threshold or a performance value from memory. Produces a recommendation memo, not a directive. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| adjacency-matrixDavidCho1999/archaiflow-skillsBuilds a programme adjacency matrix from movement and constraint rather than from stated preference: takes the room list, asks for each pair what actually travels between them and how often, separates a required adjacency from a desired one and from a required separation, then reads the finished matrix for the rooms that want to be everywhere at once and the conflicts that no plan can satisfy. Trigger on "adjacency matrix", "bubble diagram", "which rooms need to be near each other", "programme relationships", "adjacency-matrix", or a room list handed over with a request for how it should be organised. Carries no adjacency conventions for any building type, because who has to be near whom is the client's operation and not a rule. Reads a room list from `space-program` where one exists and does not duplicate its area tracking. It does not lay out a plan and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| area-measurementDavidCho1999/archaiflow-skillsSettles the question every project answers three times and differently: which area standard is being used, where its boundary is drawn, and what counts toward it. A building has a zoning floor area, a code floor area, a gross and a net for programming, and a leasable area, and each is measured by a different rule from a different document. Records one basis per purpose with its source, reconciles the figures that result, and reports the difference rather than resolving it into one number. Trigger on "which area standard", "gross versus net", "what counts as floor area here", "our areas do not match the lease", "BOMA measurement", "area-measurement", or two area figures that disagree. Carries no standards, no definitions and no factors; each comes from the document you quote. It measures nothing itself and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| brief-reviewDavidCho1999/archaiflow-skillsThis skill should be used when the user shares a project brief, RFP, or Owner's Project Requirements (OPR) and wants it interrogated for unstated assumptions, gaps, contradictions, and missing constraints before design work proceeds. Trigger on 'review this brief', 'check the RFP', 'unpack this brief', 'analyze the OPR', 'is this brief complete', or pasted brief text accompanied by a request to evaluate completeness. Generates a structured brief review markdown in `docs/briefs/` and appends to the project brief index. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| budget-reconciliationDavidCho1999/archaiflow-skillsWorks the conversation every project has and most handle badly: the design costs more than the budget. Establishes first what each number actually is, since a client's budget often excludes things an estimate includes and half the gap disappears there. Then sorts the ways of closing it into the four that behave differently — less area, less quality, less scope, more money — and prices each move in what it costs the design rather than only in what it saves. Trigger on "we are over budget", "the estimate came back high", "what do we cut", "value engineering at design stage", "the client's budget will not cover this", "budget-reconciliation", or an estimate set against a budget with a gap between them. Carries no costs, no rates and no benchmarks; every figure comes from the estimator, the contractor, or a source you name. `value-engineering-advisor` sorts a cost-cutting list during construction; this is the design-stage conversation. It does not estimate and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| circulation-studyDavidCho1999/archaiflow-skillsStudies circulation as a set of named journeys rather than as corridor area: establishes who moves through the building and why, traces each journey door to door, finds the places two journeys cross that should not, and reports where a route depends on something being unlocked, staffed or explained. Separates the circulation a plan needs from the circulation it happens to have. Trigger on "circulation study", "trace the routes", "do these flows cross", "clean and dirty separation", "public and staff routes", "wayfinding through the plan", "circulation-study", or a plan handed over with a question about how people move through it. Carries no corridor widths, no efficiency ratios and no separation requirements; egress widths and distances belong to `design-egress` and accessibility to the accessibility standard you quote. It does not lay out a plan and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| daylight-studyDavidCho1999/archaiflow-skillsChecks each room's depth against how far sidelight can reach it, from the window head heights, room depths, and glazing areas the user supplies: daylit depth by a stated convention, glazing-to-floor arithmetic held against a code minimum the user quotes, and the no-sky line when a facing building is in the way. Trigger on "daylight study", "how deep does daylight reach", "is this room too deep for daylight", "no-sky line", "daylight-study", or room depths paired with window head heights. The depth convention and the obstruction geometry are the only things this skill supplies itself; every dimension, glazing area, and code minimum comes from the user. It is a plan-stage tool for comparing layouts, not a daylighting simulation: no daylight factor, no illuminance, no glare, no LEED credit documentation, all of which come from a model. Exterior shadows on neighbors belong to shadow-study; energy-code glazing checks belong to test-glazing. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-additionDavidCho1999/archaiflow-skillsWorks an addition or a renovation at the place it actually gets decided: the joint between new and existing. Settles the relationship the new work takes to the old, then works the six things that cross the joint — structure, envelope, services, levels, fire separation and finishes — and separately establishes what the work triggers in the existing building, since a change of use or a threshold crossed can require upgrades to parts of the building nobody was touching. Trigger on "addition", "extension", "renovation", "how does the new bit meet the old", "does this trigger an upgrade", "matching the existing", "design-addition", or new work proposed against a building that already exists. Carries no code thresholds and no structural values; existing-building provisions are jurisdictional text you quote and capacity is the engineer's. Read `existing-conditions-survey` first: an addition designed against unverified dimensions is designed twice. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-bathroomDavidCho1999/archaiflow-skillsLays out a domestic bathroom or ensuite from the two things that actually constrain it — where the waste can run and which way the door swings — rather than from the fixtures. Works ventilation, the wet area and its waterproofing, storage, and the reach and clearance around each fixture, and separates what is fixed by the building from what is a choice. Trigger on "bathroom layout", "ensuite", "can we move the toilet", "powder room", "where does the shower drain go", "design-bathroom", or a bathroom to be laid out or moved. Carries no clearances, no fixture dimensions and no ventilation rates; each comes from the code you quote, the accessibility standard, or the fixture's own data. For an accessible restroom to a standard use `design-accessible-restroom`; for commercial fixture counts use `/count-plumbing-fixtures`. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-coreDavidCho1999/archaiflow-skillsAggregates the pieces of a building core (elevator shafts, stairs, toilets, mechanical and electrical shafts and rooms) from dimensions the user supplies, applies the user's own wall-and-circulation factor, and reports total core area and core-to-floor-plate ratio against the user's benchmark, showing every step. Trigger on "core sizing", "how big is my core", "core-to-floor ratio", "core efficiency", "design-core", or a floor plate paired with a list of core components. Every dimension comes from the user: shaft sizes from manufacturer cut sheets, stair footprints from the user's stair layout, room sizes from the user's plans, the grossing factor and the target ratio from the user's own benchmarks. The skill never supplies a typical shaft size, fixture count, or target ratio. It does not decide elevator count (the elevator consultant's traffic analysis does), does not check stair or fixture code compliance, and is not a substitute for the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-criticDavidCho1999/archaiflow-skillsThis skill should be used when the user shares an architectural project (concept text, plans, sections, renderings, references) and asks for critique, feedback, or a second opinion. Trigger on 'design critique', 'review this design', 'critique this', 'second opinion', or when context implies the user wants challenge over validation. Generates a structured critique markdown in `docs/reviews/` and appends to the project review index. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |