Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 44581–44610 of 51908 skills
| Skill | Stars | Updated | Works with | Status | 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 |
| post-occupancy-evaluationDavidCho1999/archaiflow-skillsGoes back to a finished building and finds out what actually happened: what people do that the design did not expect, what they have changed, what they work around, and what performs differently from what was intended. Separates observation from opinion and from measurement, keeps the visit away from the questions that only produce politeness, and ends by naming who each finding is for, since a finding nobody receives is a visit nobody should have made. Trigger on "post occupancy", "POE", "how is the building working", "go back and see how it is used", "soft landings", "post-occupancy-evaluation", or a building in use with a question about it. Carries no benchmarks and no satisfaction scales; targets come from what the project set and measurements from whoever takes them. `lessons-learned` records what a project taught the practice; this finds out what the building is doing. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| precedent-critiqueDavidCho1999/archaiflow-skillsCritiques the user's scheme through lenses extracted from reference projects the user supplies, instead of a generic rubric. Trigger on "critique this through these precedents", "hold my scheme against these references", "critique this like these projects", "precedent-critique", or a scheme shared alongside two or more admired projects. The user supplies both sides: their own scheme (concept text, plans, sections, images) and material for each reference (project descriptions, photographs, drawings, published texts). The skill derives three to five lenses from the supplied material, confirms them with the user, then reads the scheme through each lens. It never characterizes a firm or a project from memory: a name without material stops the run. Divergence from the references is reported and questioned, never scored. It does not design, does not rank, and does not replace the designer's judgment or a design review. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| precedent-finderDavidCho1999/archaiflow-skillsThis skill should be used when the user describes a project concept, program, atmosphere, or site condition and needs architectural precedents. Trigger on 'find references', 'similar projects', 'precedents for', or natural-language descriptions paired with phrases like 'something with this feeling'. Caches a curated precedent list in `docs/precedents/` (one file per topic) and updates the project precedent index. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| program-readerDavidCho1999/archaiflow-skillsReads any brief or programme document — a client's schedule of accommodation, a spreadsheet from a user group, a consultant's brief, a previous architect's programme — and establishes what its numbers actually are before anybody designs against them: which are measured, which are standards, which are wishes, what area basis they are on, whether the total is the sum of the parts, and what the document counts that a building would not. Trigger on "read this brief", "they sent a schedule of accommodation", "what does this programme actually say", "is this area realistic", "program-reader", or a brief handed over. Carries no area standards and no benchmarks; the basis comes from the document or from `area-measurement`. `brief-review` interrogates a brief for gaps and contradictions; this reads one for what its figures rest on, and it runs first. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| project-trackerDavidCho1999/archaiflow-skillsKeeps one dated log of a project's issues, decisions, risks, and action items in docs/project/tracker.md. Trigger on "project tracker", "decision log", "issue log", "risk register", "action items", "track this", "log this decision", "what did we decide", "who owns this", "project-tracker", or when meeting notes produce action items worth keeping past the meeting. Every entry carries a date and a person; closed items move to a closed section rather than being deleted, so the log is also the project's history. The skill never invents a status, an owner, or a deadline. What it was not told, it records as unassigned and says so. Feeds on meeting-notes-cleaner output and is what generate-weekly-report reads. Not a construction schedule and not a CA log; RFIs and submittals have their own logs. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| project-website-builderDavidCho1999/archaiflow-skillsTurns a project deck PDF, renders, site photos or drawing images into one web page that reads on a phone and can be sent as a link. Uses only the words and numbers in the files or typed in the chat, lists what it found and asks how each part should be shown (full width or grid, side by side or slider, one scroll or one section per screen) before building, keeps PDF drawings sharp when zoomed, and writes the page as one index.html that a drag-and-drop host can put online. Trigger on "make this a website", "project website", "send the deck as a link", "shareable project page", "a page the client can open on their phone", "project-website-builder", or files attached with a request for something a client can open. It does not write project copy, and it does not put anything online by itself. | 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 |
| rfp-response-builderDavidCho1999/archaiflow-skillsBuilds an RFP or RFQ response around the evaluation criteria rather than around the practice's usual material: pulls every requirement and every question out of the document into a compliance matrix, follows the issuer's structure and numbering exactly, and checks before submission that every requirement has an answer and every page limit and format rule is met. Trigger on "respond to this RFP", "RFQ response", "build the proposal response", "do we answer everything in this RFP", "rfp-response-builder", or a solicitation handed over to answer. Carries no boilerplate and no standard firm material; everything comes from the practice's own content. For a federal qualifications package use `sf330-builder`; to decide whether to respond at all use `go-no-go-review` first. It does not decide the fee and does not replace the principal. | 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-readerDavidCho1999/archaiflow-skillsReads any engineer's or consultant's schedule — mechanical equipment, plumbing fixtures, electrical panels, lighting, fire protection devices, structural members — and translates it into the architectural consequences: what has to fit somewhere, what needs a room, what needs access, what needs a route, what lands on a wall or a ceiling, and what weighs something the structure has to carry. Trigger on "read this equipment schedule", "what does this mechanical schedule mean for us", "they sent a schedule", "schedule-reader", or any consultant's schedule handed over. Carries no dimensions, capacities or clearances; every figure comes from the schedule or the product data. Not to be confused with `schedule-review`, which reads a contractor's construction programme — a different document entirely. `explain-panel-schedule` goes deeper on one electrical panel. It does not check the engineering and does not replace the engineers or the Architect of Record. | 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 |
| section-reviewDavidCho1999/archaiflow-skillsReads any section — a sketch section, a building section, a wall section, a consultant's, an inherited one — for the thing a section exists to settle: whether the vertical dimensions actually add up, and what has been drawn around rather than resolved. A section is the only drawing where the structure, the services, the ceiling, the floor build-up and the envelope have to agree in the same line, which is why it is the drawing most often cut where the conflicts are not. Trigger on "read this section", "does this section work", "they sent a wall section", "check this section", "section-review", or any section handed over. Carries no dimensions or depths; anything measured is read off the drawing at its stated scale. `plan-review` reads a plan and `assembly-review` reads a stack; this reads the drawing where the vertical dimensions meet. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| security-design-reviewDavidCho1999/archaiflow-skillsReads a plan for security as a property of the layout rather than as equipment added later: who is meant to be where and how the building tells them, where somebody can be unobserved, where the boundary between public and controlled actually falls, and what happens to all of it after hours when the staff who make it work have gone home. Works the design questions first, because a camera is what gets bought when the plan did not answer them. Trigger on "security review", "CPTED", "is this plan secure", "where do we put the access control", "how do we secure this after hours", "security-design-review", or a plan for a building with a controlled boundary. Carries no standards, no ratings and no requirements; the client's security policy, the operator's rules and any regulation come from you. It does not design systems, does not do threat assessment, and does not replace the security consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| seismic-lookupDavidCho1999/archaiflow-skillsRecords the seismic design parameters a project needs before structural design starts, one at a time, with the source of each: mapped accelerations, site coefficients, design accelerations, the design category, and the long-period transition. Trigger on "seismic design category", "what is the SDC for this site", "seismic parameters", "site class", "design spectral accelerations", "seismic-lookup", or a pasted site location with a seismic question. Works in any jurisdiction. The parameters come from the user's own hazard tool, code maps, or geotechnical report, and the site class comes from the geotechnical engineer. The skill never supplies a seismic value from memory or from web search, and reports every parameter it could not source as a gap. Writes a CSV and a summary. | 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 |
| sf330-builderDavidCho1999/archaiflow-skillsAssembles a federal qualifications submission section by section, and does the part that decides the score: selecting the example projects and writing them so that each one demonstrates a specific evaluation criterion rather than being included because it is good work. Builds the team organisation against the projects named, keeps résumés consistent with the projects they claim, and checks every section against the solicitation's own instructions before submission. Trigger on "SF330", "federal qualifications package", "which projects go in Section F", "architect-engineer qualifications", "sf330-builder", or a federal solicitation handed over to answer. Carries no form instructions and no evaluation criteria; both come from the current form and the specific solicitation, which override any general guidance. It does not replace the principal, who signs. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| shadow-studyDavidCho1999/archaiflow-skillsComputes solar altitude and azimuth from latitude, date, and time, then the shadow a massing casts: length, direction, and, if the user supplies the distance, whether it reaches a neighboring line. Trigger on "shadow study", "how far does the shadow go", "solstice shadows", "will my building shade the neighbor", "shadow-study", or a massing height paired with a date and a place. The solar geometry is computed from published astronomy formulas, the one thing this skill works out itself; everything else comes from the user: heights, distances, grades, and any shadow criteria the jurisdiction enforces. Flat ground is assumed unless the user supplies grades. It is a design-stage tool for comparing massing options, not a submission-grade shadow study, and it does not know which hours or open spaces any city protects. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| site-access-studyDavidCho1999/archaiflow-skillsStudies everything that has to reach a site and finds where two of them want the same frontage: lists every arrival — people, cars, deliveries, refuse, fire apparatus, utilities, moving vans, coaches — traces each from the public way to where it has to end up, and reports the conflicts, the curb cuts that will not be granted, and the frontage the project has already spent. Trigger on "site access study", "how does the truck get in", "where does the fire access go", "can we get a curb cut here", "loading and refuse access", "site-access-study", or a site plan with a question about how anything reaches it. Carries no dimensions, no turning radii, no fire apparatus requirements and no curb cut standards; all come from the jurisdiction, the fire department and the utility. It does no traffic engineering and no swept path analysis, and does not replace the civil engineer or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| site-analysisDavidCho1999/archaiflow-skillsReads a site for the things that will decide the building rather than for a set of diagrams: what is fixed and cannot move, what the approach and the ground do to where a building can sit, where the sun and the weather come from, what the neighbours and the context require, and what has to be found out before anything is committed. Separates observation from inference throughout, and ends with the list of what is still unknown and who answers it. Trigger on "site analysis", "read this site", "what does the site tell us", "first visit to the site", "site-analysis", or a new site with nothing decided yet. Carries no climate data, no zoning limits and no soil values; `climate-zone-mapper`, `seismic-lookup`, `wind-snow-lookup` and `zoning-summary` collect those and this reads what they found for what it means. It is not a survey and does not replace the surveyor, the civil engineer, or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| sketch-readerDavidCho1999/archaiflow-skillsReads the drawings that are not drawings: a hand sketch, a napkin diagram, a photograph of a whiteboard, a rendered view, a screenshot of a model. Separates what is decided from what is drawn loosely and what is placeholder, since the three look alike in a sketch and the difference is the whole content. Then names what the sketch has already committed to without anybody deciding it. Trigger on "read this sketch", "what does this diagram say", "the client sent a drawing they did", "read this rendering", "what does this model view show", "sketch-reader", or any informal drawing handed over. Carries no dimensions and reads no scale off an unscaled drawing. `drawing-reader` reads a measured PDF; this reads the ones drawn by hand or produced to look convincing. It does not judge the design and does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| space-programDavidCho1999/archaiflow-skillsMaintains a space program in docs/program/program.md: every space the project must contain, its required quantity and target area from the brief, the area the current plan gives it, and the delta. Trigger on "space program", "program of requirements", "room list", "area program", "programming", "target area", "are we over program", "space-program", or a pasted brief with a room schedule to capture. Targets come from the brief or the client, measured areas come from your plan, and the grossing factor comes from you; the skill supplies none of them and computes only the arithmetic between them, shown. Works in the unit system the brief uses. Reports name every space still missing a target or a measured area rather than hiding them in totals. Interrogating the brief itself is brief-review's job. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |