Install
$ agentstack add skill-nice3point-revit-skills-revit-addin-publishing ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
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/publishfor 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
.addinmanifest. - [ ] 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.
- Author: Nice3point
- Source: Nice3point/revit-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.