Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 44611–44640 of 52046 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| airtightness-trackerDavidCho1999/archaiflow-skillsKeeps one dated record of a project's airtightness target from the moment it is written into the specification to the moment it is tested: what the target is and where it came from, which surface the enclosure boundary follows, every junction that has to be sealed and who owns it, every intermediate test and what it found, and every change that moves the number or the boundary. Trigger on "airtightness tracker", "blower door target", "track the air leakage requirement", "who owns this junction", "air barrier sign-off log", "airtightness-tracker", or an air leakage target named with a request to keep track of it. Carries no target values, no test standards and no unit conversions; the target, its units and its test method all come from the specification or the certification the project is chasing. It is not a test, does not model leakage, and does not replace the enclosure consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| alternative-means-builderDavidCho1999/archaiflow-skillsAssembles an alternative means and methods request as an argument rather than a form: establishes the prescriptive requirement that cannot be met and why, states the intent behind that requirement in the code's own words, sets out what is proposed and how it meets that intent, and gathers the evidence, the compensating measures and the conditions the applicant is willing to accept. Trigger on "alternative means and methods", "AMMR", "code modification request", "equivalency request", "we cannot meet this section, what now", "alternative-means-builder", or a prescriptive requirement named as unachievable with a request to make the case. Carries no code text, no precedent from other jurisdictions and no performance criteria; the requirement, its stated intent and any referenced standard all come from documents you supply. It does not approve anything, does not perform fire modelling or engineering analysis, and does not replace the fire protection engineer, the code consultant, or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| applicability-checkDavidCho1999/archaiflow-skillsTakes any requirement — a code section, a standard, an ordinance, a lease clause, an owner's design standard, a certification credit — and answers the question that comes before every other one: does this apply to this project at all. Works the six tests that decide it: is the document adopted or binding here, does the project fall inside its stated scope, has the trigger been met, does an exemption remove it, is this the edition that binds, and is something else more restrictive. Trigger on "does this apply to us", "is this section relevant", "do we have to comply with this", "they say this applies", "applicability-check", or a requirement quoted at you. Carries no text and no thresholds: every answer comes from the document you supply or the jurisdiction's own source. It does not interpret the requirement — `code-reader` takes it apart — and does not replace the code consultant or 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 |
| assembly-reviewDavidCho1999/archaiflow-skillsTakes any envelope assembly you are handed — a wall, a roof, a floor, a below-grade construction, from a consultant, a contractor, a manufacturer or an earlier phase of your own project — and reads it for what it is trying to do and where it does not. Locates the four control layers, checks each is continuous through the stack and has somewhere to go at the edges, names every layer with no job, and reports which direction it can dry. Trigger on "review this assembly", "is this wall build-up any good", "they sent us a section", "read this stack", "assembly-review", or any layered construction handed over for an opinion. Carries no R-values, permeance figures or code minimums; every value comes with the assembly or is marked missing. The `design-` assembly skills build one from demands; this reads one that already exists. It runs no arithmetic — `condensation-check` does — and does not replace the enclosure consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| bid-reviewDavidCho1999/archaiflow-skillsThis skill should be used during the bid phase when the user shares contractor bids, sub-bids, or proposal packages and wants them reviewed for completeness, scope alignment, qualifications, exclusions, alternates, and contract terms before owner award. Trigger on 'review these bids', 'bid review', 'check this proposal', 'compare bids', 'are these bids complete', 'bid leveling', 'bid analysis', 'qualifications and exclusions', or pasted bid content with award-decision intent. Generates a structured bid-review markdown in `docs/bids/` and appends to the project bid index. | 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 |
| calculation-readerDavidCho1999/archaiflow-skillsReads any calculation an architect is handed — structural, thermal, egress, drainage, load, acoustic — and checks the part an architect can and should check: the inputs, the assumptions, the standard it was worked to, and the version of the design it was worked from. The arithmetic is sealed by somebody and is not the architect's to verify; the inputs frequently describe a building that has changed since. Trigger on "read this calculation", "they sent calcs", "what did the engineer assume here", "is this calc still valid", "calculation-reader", or any calculation handed over. Carries no formulas, values or code limits. It verifies no arithmetic, has no engineering opinion, and does not replace the engineer of record or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| change-order-reviewDavidCho1999/archaiflow-skillsReviews a proposed change order against a fixed checklist and keeps a running change log in docs/construction/change-log.md. Trigger on "change order", "CO review", "change proposal", "PCO", "COP", "cost of this change", "change log", "change-order-review", or a pasted change proposal. The checklist asks whether the scope is described, the cost is broken down, the time impact is stated, the contractual basis is named, and the markup matches what the contract allows as you quote it. The skill supplies no judgment of fair price and no contract terms from memory; clause text comes from you or explain-aia, and price sanity is lookup-cost's separate job. The log carries every change with the running total against the original contract sum, arithmetic shown. Approval is the owner's and architect's act, not this skill's. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| change-order-trackerDavidCho1999/archaiflow-skillsKeeps one dated log of every change from the moment it is first raised, not from the moment it becomes a change order: records where each one came from, what instrument carried it, its cost and time position at every stage, and who it is sitting with, so that the work directed but not yet priced and the changes stalled between proposal and execution are both visible. Reports the running total against the contingency and the count of changes proceeding on direction alone. Trigger on "change order log", "track changes", "how much have we spent of the contingency", "what changes are outstanding", "work proceeding without a change order", "change-order-tracker", or a change register handed over to keep. Carries no cost data, no markup rates and no contract periods; all come from the contract and the proposals. It does not price, review, or negotiate a change — `change-order-review` does that for one — 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 |
| cite-checkDavidCho1999/archaiflow-skillsTakes a citation somebody handed you — in a review comment, a consultant's report, a contractor's letter, a manufacturer's claim, or your own earlier drawing — and checks the three things that make it usable: does the document exist and in which edition, does the section number resolve inside it, and does the text actually say what it is being used to say. Reports which of the three could be verified and which could not, rather than a yes or a no. Trigger on "is this citation right", "check this code reference", "they quoted a section at us", "does this clause say that", "cite-check", or a section number pasted with a claim attached. Carries no code text: verification comes from the document you supply or from the jurisdiction's own published source, never from recall and never from a search result that is not the publisher. It does not interpret the clause — `explain-code` does — and does not replace the code consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| civil-drawing-reviewDavidCho1999/archaiflow-skillsReads a civil set against the architectural set for the disagreements that only show up where the two meet: the finished floor against the finished grade at every door, the accessible route against the actual slopes, where utilities enter the building against where the risers are, and what the civil drawings assume about a building they were not drawn from. Reports every conflict with both values and rules on neither. Trigger on "review the civil drawings", "do the civil and architectural agree", "grading around the building", "utility entry coordination", "civil-drawing-review", or a civil set issued for coordination. Carries no slope limits, no cover requirements and no utility standards; accessibility limits come from the standard you quote and utility requirements from the utility. It is not civil engineering, does not check drainage design, and does not replace the civil engineer or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| client-translatorDavidCho1999/archaiflow-skillsThis skill should be used when the user has architecture/engineering technical text needing client-friendly rephrasing, OR a vague client wish needing translation into actionable technical options. Trigger on 'translate this for the client', 'put this in plain language', 'client-facing version', or pasted technical specs alongside client communication context. Generates a paired client-facing or technical document in `docs/client-comms/`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| climate-zone-mapperDavidCho1999/archaiflow-skillsRecords the climate or thermal zone a project sits in, then builds the envelope requirement scorecard component by component: roof, walls above and below grade, floors, slab edge, fenestration thermal, fenestration solar gain, and air leakage. Trigger on "what climate zone is this", "climate zone for this site", "envelope requirements for zone X", "energy code envelope scorecard", "climate-zone-mapper", or a pasted project address with an envelope question. Works with any energy code. The zone determination and every requirement value come from the user, typed, pasted, or read from a file they name. The skill never supplies a zone, an R-value, a U-factor, or a solar gain figure from memory or from web search, and any component without a supplied requirement is reported as unverified. Writes a CSV scorecard and a summary. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| closeout-checkDavidCho1999/archaiflow-skillsBuilds and tracks the closeout deliverables list in docs/construction/closeout.md: O&M manuals, warranties, test and inspection reports, record documents, spare parts and attic stock, training, each with the spec section that requires it. Trigger on "closeout", "closeout checklist", "O&M manuals", "warranties", "attic stock", "record drawings", "as-builts", "turnover package", "handover", "closeout-check", or the end of construction approaching. The list is built by reading the closeout requirements out of your spec book or typed by you; the skill never invents a deliverable a spec did not require. Received items are recorded with dates; the report leads with what is outstanding, by division. Whether the contract's closeout conditions are met is the architect's certification, not this skill's. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| code-analysis-builderDavidCho1999/archaiflow-skillsAssembles the code analysis block that goes on a permit set cover sheet, in six parts: occupancy classification, construction type, height and area with the allowable-area arithmetic shown, fire-resistance summary, means-of-egress summary, and accessibility statement. Trigger on "code analysis", "cover sheet code block", "G001 code block", "code-analysis-builder", "allowable area calc", "construction type check", or a pasted program with use, footprint, and sprinkler condition. Works in any jurisdiction. The user names the governing code and edition and supplies every value by typing it, pasting the clause or table row, or naming a file to read. The skill never supplies a code value from memory or from web search, and any line without a supplied value is printed as unverified rather than filled in. Does not replace the Architect of Record or the AHJ. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| code-analysis-readerDavidCho1999/archaiflow-skillsReads a code analysis produced by somebody else — a previous architect, a code consultant, a design-build partner, an earlier phase of your own project — and separates its three layers: the determinations it made, the arithmetic it showed, and the conclusions it stated without either. A code analysis is a chain of decisions and the first link, the occupancy classification, silently sets everything after it. Trigger on "read this code analysis", "we inherited a code summary", "is this code sheet still right", "the consultant sent their analysis", "code-analysis-reader", or a code analysis handed over. Carries no code text and no limits; every figure in it is checked for whether it was cited, not for whether it is correct. `code-analysis-builder` assembles your own; this reads one you were given. It does not verify compliance and does not replace the code consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| code-compliance-reviewDavidCho1999/archaiflow-skillsAudits a floor plan, schematic set, or program layout across eight egress and accessibility axes: use and occupant load, egress capacity and exit count, common path of travel, travel distance, exit access and door width, exit separation, accessibility, and fire-resistance assemblies. Trigger on "code review", "egress check", "life safety review", "plan check", "check egress", "accessibility check", "exit count", "travel distance", or a pasted plan with a code question. Works in any jurisdiction. The user names the governing code and edition and supplies each limit by typing it, pasting the clause, or naming a file to read. The skill never supplies a limit from memory or from web search. Writes a dated review file and appends to a project index, with every unverified axis counted on the face of the review. Does not replace the Architect of Record or the AHJ. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| code-readerDavidCho1999/archaiflow-skillsTakes a code section, a standard, or an ordinance you paste and pulls it apart into the separate requirements inside it: what each one applies to, what it demands, what triggers it, what exempts it, and which other section it hands off to. A single paragraph routinely contains four requirements and two exceptions, and reading it as one sentence is how half of it gets missed. Trigger on "read this code section", "what does this clause actually require", "pull the requirements out of this", "code-reader", or a pasted section that has to be worked through. Carries no code text and recalls no section: everything comes from what you paste or from the jurisdiction's own published source. `explain-code` puts one clause in plain English; this takes the clause apart into a table you can check a design against. It does not check the design — `compliance-check` does — and does not replace the code consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| compliance-checkDavidCho1999/archaiflow-skillsTakes a drawing and the code text that governs it and works through them together, one requirement at a time: what the text demands, what the drawing shows, and whether the drawing shows enough to tell. The third answer is the common one and it is the useful one, because a drawing that does not say is not a drawing that complies. Trigger on "does this drawing meet this code", "check this against the code text", "we pasted the section, now check the plan", "compliance-check", or a drawing and a quoted requirement handed over together. Carries no code text and recalls no limit: everything comes from what you paste. `code-compliance-review` audits a plan across eight fixed axes without being given text; this checks whatever text you bring against whatever drawing you bring. It does not interpret the clause, does not certify anything, and does not replace the code consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| condensation-checkDavidCho1999/archaiflow-skillsWorks out where water condenses inside a wall, roof, or floor assembly: the temperature at every layer boundary from the layer R-values and the design conditions, the dew point of the indoor air from its temperature and relative humidity, and which boundary is the first to fall below it. Then walks the layers in order of vapor permeance to flag a vapor-tight layer sitting on the cold side of the insulation, or two of them sealing the assembly from both directions. Trigger on "condensation check", "dew point in this wall", "will this assembly condense", "vapor retarder on the wrong side", "sheathing temperature", "condensation-check", or an assembly listed layer by layer with indoor and outdoor conditions. Every R-value, permeance, design temperature, and humidity comes from the user, out of manufacturer data, a climate data set, or the project's own documents; the skill supplies the heat-flow and psychrometric relations and never a material property. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| constructability-reviewDavidCho1999/archaiflow-skillsThis skill should be used when the user shares construction documents (DD set, 50%/100% CD, GMP set) and wants them reviewed through a constructor's lens — sequencing, tolerance stack-ups, MEP coordination, install access, lay-down logistics, temporary works, long-lead procurement, and phased operations. Trigger on 'constructability review', 'CM review', 'sequencing check', 'install access', 'crane reach', 'lay-down', 'long-lead', 'MEP coordination clearance', 'site logistics', or pasted CD context with build-feasibility intent. Generates a structured review markdown in `docs/constructability/` and appends to the project constructability index. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| consultant-drawing-reviewDavidCho1999/archaiflow-skillsReads a drawing from any consultant — structural, mechanical, electrical, plumbing, fire protection, civil, landscape, acoustic, kitchen, security — against the architectural set, from the architect's side. Checks the things that go wrong the same way whatever the discipline: the background it was drawn on, the grids and levels, what it lands in that has to stay clear, what it defers to somebody else, and where the two sets simply disagree. Trigger on "review the consultant drawings", "read this engineer's drawing", "do these agree with our plans", "they issued a set, what do we check", "consultant-drawing-review", or any consultant's drawing handed over. Carries no engineering values and checks no engineering. `mep-review`, `structural-drawing-review` and `civil-drawing-review` go deeper on those three; this is the one that works for the disciplines that have no skill of their own. It does not replace the engineers or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| contract-reviewDavidCho1999/archaiflow-skillsReads an owner-drafted or heavily amended professional services agreement for the provisions that shift risk onto the architect, working in the order the money moves rather than the order the document is written: standard of care, indemnity, limitation of liability, insurance, scope creep, payment and termination, ownership, and the dispute path. Reports each finding with the clause quoted, what it changes from the industry-standard position, whether it is insurable, and whether it is usually negotiable. Trigger on "review this contract", "the client sent their own agreement", "is this indemnity clause standard", "can we sign this", "contract-review", or an agreement handed over before signing. Carries no standard-form text and no legal positions; comparisons to a standard form require you to supply it. It is not legal advice and does not replace the attorney, the broker, or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| coordination-logDavidCho1999/archaiflow-skillsKeeps one dated log of conflicts between disciplines and follows each to the only ending that counts: both sets showing the same thing. Records which two documents disagree, what each says, who resolves it, and then the step everyone skips — whether the agreed answer reached both drawings and at which revision. Consolidates what the review skills find rather than leaving each discipline's findings in its own report. Trigger on "coordination log", "track the clashes", "did that conflict get fixed in both sets", "coordination issues", "coordination-log", or the output of a discipline review handed over to keep. Carries no positions of its own; the conflicts come from `mep-review`, `structural-drawing-review`, `civil-drawing-review`, `penetration-review` and `design-ceiling`. It does not resolve anything and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| cost-readerDavidCho1999/archaiflow-skillsReads any document with money in it — an estimate, a budget, a cost plan, a supplier quote, a contractor's proposal, a client's own number — and does the part an architect can do without being an estimator: establish what it covers, what it excludes, what it assumed, and what date it is on. Those four decide almost every argument about a price, and none of them require checking the arithmetic. Trigger on "read this estimate", "what does this quote actually include", "the budget came back", "is this number comparable", "cost-reader", or any priced document handed over. Carries no rates, no benchmarks and no cost data; `/lookup-cost` quotes a benchmark with its source and `senior-cost-estimator` gives judgement. It checks no arithmetic, prices nothing, and does not replace the estimator, the contractor, or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| curtain-wall-submittal-reviewDavidCho1999/archaiflow-skillsReads a curtain wall or unitised facade submittal package as a system rather than as a set of sections: checks that the drainage and pressure-equalisation strategy is coherent through every joint, that the thermal break line is continuous and lands where the wall's insulation does, that movement is provided for at stack joints and anchors, that the tested system and the drawn system are the same system, and that the interfaces to every adjoining assembly have an owner. Trigger on "curtain wall shop drawing review", "unitised facade submittal", "review the glazing submittal", "stack joint detail review", "is the thermal break continuous", "curtain-wall-submittal-review", or a facade shop drawing package handed over for comment. Carries no performance criteria, no test values and no tolerances; all come from the specification and the test reports, quoted. It reviews and comments, does not stamp or approve, and does not replace the facade engineer or 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 |