Connector SkillRevit
Inspect model data, scope changes and check the result. Give your AI a consistent way to work inside Revit.
Connectors give your AI agent the tools. Skills give it the method.
They guide it through tasks in Revit, AutoCAD, 3ds Max and more,
with clear steps for doing the work and checking the result.
Inspect model data, scope changes and check the result. Give your AI a consistent way to work inside Revit.
Query drawings, work with selected objects and organise repeated operations with checks along the way.
Navigate coordination models, narrow searches and inspect properties without retrieving the entire model.
Read definitions, trace connections and check data trees when building or adjusting a graph.
Inspect DGN models, levels and elements. Keep queries focused and verify changes against the drawing.
Inspect scenes, use focused object queries and verify modelling or scene-management operations.
Read the document, layers and objects, model with typed operations and verify each result by measurement or capture.
Inspect surfaces, alignments, profiles and pipe networks with focused reads, take numbers from the model and verify civil edits against it.
Inspect steel objects, assemblies and numbering, work from the loaded catalogues and verify model, numbering and drawing changes.
Build loadable families the way a content author would: template and category, a named reference rig, labelled dimensions, flexing before and after geometry, types, materials and visibility, then load and check.
Model from a linked point cloud with evidence: confirm placement and units, sample bounded regions and section stacks, fit faces and axes, author native elements, then compare the model back to the points.
Review a model the way a BIM manager would: a baseline of warnings, views, families and links, triage by type, one fix at a time with a preview first, the clean-up chain, coordination checks and a before and after report.
Produce a drawing set the way a drafter would: take stock of what exists, create and crop the views, apply templates, tag and dimension, build schedules, lay out sheets, record revisions, write the register and issue PDF and DWG.
Set out a frame the way a structural engineer would: levels before grids, columns, beams, beam systems, braces, structural floors and footings from catalogue types, justification, copings and openings, then support checks and the analytical model for handoff.
Model building services the way an engineer would: spaces in step with the rooms, ducts, pipes, flex, tray and conduit with the fittings the types route with, joints, caps and systems, circuits to panels, penetrations sized for the host owner, and open-end checks.
Run a federated model the way a BIM coordinator would: link the discipline models, audit and acquire shared coordinates, copy the datums, keep links loaded and pathed, clash discipline against discipline with a review view and a CSV report, and issue the federated NWC and IFC.
Build the site the way a landscape or civil modeller would: link the survey and acquire its grid, terrain from contours or spot heights, point edits, graded pads with cut and fill, paving and planting areas, fitted hard landscaping, terrain walls, ramps, planting from a schedule and retention between phases.
Run document control the way a document controller would: document numbers composed from the ISO 19650 fields, status codes, revisions in the practice sequences, the drawing register and matrix issue sheet filled from the practice template, PDF and DWG issued and named from the parameters, and whole reissue sets.
Prepare laser, CNC and model-making cut files the way a workshop would: agree the machine and material, pull the profiles out of the drawing, make every cut a closed polyline on the layers the machine reads, scale for the model, allow for kerf, lay the parts out on sheets with labels, check, then write the DXF.
Set up Corona the way a visualiser would: one daylight source, a physical camera with its exposure, quality by noise limit, a test frame, LightMix and tone mapping in the frame buffer, then EXR output.
Set up V-Ray the way a visualiser would: one HDR dome, a V-Ray physical camera with its exposure, materials with reflection, glass, dirt and round edges, quality by noise threshold, a test frame, then raw EXR with the elements a grade needs.
Build parametric definitions the way a computational designer would: agree the intent and its drivers, place one cluster at a time from a declarative graph, prove each stage by the data it computes, fix data-tree matching, script what no component covers, reference live Rhino geometry and bake to named layers.
We build skills around your team’s templates, standards and sign-off checks.
Tell us the task. We build it, test it against agreed requirements and hand it over.