Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 47191–47220 of 56218 skills
| Skill | Stars | Updated | Works with | Status | 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| stakeholder-mapDavidCho1999/archaiflow-skillsThis skill should be used when the user wants to map the stakeholders, decision rights, and communication structure of an AEC project. Trigger on 'stakeholder map', 'who decides what', 'project stakeholder analysis', 'RACI matrix for this project', 'map the stakeholders', 'governance plan', or pasted project context where governance, sign-off authority, or communication cadence is the question. Generates a structured stakeholder map markdown in `docs/stakeholders/` and appends to the project stakeholder index. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| start-the-projectDavidCho1999/archaiflow-skillsThe first hour on a new project: separates the decisions that have to be made before anything is drawn from the ones that can wait, because most projects reverse that and spend a month on the ones that could have waited. Establishes who decides what, what the project is actually being measured on, which unknowns block work and which do not, and what has to be commissioned now to arrive in time. Produces the decision list and the commissioning list, and hands each part off by name. Trigger on "we just won a project", "where do I start", "kick off", "what do we need before we start designing", "start-the-project", or a new commission with nothing set up. Carries no schedules, no fees and no checklists of deliverables; `drawing-checklist` holds what a phase produces and this holds what a phase has to decide. It does not replace the principal or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| subconsultant-agreement-reviewDavidCho1999/archaiflow-skillsReads subconsultant agreements against the prime agreement to find the gap the architect is standing in: obligations promised to the owner that were never passed down, insurance required upstream and not required downstream, payment terms that oblige payment before you are paid, and scope that appears in neither agreement. Works clause by clause across both documents and reports every mismatch with what each side says. Trigger on "review the subconsultant agreement", "does our consultant agreement match the prime", "flow down check", "who carries this obligation", "subconsultant-agreement-review", or a consultant agreement handed over before execution. Carries no standard-form text and no legal positions; both agreements come from you. It is not legal advice and does not replace the attorney or the Architect of Record. Read `contract-review` on the prime first. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| thread-readerDavidCho1999/archaiflow-skillsReads a thread of emails or messages and answers the question that starts most disputes: what did we actually agree. Separates what was decided from what was proposed and never answered, tracks who was on the thread at each point since a decision made after somebody dropped off is a decision they never saw, finds the requests that were never replied to, and flags anything that quietly accepted scope, cost or time. Trigger on "read this thread", "what did we agree on this", "go through this email chain", "did we ever answer this", "thread-reader", or a chain of correspondence handed over. Carries no contract terms; whether something is binding comes from the agreement. `draft-email` writes one message; this reads a chain of them. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| utilization-trackerDavidCho1999/archaiflow-skillsKeeps one dated record of hours against fee at the level where it can still be acted on: by phase and by person rather than by project total, with the percentage of work complete recorded separately from the percentage of fee spent, since a project can be on budget and forty percent behind. Records what caused each overrun so the pattern separates from the incident, and flags the hours that should have been additional services before they are written off. Trigger on "utilization tracker", "are we over on this project", "hours against fee", "track the team's time by phase", "utilization-tracker", or a timesheet export handed over to make sense of. Carries no rates, no utilization targets and no benchmarks; the practice sets those. It does not replace the accounting system — it reads what that produces — and it does not replace `fee-tracker`, which follows the fee itself. | 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 |
| 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 |
| design-acoustic-separationDavidCho1999/archaiflow-skillsWorks acoustic separation between two spaces as a whole rather than as a wall or floor rating: establishes what the source is and what the receiver needs, then traces every path sound can take between them, because the assembly's tested rating describes the direct path only and the built result is set by whatever flanks around it. Names the structural decisions that have to be made early and cannot be fixed later. Trigger on "acoustic separation", "STC between these units", "impact noise from above", "flanking", "why is this wall not working acoustically", "design-acoustic-separation", or two spaces with a noise problem between them. Carries no ratings, no laboratory values and no criteria; the target comes from the code, the brief or the acoustician, and every assembly value is a tested figure you cite. It is not acoustic engineering and does not replace the acoustician or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-beamDavidCho1999/archaiflow-skillsSizes a single simply-supported beam in steel, wood, or reinforced concrete for a known span, tributary load, and deflection limit, showing every step of the arithmetic. Trigger on "size beam", "preliminary beam size", "pick a section", "glulam beam size", "concrete beam size", "beam deflection check", "design-beam", or a pasted span with loads. Works with any design standard. The user names the standard, the design method, and supplies the load combinations, material properties, section properties, resistance factors, and deflection limit, by typing them, pasting the table, or naming a file. The skill never supplies an engineering value from memory or from web search. Preliminary sizing only, for a fully braced simple span, and never a substitute for the Engineer of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-ceilingDavidCho1999/archaiflow-skillsWorks the ceiling as the place every discipline's leftovers land: adds up what has to fit in the plenum in the order it gets installed, finds the one crossing that sets the height for the whole floor, and works access, transitions and the elements that arrive late and wreck a reflected ceiling plan. Reports the height available against the height wanted. Trigger on "ceiling height", "what fits in the plenum", "reflected ceiling plan", "will the duct clear the beam", "ceiling access", "design-ceiling", or a floor-to-floor with a question about what it leaves. Carries no depths, no clearances and no code requirements; structural depths come from the engineer, service sizes from the MEP set, and required heights from the code you quote. It does not size services or structure and does not replace the engineers or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-columnDavidCho1999/archaiflow-skillsChecks a single axially loaded, braced column against the capacity your standard's values produce, with every step of the arithmetic shown: slenderness from your effective length factor, capacity from the expression or table row you supply, demand over capacity at the end. Trigger on "column check", "column size", "post size", "axial capacity", "slenderness check", "KL/r", "design-column", or a pasted column load with a trial section. Works with any design standard. The user names the standard and method and supplies the load combinations, the effective length factor, the section and material properties, and the capacity expression or its tabulated value, by typing, pasting, or naming a file; the skill never supplies an engineering value, a buckling curve, or a section from memory or web search. Concentric axial load on a braced member only; combined bending needs your interaction equation or it stops. Preliminary sizing, never a substitute for the Engineer of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-ductDavidCho1999/archaiflow-skillsSizes a duct segment from an airflow and the limits you set: area from the velocity limit you state, rectangular dimensions within your aspect ratio, the equivalent-diameter arithmetic between round and rectangular, and a pressure-drop tally over a run when you supply the loss values, every step shown. Trigger on "duct size", "duct sizing", "duct velocity", "equivalent diameter", "static pressure", "cfm to duct size", "design-duct", or a pasted airflow with a size question. Works in either unit system, as given. The user supplies the airflow, the velocity or friction-rate limit with where it came from, aspect ratio limits, and any fitting loss values, cited; the skill never supplies a velocity limit, a friction rate, or a loss coefficient from memory or from web search. Geometry and arithmetic only: fan selection, system effect, acoustics, and leakage class are the mechanical engineer's calls. Preliminary, never a substitute for the mechanical Engineer of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-electrical-roomDavidCho1999/archaiflow-skillsLays out an electrical, communications or service entrance room around the working clearances that surround the equipment rather than around the equipment itself, because those clearances are code, they are volumes, and they appear on no architectural drawing by default. Works the utility's own requirements separately from the code's, since a service entrance room is designed to the utility's standard and they will refuse a room that meets the code and not their manual. Trigger on "electrical room layout", "how big does the switchgear room need to be", "working clearance in front of the panel", "service entrance room", "transformer vault", "design-electrical-room", or an electrical equipment schedule with a room to put it in. Carries no clearance dimensions, no equipment sizes and no utility requirements. It does not do electrical design and does not replace the electrical engineer or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-elevatorDavidCho1999/archaiflow-skillsHolds the architectural space an elevator installation needs from the consultant's or manufacturer's data: the hoistway, the pit below the lowest landing, the overrun above the highest, the machine and controller wherever the product puts them, and the lobby and door dimensions at every level. Works the constraints that decide the building — what the pit does to the foundation, what the overrun does to the roof or the height limit, and where the machine has to be if there is no machine room. Trigger on "elevator pit depth", "lift overrun", "machine room-less", "how big is the hoistway", "elevator shaft coordination", "design-elevator", or an elevator specification handed over to fit into a building. Carries no dimensions, no capacities, no speeds and no code requirements; every one comes from the manufacturer, the elevator consultant, or the code you quote. It does not do traffic analysis and does not replace the elevator consultant or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-footingDavidCho1999/archaiflow-skillsChecks a single isolated spread footing: bearing pressure under your loads against the allowable bearing value your geotechnical report gives, with every step of the arithmetic shown. Trigger on "footing size", "spread footing", "bearing pressure", "bearing check", "pad footing", "footing check", "design-footing", or a pasted column load with a bearing value. Works with any standard. The user supplies the loads, the allowable or factored bearing resistance with its source, the load combinations, and a trial plan size; the skill never supplies a bearing value, a soil property, or a frost depth from memory or from web search. Plan size and bearing only: the footing's thickness, shear, and reinforcement are concrete design and stop the run. Preliminary sizing, never a substitute for the Engineer of Record or the geotechnical engineer. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-mechanical-roomDavidCho1999/archaiflow-skillsLays out a mechanical plant room from the equipment schedule the engineer gives you, and adds the four things that make it bigger than the equipment: the service clearances each unit needs, the route to get equipment in during construction and out at replacement, the air the room itself has to take in and exhaust, and the connections that leave it. Reports the required footprint and height against what is drawn. Trigger on "size the mechanical room", "plant room layout", "will the AHU fit", "how do we get the chiller in", "mechanical room design", "design-mechanical-room", or an equipment schedule handed over with a room to put it in. Carries no equipment dimensions, no clearances, no ventilation rates and no code requirements; all come from the engineer, the manufacturer and the code text you quote. It does not select or size equipment and does not replace the MEP engineer or the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-panel-loadDavidCho1999/archaiflow-skillsTotals an electrical panel or service load: connected load summed by the categories your code uses, demand factors applied as you cite them, continuous-load multipliers as you cite them, and the result converted to amps at the voltage you state, with every step of the arithmetic shown. Trigger on "panel load", "load calc", "service size", "connected load", "demand load", "panel schedule totals", "design-panel-load", or a pasted load list. Works with any electrical code. The user supplies the load list, the category rules, the demand factor rows, and any multipliers, pasted and cited; the skill never supplies a demand factor, a VA allowance, or a multiplier from memory or from web search, and categories without a cited factor come out at connected load, marked unverified. Load totalling only: conductor and breaker sizing, fault current, voltage drop, and coordination are the electrical engineer's calculations and stop the run. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |