How do I install the Revit Addin Publishing skill?

Run npx skillmds@latest add nice3point/revit-addin-publishing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Revit Addin Publishing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Revit Addin Publishing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Revit Addin Publishing free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Revit Addin Publishing?

nice3point (@nice3point) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Revit Addin Publishing by nice3point

Name: Revit Addin Publishing
Author: nice3point

Revit Addin Publishing

Configure an Autodesk Revit add-in project to copy the add-in, .addin manifest to the local Revit or a `bin/publish` folder, using the Nice3point.Revit.Sdk publish targets. USE FOR: setting up a project for publishing, bundling extra content into the output, and relying on per-version manifest patching. DO NOT USE FOR: launching and debugging the add-in from the IDE (use revit-addin-debugging), dependency isolation or repacking (use revit-dependency-isolation), or packaging a versioned App Store bundle (use revit-addin-bundle).

nice3point cf4f257 2.9 KB Updated Sep 17, 2026

File contents

Revit Add-in Publishing

The Nice3point.Revit.Sdk targets copy the built add-in and its .addin manifest to one of two destinations and patch the manifest per Revit version. DeployAddin copies into the local Revit add-ins folder (%AppData%\Autodesk\Revit\Addins\<version>); the running Revit loads the add-in on its next start. PublishAddin copies into bin\publish (like dotnet publish) for distribution or the installer. Enable them only in the project that owns the .addin manifest.

When to use

Setting up a project to copy its add-in to the local Revit for testing, or to bin/publish for distribution.
Bundling extra content (families, resources) into the add-in output.

Workflow

Step 1: Deploy or publish

<DeployAddin>true</DeployAddin> <!-- to %AppData%\Autodesk\Revit\Addins\<version> -->
<PublishAddin>true</PublishAddin> <!-- to bin\publish for distribution -->

DeployAddin implies publishing. Override the targets with AddinDeployDir / AddinPublishDir.

Step 2: Include extra content

<Content Include="Families\**" PublishDirectory="Families" CopyToPublishDirectory="PreserveNewest" />

Step 3: Rely on manifest patching

The SDK removes the ManifestSettings node for Revit versions older than 2027 during publish.

Step 4: Verify

Build, and confirm the add-in and manifest land in the deploy or publish folder and that Revit loads the add-in.

Validation

Deploy/publish is enabled only in the project holding the .addin manifest.
Extra content is declared with PublishDirectory / CopyToPublishDirectory.
The manifest works across supported years via SDK patching.

Common Pitfalls

Pitfall	Correct approach
Enabling deploy in a class-library project with no `.addin`	Enable it only in the manifest-owning project.
Copying families with a raw `<None>` item	Use `<Content … PublishDirectory=… CopyToPublishDirectory=… />`.
Hand-editing the manifest per Revit version	Let the SDK patch `ManifestSettings` on publish.

---name: revit-addin-publishingdescription: Configure an Autodesk Revit add-in project to copy the add-in, .addin manifest to the local Revit or a `bin/publish` folder, using the Nice3point.Revit.Sdk publish targets. USE FOR: setting up a project for publishing, bundling extra content into the output, and relying on per-version manifest patching. DO NOT USE FOR: launching and debugging the add-in from the IDE (use revit-addin-debugging), dependency isolation or repacking (use revit-dependency-isolation), or packaging a versioned App Store bundle (use revit-addin-bundle).license: MIT---# Revit Add-in PublishingThe `Nice3point.Revit.Sdk` targets copy the built add-in and its `.addin` manifest to one of two destinations and patch the manifest per Revit version.`DeployAddin` copies into the local Revit add-ins folder (`%AppData%\Autodesk\Revit\Addins\<version>`); the running Revit loads the add-in on its next start.`PublishAddin` copies into `bin\publish` (like `dotnet publish`) for distribution or the installer.Enable them only in the project that owns the `.addin` manifest.## When to use- Setting up a project to copy its add-in to the local Revit for testing, or to `bin/publish` for distribution.- Bundling extra content (families, resources) into the add-in output.## Workflow### Step 1: Deploy or publish```xml<DeployAddin>true</DeployAddin> <PublishAddin>true</PublishAddin> ````DeployAddin` implies publishing.Override the targets with `AddinDeployDir` / `AddinPublishDir`.### Step 2: Include extra content```xml<Content Include="Families\**" PublishDirectory="Families" CopyToPublishDirectory="PreserveNewest" />```### Step 3: Rely on manifest patchingThe SDK removes the `ManifestSettings` node for Revit versions older than 2027 during publish.### Step 4: VerifyBuild, and confirm the add-in and manifest land in the deploy or publish folder and that Revit loads the add-in.## Validation- [ ] Deploy/publish is enabled only in the project holding the `.addin` manifest.- [ ] Extra content is declared with `PublishDirectory` / `CopyToPublishDirectory`.- [ ] The manifest works across supported years via SDK patching.## Common Pitfalls| Pitfall | Correct approach ||-------------------------------------------------------------|------------------------------------------------------------------|| Enabling deploy in a class-library project with no `.addin` | Enable it only in the manifest-owning project. || Copying families with a raw `<None>` item | Use `<Content … PublishDirectory=… CopyToPublishDirectory=… />`. || Hand-editing the manifest per Revit version | Let the SDK patch `ManifestSettings` on publish. |

Frequently asked questions