AgentStack
SKILL verified MIT Self-run

Revit Api References

skill-nice3point-revit-skills-revit-api-references · by Nice3point

>

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-nice3point-revit-skills-revit-api-references

✓ 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 Api References? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Revit API References

The Nice3point.Revit.Api.* NuGet packages carry the Revit API assemblies; a project compiles for any Revit year without that year installed locally. A local file (HintPath) reference ties the build to one installed version at one path and breaks CI and teammates' machines.

When to use

  • Adding a reference to RevitAPI, RevitAPIUI, or another Revit assembly.
  • Reviewing a project that references Revit DLLs by local path.

Workflow

Step 1: Reference the API package with a version wildcard

The $(RevitVersion).* wildcard resolves the assembly set for the active configuration. $(RevitVersion) is supplied by the Nice3point.Revit.Sdk, which derives it from the build configuration (for example Release.R272027) — see revit-sdk-project-configuration. With central package management, pin the version in Directory.Packages.props and reference it without a version here.

Step 2: Never reference a local Revit DLL

Do not add a local file reference — it requires that exact Revit version at that exact path on every build machine:


    C:\Program Files\Autodesk\Revit 2027\RevitAPI.dll

Step 3: Find the right package

Assemblies ship as Nice3point.Revit.Api.* (RevitAPI, RevitAPIUI, RevitAPIIFC, AdWindows, UIFramework, and more). Check the Nice3point.Revit.Api.* packages before adding any assembly reference; only request a new one if it does not exist.

Step 4: Verify

Restore and build on a machine (or CI) with no Revit installed.

Validation

  • [ ] Revit API assemblies come from Nice3point.Revit.Api.* packages.
  • [ ] No HintPath/local-file reference to a Revit DLL remains.
  • [ ] The version uses the $(RevitVersion).* wildcard (or central package management).
  • [ ] The project restores and builds without Revit installed.

Common Pitfalls

| Pitfall | Correct approach | |---------------------------------------------|--------------------------------------------------------| | ` to an installed Revit DLL | Use Nice3point.Revit.Api. with $(RevitVersion).. | | A fixed API version that breaks other years | Use the $(RevitVersion).*` wildcard. | | Copying a Revit DLL into the repo | Reference the NuGet package instead. |

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.