Product guide

HuskyBIM for Revit 2025

HuskyBIM for Revit 2025 connects Claude Desktop directly to Autodesk Revit 2025 (.NET 8) through 641 AI tools covering elements, families, views, sheets, parameters, schedules, documentation and more. Control your model in plain language — no scripting required.

Installation

Download the installer

Sign in to your account page and download HuskyBIM_for_Revit_2025_v1.53.exe from the Downloads section. Make sure no other version of HuskyBIM for Revit is installed before running the installer.

Run the installer

Double-click the .exe and approve the Windows security prompt (enter an administrator password if asked). Do not right-click and choose "Run as administrator" — activation must run from your own account. The installer copies the add-in files to the correct Revit Add-Ons directory and registers the Claude Desktop extension automatically.

Enter your account email

When prompted, enter the email address for your free HuskyBIM account. The installer validates your account, configures the Revit add-in and registers the Claude Desktop extension automatically.

Restart Claude Desktop and Revit

Start Revit with a project open, then open Claude Desktop. HuskyBIM connects automatically. You should see HuskyBIM tools available in Claude.

Always keep a project open in Revit when working with HuskyBIM. Most tools operate on the active document. Tools that read model data will fail if no project is loaded.

What you can do

HuskyBIM for Revit 2025 includes 697 tools across all major Revit domains. A representative sample:

ElementsGet, create, modify, delete elements. Filter by category, level, phase.

ParametersRead and write instance and type parameters. Create shared parameters.

Views & sheetsCreate floor plans, sections, elevations. Place views on sheets.

FamiliesLoad families, place instances, modify type parameters.

SchedulesCreate and export quantity schedules and material takeoffs.

Levels & gridsList, create and modify levels and grid lines.

Rooms & spacesCreate rooms, read area and volume, manage room names and numbers.

ExportExport to IFC, DWG, PDF and NWC. Async export for large models.

Example workflows

Model QA

Check all walls in the model and list any that are missing a fire rating parameter.

Documentation

Create a room schedule for all rooms on Level 1 showing name, number, area and department.

Model setup

Create levels at 0, 3.5, 7.0 and 10.5 meters named Ground Floor, Level 1, Level 2 and Level 3.

Skills — save a workflow and run it again

When you have finished a piece of work in the chat, you can save it as a skill: a named recipe that runs the same steps again, on any model, without describing them a second time. Ask for it in plain language — for example "save what we just did as a skill called stamp-doors". Skills are stored as small files on your machine, one per skill, and they are data rather than code: nothing runs that you did not ask for.

Two kinds

A macro skill replays an exact sequence of operations — find these elements, write this parameter, export that schedule. It is deterministic, so it does the same thing every time. A prompt skill stores instructions instead, for work that needs judgement: "audit the room names against our convention, list what looks wrong, and ask me before changing anything".

Preview before anything changes

Every skill can be run as a dry run first. Read-only steps execute for real, so the preview is based on your actual model, while anything that would modify the model is only listed. You see exactly which elements would be touched and what would be written to them, and the model stays untouched.

Run the skill "stamp-doors" as a dry run on this model.

They work on your selection

A skill can start from whatever you have selected in Revit, which makes it the natural way to say "do this to these". Select the elements, then run the skill — it picks up the selection and works through it.

Conditions and calculations

Steps can be conditional, so a skill can act only on the elements that actually need it — the doors missing a fire rating, the walls taller than a given height. Skills can also count, sum, average and build text, so a QA skill can end with a one-line summary instead of a wall of output.

Built from what actually happened

You do not have to describe the workflow again from memory. The connector remembers the operations it performed in the session, so a skill can be built from the calls that were really made. Element IDs differ between models, so a saved skill must generalise: it queries for the elements it needs rather than hard-coding IDs — the connector refuses to save a skill that would only work on one specific file, unless you deliberately pin it to that model.

A record of what ran

Every run is logged: when it ran, which inputs were used, how many operations it made, which elements it touched, and whether anything failed. Ask "what have my skills done today?" to read it back. Useful when a check has to be defensible weeks later.

Sharing skills across an office

Skills live in %APPDATA%\HuskyBIM\skills by default. Point the HUSKYBIM_SKILLS_DIR environment variable at a shared network folder and everyone on that folder sees the same skills — a practical way for a BIM manager to publish office standards, since a skill is a single small file that can be copied, reviewed and versioned like any other document.

Troubleshooting

HuskyBIM tools not visible in Claude Desktop

Make sure Claude Desktop was restarted after installation. Check that the extension is enabled in Claude Desktop settings under Extensions. If the extension is missing or shows an error, re-run the installer.

Commands return "No active Revit document"

Open a Revit project first. HuskyBIM requires an active, open document to operate on most commands.

Installer fails

Ensure Revit is not open during installation, and start the installer by double-clicking it — not via "Run as administrator", which can place the activation under the wrong Windows account. Check that Revit 2025 is installed. Contact support if the issue persists.