Latest news
TutorialsRevitdll2llm

How to Create a Revit API Agent Skill: The dll2llm Guide

Autodesk’s APS guide describes an Agent Skill workflow that uses dll2llm to give AI agents access to Revit API knowledge. This guide covers the required files and steps.

A designer working on a BIM model in an architecture studioAI image
Representative image, generated with AI.Image: 3dsınıfı / FCA AI

In brief

  1. dll2llm is a command-line tool that can inspect .NET assemblies and create an Agent Skill folder.
  2. You can provide the tool with RevitAPI.dll; add RevitAPIUI.dll if the user interface layer is also needed.
  3. The generated folder contains SKILL.md, INDEX.md, and topic files organized by namespace.
  4. Revit operations that modify the model require a Transaction; a SubTransaction can be used within an open Transaction.

What will you learn in this guide?

An AI agent working with the Revit API may not always choose the right classes and methods based on general programming knowledge alone. The Autodesk Platform Services (APS) guide explains this as a lack of API context: an agent may recognize some common types but incorrectly guess less frequently used methods. Since the Revit API contains many classes and namespaces, putting all the information into a single text file may not be practical either.

In this tutorial, we’ll look at how to generate an Agent Skill folder from Revit API assemblies and how to use it in an agent development workflow. The aim is not to build end-to-end automation in Revit, but to give the agent more structured, searchable API context. Autodesk’s guide uses a command-line tool called dll2llm for this purpose.

Requirements and limitations

This workflow requires access to the Revit API assemblies. The APS guide describes pointing the tool to RevitAPI.dll and adding RevitAPIUI.dll if the user interface layer is also needed. The guide also demonstrates using files from a Revit installation directory to generate a skill folder.

The tool is presented as the dll2llm GitHub project, which inspects a .NET assembly and converts it into Agent Skill files. The source does not specify supported operating systems, the required .NET version, a Revit version compatibility matrix, installation commands, or a particular agent product. It would therefore be misleading to provide commands, menu paths, or assumptions about versions here. Before getting started, check the current dll2llm project documentation and the DLL files in your Revit installation.

The official guide lists SKILL.md, INDEX.md, and topic Markdown files as the core files in the generated folder. Topic files are organized by namespace; large namespaces may be split alphabetically to avoid overloading the context window. Since the source does not mention an account requirement, this tutorial does not assume one.

Creating an Agent Skill step by step

  1. Define the goal. First, specify which Revit API tasks the agent is expected to support. For example, reading model data, filtering elements, and modifying a model in a plugin may require different API knowledge. Autodesk presents Agent Skill as a way to provide API context to an agent; the tool itself does not define your project requirements.

  2. Choose the required assemblies. RevitAPI.dll is the core input containing the database layer of the Revit API. If the agent also needs information about the user interface layer, consider adding RevitAPIUI.dll. The APS article says the second file can be used optionally. Don’t assume both assemblies are required for every task; the project’s needs should determine the scope.

  3. Review the dll2llm project. The tool is presented as the dll2llm project on GitHub. Since the source text does not include installation or usage details, we’re not providing a specific terminal command here. Follow the project’s own instructions and confirm which assembly path the tool expects as input.

  4. Provide the assembly to the tool. In the APS guide’s workflow, dll2llm is run against assemblies in the Revit installation directory. Select RevitAPI.dll and, if needed, RevitAPIUI.dll, and have the tool collect its output in a separate skill folder. The guide says the resulting files are organized by namespace, so the output may consist of more than one long API document.

  5. Check the generated files. Confirm that SKILL.md and INDEX.md are present, along with the topic Markdown files. These topic files contain API information grouped by namespace. Splitting large namespaces alphabetically can help prevent the agent’s context from becoming one huge block of content. Don’t treat the files as verified code examples just because they were generated; the tool provides API context, but it does not test your project logic for you.

  6. Add the skill to the agent workflow. In Autodesk’s approach, once the skill is set up, the agent can use the Revit API reference while working on a task. The goal is to reduce the cycle of copying and pasting individual code snippets into the chat window and give the agent access to broader API context. This source does not explain which agents support the skill format or how to install it; refer to the instructions for the environment you use.

  7. Test code suggestions with small tasks. Don’t assume code generated by the agent is reliable. First check that class and method names match the generated reference, then verify that the operation produces the expected result in the target model. Pay particular attention to transaction management in code that modifies the model: a Transaction is required to make changes in Revit, and only one Transaction can be open at a time. When a transaction completes successfully, changes are saved with Commit; RollBack reverses them. The Revit API documentation also explains that transaction statuses can be checked.

Common mistakes

Confusing API context with project validation: A Skill gives the agent a reference for API types and namespaces; it doesn’t prove that generated code will work correctly in a project. Test what the code does to the model separately.

Ignoring Transaction structure: Operations that modify the model must run within a Transaction. A SubTransaction can help divide a larger task into logical parts, but it must be created inside an open Transaction and closed before the parent transaction. A TransactionGroup can be used to handle multiple independent transactions together; it cannot be started while a Transaction is open.

Adding unnecessary files: The guide describes RevitAPIUI.dll as an additional input that can be used when the user interface layer is also needed. Match the skill’s scope to the task instead of adding content you don’t need.

Making assumptions about versions and installation details: The APS article does not include a detailed compatibility table or installation command. Make a note of the source of the Revit assembly you’re using, follow the dll2llm instructions, and don’t assume other versions will produce the same output.

Next steps: architecture and visualization workflows

BIM teams working on recurring data extraction or model editing tasks in Revit, plugin developers, and students learning the API may benefit from this approach. Helping an agent find API classes more effectively can reduce incorrect method guesses when prototyping. However, it does not replace model checks, code review, or testing the workflow under real project conditions. For architecture and interior design offices, potential benefits may be particularly relevant when developing in-house automation and helping team members new to the API find references.

Revit API Agent Skill is not a feature that directly improves render quality; it is intended for software and automation workflows that work with model data. For visualization teams, possible use cases include developing tools that retrieve information from Revit or automate model changes. The sources do not explain hardware, licensing, or agent subscription costs. Before implementation, assess your existing software requirements and whether your agent environment supports skills.

Sources and licensing

This tutorial is adapted from Autodesk Platform Services’ “Let AI Write Your Revit Code” guide, which describes dll2llm and Agent Skill, and from Autodesk’s Revit API documentation on Transaction, SubTransaction, and TransactionGroup. The sources are listed as license=free; the text and steps have been rewritten in original wording. Autodesk University’s course description for newcomers to the Revit API was used to support the learning scope covering the API, filtering, and Transactions.

Sources

3 sources
H
help.autodesk.comhelp.autodesk.com/view/RVT/2013/ENU/caas.html
Summary
A
aps.autodesk.comaps.autodesk.com/blog/let-ai-write-your-revit-code
Summary
A
autodesk.comautodesk.com/autodesk-university/de/class/Revit-Programming-Beginners-Easily-Access-Revit-API-Using-Free-Tools-2018
Summary

Source texts are not republished; short quotes are marked, everything else is our own summary and commentary.

3dsınıfı’s take
3dEditor’s assessment

For offices and students using Revit in Turkey, the practical value of the Agent Skill approach is that it brings a more systematic API reference into the agent workflow. Teams working on recurring model-data tasks or plugin prototypes in particular may be able to review code suggestions more quickly.

However, a skill folder is not a standalone automation or a validated plugin. Access to the DLLs, support for skills in the agent environment, and the software requirements in use should all be checked in advance. Since the sources do not provide hardware or licensing costs, these items should be clarified separately when estimating the investment.

Frequently asked questions

Which files are needed for a Revit API Agent Skill?

Autodesk’s guide describes providing dll2llm with RevitAPI.dll. RevitAPIUI.dll can also be added if the user interface layer is needed.

What does dll2llm generate?

According to the APS guide, the tool creates a skill folder containing SKILL.md, INDEX.md, and topic Markdown files organized by namespace.

Are Transactions required in code that modifies a Revit model?

Yes. The Revit API documentation states that a Transaction is required to modify the model and that only one Transaction can be open at a time.

Comments and the forum are in Turkish.Join the discussion
+

Related news