Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 41551–41580 of 43303 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| facade-access-studyDavidCho1999/archaiflow-skillsWorks out how every part of a building's envelope will be reached after it is built: cleaned, inspected, repaired, and, for glass, replaced. Inventories the envelope by zone, holds candidate access methods against each one — reach from grade, rope descent, davits, a building maintenance unit, interior access — and reports what each method demands of the design now: roof space, structure, anchors, parapets, and ground kept clear. Trigger on "facade access", "how do we clean this", "window washing", "BMU", "davits", "rope access", "facade-access-study", "how does the glass get replaced", or a tall or complex envelope with no maintenance story. The zoning of the envelope and the demands table are the skill's method; every load, every regulation, and every equipment figure comes from elsewhere: anchor and davit loads are the structural engineer's, the rules for suspended access are regulatory text the user quotes, and reach figures come from the equipment's own data. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| facade-moduleDavidCho1999/archaiflow-skillsDivides elevation lengths and heights by a panel module and works the remainder into explicit options: resize every panel equally, absorb the leftover in end or corner panels, or take it in one feature bay, with the arithmetic for each and a check of where mullions land against the structural grid. Trigger on "panelize", "curtain wall module", "facade module", "mullion spacing", "panel layout", "facade-module", or an elevation length paired with a module. Every dimension comes from the user: elevation lengths and floor heights from their drawings, the module and any panel size limits from the manufacturer's literature, the grid from their structural plans. The skill never supplies a manufacturer's maximum panel size or a standard module from memory, does not size mullions or check wind load, does not judge thermal or glare performance, and does not choose between the options it lays out. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| fee-estimatorDavidCho1999/archaiflow-skillsEstimates a design fee four ways in parallel, as a percentage of construction cost, by area, as hourly against a cap, and as a lump sum, then splits the result by phase and by consultant and adds a reimbursables budget. Trigger on "fee estimate", "what should I charge", "design fee", "percent of construction cost", "lump sum or hourly", "consultant fee split", or a pasted program with a fee question. Works in any market. Every rate, percentage, phase split, consultant share, and any procurement cap comes from the user's own past projects, their contract, or the rule they name; the skill supplies the four methods and the comparison and never a benchmark figure from memory, since the published fee surveys are paywalled and cannot be quoted. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| fee-trackerDavidCho1999/archaiflow-skillsTracks a project's design fee in docs/practice/fees.md: the contract fee by phase, percent complete as you state it, earned fee computed from the two, invoices as issued and as paid, and the aging of what is outstanding, with the arithmetic shown. Trigger on "fee tracker", "how much have we billed", "earned vs billed", "unbilled", "outstanding invoices", "receivables", "invoice log", "fee-tracker", or an invoice to record. Percent complete is your judgment and the skill never estimates it; fees, invoice amounts, and dates come from you, in your currency, and nothing is recalled or benchmarked. Estimating a fee before there is a contract is fee-estimator's job; this starts when the contract is signed. It is a project record, not accounting: no tax, no ledger, no payroll costs. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| file-organizerDavidCho1999/archaiflow-skillsSorts a disorganized folder into a target tree, by writing a move plan you read and approve before any file is touched. Trigger on "organize this folder", "sort these files", "clean up this directory", "tidy this handoff folder", "file organizer", or a pasted path plus an organizing verb. Matches on filename, extension, size, and modified date, never on file contents. Finds duplicates by hash and routes them for review rather than deleting anything. Every run writes a plan first, executes only against the approved plan, and appends an audit log that a rollback can read backwards. The taxonomy is yours: the skill will draft one from what it finds, but it does not invent target folders you did not agree to. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| fit-out-studyDavidCho1999/archaiflow-skillsTests whether a tenancy works in a shell that is already there, which is a different problem from fitting a building on a site: the grid, the core, the servicing and the base building's own rules are fixed, and the programme has to bend around them. Establishes what is actually immovable before laying anything out, works the programme against the fixed points, and separates what the landlord provides from what the tenant does, since that boundary decides the budget and it is in a document nobody has read. Trigger on "fit out", "will this programme fit in this space", "tenant improvement", "test fit for a lease", "is this floor plate any good for us", "fit-out-study", or a floor plan of an existing building with a programme to place in it. Carries no areas, no ratios and no code requirements; areas come from the user and the lease's measurement basis from `area-measurement`. `test-fit` works a site under zoning limits; this works a shell under a lease. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| geotech-report-reviewDavidCho1999/archaiflow-skillsReads a geotechnical report from the architect's side: separates what was actually investigated from what was inferred between boreholes, pulls out every recommendation that becomes a design obligation, finds the conditions the report makes contingent on something happening later, and reports what it means for the building rather than for the foundation engineer. Trigger on "review the geotech report", "what does this soils report mean for us", "read the geotechnical recommendations", "borehole log review", "geotech-report-review", or a soils report handed over at the start of design. Carries no bearing values, no soil classifications and no design parameters; every figure comes from the report, quoted. It is not geotechnical engineering, does not verify a recommendation, and does not replace the geotechnical engineer, the structural engineer, or the Architect of Record. For one recommendation in plain English use `/explain-soils`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| go-no-go-reviewDavidCho1999/archaiflow-skillsScores a pursuit before the proposal is written, against the factors that actually predict whether a project is won and whether it is worth winning: the relationship, the client's decision process and funding, the competition, the fit with what the practice does, the fee and terms, and the capacity to deliver it. Records the decision and the reasoning so it can be read back against the outcome. Trigger on "go no go", "should we chase this", "pursuit review", "is this RFP worth answering", "go-no-go-review", or an opportunity raised for a decision. Carries no scoring weights and no thresholds; the practice sets what matters to it and what score means yes. It does not write the response — `rfp-response-builder` does — and does not decide. It records a decision somebody made, with the reasoning, so the next one is better informed. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| insurance-advisorDavidCho1999/archaiflow-skillsAssembles a project insurance program recommendation: which policy types the project needs, what each one covers, the wrap-up against traditional structure decision, and a checklist to take to a broker. Trigger on "insurance program", "what limits should we carry", "wrap-up insurance", "builder's risk", "professional liability limits", "insurance review", or a pasted project profile with a coverage question. Works in any market. Limits, required coverages, and certificate formats come from the user's contract and their broker; the skill supplies the structure of the decision and never a limit figure or a required coverage from memory. Produces a recommendation memo and a broker request checklist, and is not broker advice, a quote, or a binder. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| jurisdiction-profileDavidCho1999/archaiflow-skillsBuilds and maintains one file per project that records the limits a code sets, each with the clause it came from, so the checking skills stop asking for the same number on every run. Trigger on "jurisdiction profile", "set up the code profile", "record the code limits", "reuse my code values", "where do the limits come from", or a request to fill in or extend an existing profile. Works in any jurisdiction. The profile ships empty: every value is typed, pasted from the clause, or read out of a file the user names, and a row without a clause is marked as such rather than being treated as verified. Does not look a code value up, does not carry a default, and does not decide which code governs. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| leak-triageDavidCho1999/archaiflow-skillsWorks out what kind of water is appearing before anyone opens a wall: rain driven in, groundwater, a plumbing failure, condensation, or air-carried moisture, which look identical inside and have entirely different causes, owners and repairs. Reads the evidence that separates them — when it appears, what the weather was doing, whether it is warm or cold, whether it is clean, whether it stops — then narrows the source and names what would confirm it. Trigger on "there is a leak", "water is coming in", "a stain appeared on the ceiling", "is this condensation or a leak", "where is this water coming from", "leak-triage", or water appearing anywhere with no agreed cause. Carries no dew points, no rainfall figures and no test standards; every value comes from the building's own data or the tester. It diagnoses rather than repairs, does not apportion liability, and does not replace the enclosure consultant, the plumber, or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| leed-trackerDavidCho1999/archaiflow-skillsThis skill should be used when the user wants to build, update, or score a LEED v4.1 BD+C New Construction scorecard for an architectural project — by walking the credit list, declaring pursuit status (Yes / Maybe / No / N/A) for each credit, and summing points to predict certification level (Certified / Silver / Gold / Platinum). Trigger on "LEED scorecard", "LEED v4.1 score", "score this project for LEED", "LEED tracker", or pasted project program with sustainability goals. Reads bundled credit-by-credit point matrix from USGBC LEED v4.1 BD+C and outputs a CSV scorecard plus a markdown summary in `docs/leed/`. Does NOT make LEED eligibility judgments — the user declares what they intend to pursue; this skill organizes and scores. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| lessons-learnedDavidCho1999/archaiflow-skillsKeeps a lessons-learned log in docs/practice/lessons.md: what happened, what it cost or saved, why it happened as stated, and what to do differently, each entry tagged by phase and topic so it can be found when the situation recurs. Trigger on "lessons learned", "post-mortem", "what went wrong", "remember this for next time", "add a lesson", "lessons-learned", the close of a project, or the start of one, when the right move is reading the log rather than writing it. Lessons are recorded as you state them: the skill never invents a lesson, softens one, or assigns blame beyond what you said. At project start or before a phase it reads back the entries whose tags match, which is the entire return on writing them. A lesson is one incident; recurring patterns become visible because the log accumulates, not because the skill generalizes. | 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 |
| meeting-notes-cleanerDavidCho1999/archaiflow-skillsThis skill should be used when the user provides raw architectural project meeting notes — transcripts, STT output, .vtt/.srt files, or jotted text — and needs structured action items. Trigger on 'clean up meeting notes', 'meeting summary', 'process this transcript', or pasted multi-speaker content covering project decisions, schedule, or scope. Generates a structured meeting markdown in `docs/meetings/` and merges new To-dos into the project's `docs/todos.md`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| mep-reviewDavidCho1999/archaiflow-skillsReviews a mechanical, electrical, and plumbing drawing set against the architectural and structural drawings across eight coordination axes: shafts and risers, ceiling and plenum depth, equipment rooms, horizontal distribution, intake and exhaust, service entries, maintenance access, and document coordination. Trigger on "MEP review", "MEP coordination", "check the MEP set", "will the ducts fit", "plenum depth", "shaft coordination", "is there room for the equipment", or a shared MEP sheet with a fit question. The skill supplies no dimensions of its own: every clearance, depth, and area comes from the drawings or from you. Writes a dated review file and appends to a project index, with every unverified axis counted on the face of the review. Does not size equipment and does not replace the Engineer of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| minutes-readerDavidCho1999/archaiflow-skillsReads minutes written by somebody else — a contractor, a client, a project manager, a consultant — for the thing that matters and gets skipped: what they recorded about you. Minutes become the record if nobody objects within the period the contract or the covering note sets, so an action assigned to you that you did not accept, or a decision recorded that was not made, hardens into fact by silence. Trigger on "read these minutes", "the contractor sent minutes", "do we need to correct these", "did we agree to that", "minutes-reader", or minutes received from anybody else. Carries no contract terms; the objection period comes from the agreement or the minutes themselves. `meeting-notes-cleaner` turns your own raw notes into actions; this reads somebody else's finished document. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| mockup-reviewDavidCho1999/archaiflow-skillsReviews a built enclosure mockup, visual or performance, against the documents rather than against how it looks: establishes what this mockup was built to prove before anyone walks up to it, works the observation in a fixed order so the buildable-but-wrong conditions get seen, separates what the mockup demonstrated from what it merely did not contradict, and records what becomes the accepted standard for the rest of the work. Trigger on "mockup review", "reviewing the visual mockup", "performance mockup results", "what do we check at the mockup", "mockup punch list", "mockup-review", or a mockup photographed or described with a request for what to look at. Carries no tolerances, no test criteria and no acceptance thresholds; every one of those comes from the specification. It is not a test report, does not witness testing, does not accept or reject on the Architect's behalf, and does not replace the enclosure consultant or 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 |
| nyc-zoning-lookupDavidCho1999/archaiflow-skillsThis skill should be used when the user asks NYC-specific zoning questions and wants citation-backed answers from the NYC Zoning Resolution. Trigger on NYC zoning terms (FAR, lot coverage, setback, side/rear yard, sky exposure plane, height factor, dwelling unit factor, use group, accessory use), district codes (R1-R10, C1-C8, M1-M3), Special Districts (Special Hudson Yards District, Special West Chelsea District, etc.), or direct §X-XX citation requests. Downloads the official NYC ZR Complete PDF (~100 MB) on first use, caches a section-to-page outline at ~/.archtmpl/pdfs/nyc-zoning/, and answers each query by reading targeted pages and citing them as `§X-XX, p.N`. Operates with zero external dependencies — no Python, no embeddings, no API key beyond Claude Code subscription. Do NOT trigger for non-NYC zoning (use zoning-summary) or NYC Building Code questions (different document). | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| option-compareDavidCho1999/archaiflow-skillsBuilds a side-by-side comparison of design options in docs/design/options.md: the criteria you choose, one column per scheme, every cell filled from what you supply, and a tradeoff summary that stops short of picking the winner. Trigger on "compare options", "option A or B", "scheme comparison", "comparison matrix", "which scheme", "options for the client", "option-compare", or pasted facts about two or more schemes. Areas can be read from a space-program file where one exists, costs arrive from you or a cited benchmark, and empty cells stay visibly empty rather than estimated. Weighted scoring runs only if you supply the weights, arithmetic shown. The decision is the client's and yours; the skill structures it and does not make it. Renders to Word or PDF through aec-doc-gen when the meeting needs a handout. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| parti-studyDavidCho1999/archaiflow-skillsWorks the organizing idea of a scheme rather than its appearance: states the parti in one sentence, tests whether the plan actually obeys it, finds the places it breaks and asks whether each break is a compromise or a second idea competing with the first, and checks the parti against the constraints it has to survive. Generates alternatives only as different organizing ideas from the same constraints, never as variations of one. Trigger on "parti", "what is the organizing idea here", "is this scheme actually about anything", "concept diagram", "the plan feels arbitrary", "parti-study", or a scheme handed over with a question about what holds it together. Carries no formal vocabulary and no house style; the idea is yours and the skill tests whether the drawing keeps it. It does not critique the design — `design-critic` and `independent-critic` do that, deliberately separately — and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| passive-house-trackerDavidCho1999/archaiflow-skillsThis skill should be used when the user wants to track a Passive House project against the published certification thresholds — PHIUS+ 2021 (PHIUS, North American climate-specific targets) or PHI (Passive House Institute, fixed metric criteria — Classic / Plus / Premium). The user supplies modeled values (annual heating demand, annual cooling+dehumidification demand, source / primary energy, air leakage, peak loads, overheating frequency) from WUFI Passive or PHPP; the skill compares against published targets and emits a pass/fail-per-metric scorecard. Trigger on "PHIUS+ score", "Passive House tracker", "PHI Classic check", "compare WUFI/PHPP results to PHIUS+ targets", or pasted modeling outputs. Reads bundled PHIUS+ 2021 methodology + PHI fixed criteria from `references/` and outputs CSV + markdown summary in `docs/passive-house/`. Does NOT generate climate-specific PHIUS+ targets — user must fetch project-specific targets from the PHIUS portal (phius.org/phius-source-zero) before scoring. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| penetration-reviewDavidCho1999/archaiflow-skillsWorks through every penetration of a rated, acoustic or structural assembly and asks the three questions that get answered separately and should be answered together: what performance the assembly has to keep, what physically closes the hole, and whether a listed or tested system exists for that penetrant in that assembly. Builds the register across disciplines, since penetrations are made by trades who never see each other's drawings. Trigger on "penetration review", "firestopping check", "what closes this hole", "acoustic penetrations", "sleeve schedule review", "penetration-review", or an MEP set laid over the rated wall plan. Carries no listings, no ratings and no acoustic values; the required performance comes from your code analysis and every closure is a listed or tested system you cite. For the assembly's own continuity use `design-fire-barrier`; for air and water use `air-barrier-trace`. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| permit-trackerDavidCho1999/archaiflow-skillsKeeps one dated log of every approval a project has to obtain, from the agencies you name rather than from an assumed list: what each permit is, which agency issues it, what it depends on, who owns it, what has been submitted and when, every comment received and its response, and every expiry. Reads back what is on the critical path and what is waiting on somebody. Trigger on "permit tracker", "track the approvals", "what permits do we need", "permit log", "who owns this approval", "when does the permit expire", "permit-tracker", or a list of agencies named with a request to keep track of them. Carries no agency lists, no review durations, no fee schedules and no permit types; every one comes from the jurisdiction, because they differ between adjacent municipalities and change without notice. It does not file anything, does not predict a duration, and does not replace the expediter, the code consultant, or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| phasing-studyDavidCho1999/archaiflow-skillsWorks out the phasing for construction in and around a building that stays occupied: which functions must never close, where each one lives during each phase, the swing space that makes the moves possible, and the sequence that gets everyone home without a circular dependency. Builds the occupancy ledger, the move list, and the per-phase checklist of what must be true before a phase can start. Trigger on "phasing study", "occupied renovation", "how do we renovate without closing", "swing space", "decant plan", "phasing-study", or a renovation scope paired with functions that cannot stop. The sequencing logic is the skill's; every duration, cost, and code determination comes from elsewhere: the contractor owns means, methods, and the schedule, and whether egress and separations hold during each phase is a code and AHJ question this skill raises and never answers. It is the design-side plan that makes those conversations possible, not a construction schedule and not a logistics plan. | 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 |
| pipeline-trackerDavidCho1999/archaiflow-skillsKeeps one dated record of every pursuit the practice is chasing, from the first mention of a project — a call, a rumor, a client hint — through qualification, the go decision, the proposal, and the outcome, with the effort each pursuit consumed and the reason each loss happened. Leads every read-back with the pursuits consuming effort that have no go decision on record, because chasing without deciding is where business development money quietly goes. Trigger on "pipeline tracker", "what are we chasing", "track our pursuits", "proposals out right now", "did we ever hear back on that RFP", "what is our win rate", "pipeline-tracker", or a pile of pursuit emails handed over to make sense of. Carries no win-rate benchmarks, no hit-rate targets, and no probability weightings; the practice's history is the only pattern it reports. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| plan-check-response-builderDavidCho1999/archaiflow-skillsTurns a plan check or plan review comment set into a response matrix that answers every comment individually and on the record: splits comments that contain more than one question, sorts each into agreed, clarification, or disagreement, points every response at the specific sheet and detail that changed, and keeps the disagreements civil and evidenced because those are the ones that get read twice. Trigger on "plan check comments", "respond to the plan reviewer", "correction letter", "plan review response", "resubmittal response matrix", "plan-check-response-builder", or a set of reviewer comments pasted with a request to answer them. Carries no code positions of its own and never argues a clause from memory; every response either cites the drawing that changed or quotes the code text you supply. For a letter to the department rather than a comment matrix use `/draft-letter`; for tracking the submission itself use `permit-tracker`. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| plan-reviewDavidCho1999/archaiflow-skillsReads any floor plan you hand it and reports three things separately: what is drawn, what a plan of this kind should show and does not, and what the plan commits to without saying so. Works whatever the project type, whatever the phase, and whether the plan is yours, a consultant's, a client's previous architect's, or one found in a property listing. Trigger on "read this plan", "what do you make of this floor plan", "review this layout", "they sent us a plan", "plan-review", or a plan handed over with no particular question attached. Carries no dimensions and no standards; anything measured comes from what is on the drawing. `design-critic` judges a design, `code-compliance-review` audits against eight code axes, and `circulation-study` traces the journeys; this reads the drawing first, which is what the other three assume has happened. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |