AgentStack
SKILL verified MIT Self-run

Revit Addin Publishing

skill-nice3point-revit-skills-revit-addin-publishing · by Nice3point

>

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-nice3point-revit-skills-revit-addin-publishing

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Revit Addin Publishing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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\), so the running Revit loads the add-in on its next start; PublishAddin copies into bin\publish (like dotnet publish) for distribution. Enable them only in the project that owns the .addin manifest. To launch and debug the deployed add-in from the IDE, use revit-addin-debugging.

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

true 
true 

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

Step 2: Include extra content

Step 3: Rely on manifest patching

The SDK removes the ManifestSettings node for Revit versions older than 2026 during publish, so one .addin works across supported years (see revit-dependency-isolation).

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 ` item | Use . | | Hand-editing the manifest per Revit version | Let the SDK patch ManifestSettings` on publish. |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.