# Revit Addin Bundle

> >

- **Type:** Skill
- **Install:** `agentstack add skill-nice3point-revit-skills-revit-addin-bundle`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Nice3point](https://agentstack.voostack.com/s/nice3point)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Nice3point](https://github.com/Nice3point)
- **Source:** https://github.com/Nice3point/revit-skills/tree/main/plugins/revit-solution/skills/revit-addin-bundle

## Install

```sh
agentstack add skill-nice3point-revit-skills-revit-addin-bundle
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Revit Add-in Bundle

An Autodesk App Store add-in ships as a `.bundle` — a `PackageContents.xml` plus a `Contents/` folder for each supported Revit version.
A solution scaffolded from the templates with bundle support carries a ModularPipelines `build` project whose `pack` command assembles the bundle from every version's publish output and stamps it with a version.
This skill configures and runs that packaging; a solution created without bundle support needs the bundle wiring added first (see Common Pitfalls).

## When to use

- Packaging an add-in as an Autodesk App Store bundle.
- Setting the vendor metadata and version that go into the bundle.

## Workflow

### Step 1: Set vendor metadata

Set the vendor fields in the `Bundle` section of `build/appsettings.json` (`VendorName` is required):

```json
"Bundle": {
    "VendorName": "Contoso",
    "VendorUrl": "https://contoso.example",
    "VendorEmail": "support@contoso.example"
}
```

### Step 2: Resolve the version

`GitVersion` derives the bundle's `AppVersion` from Git tags; a fixed `Version` in `build/appsettings.json` overrides it.
Tag the commit before packing so the version is meaningful, and commit at least once — GitVersion needs history.

### Step 3: Build the bundle

Run the `pack` command from the `build` directory.
It compiles every supported Revit configuration, then assembles the bundle from each configuration's publish output.
The same run also produces an installer only when the solution was scaffolded with installer support:

```shell
cd build
dotnet run -c Release -- pack
```

The result is a zipped `.bundle` under `output/`, laid out per version:

```text
RevitAddIn.bundle/
  PackageContents.xml
  Contents/
    2025/
      RevitAddIn.addin
      RevitAddIn/RevitAddIn.dll
    2026/
      RevitAddIn.addin
      RevitAddIn/RevitAddIn.dll
```

The generated `PackageContents.xml` carries the product name, `AppVersion`, the vendor metadata, and one component entry per Revit year.

### Step 4: Verify

Confirm the bundle has a `Contents/` folder for every supported version and that `PackageContents.xml` shows the expected version and vendor fields, then upload it to the Autodesk App Store.

## Validation

- [ ] `VendorName` (at minimum) is set in the `Bundle` section of `build/appsettings.json`.
- [ ] The version derives from a Git tag, or an explicit `Version`.
- [ ] The bundle carries a `Contents/` folder for each supported Revit version.

## Common Pitfalls

| Pitfall                                              | Correct approach                                                                                                                                                                                                                                                                                                                |
|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Building before any Git commit                       | Commit first; GitVersion needs history.                                                                                                                                                                                                                                                                                         |
| Hand-numbering versions                              | Tag the commit and let GitVersion derive the version.                                                                                                                                                                                                                                                                           |
| Shipping a bundle without vendor metadata            | Set the `Bundle` fields in `build/appsettings.json`.                                                                                                                                                                                                                                                                            |
| Packing a solution scaffolded without bundle support | First create the solution with bundle support (`dotnet new revit-addin-sln --bundle`) and transfer the bundle infrastructure files from a throwaway `--bundle` solution (see `revit-template-migration`). |
| A Revit year missing from the bundle                 | Pack builds every configured version; add the year to the configuration matrix (`revit-multi-version-configuration`).                                                                                                                                                                                                           |

## Source & license

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

- **Author:** [Nice3point](https://github.com/Nice3point)
- **Source:** [Nice3point/revit-skills](https://github.com/Nice3point/revit-skills)
- **License:** MIT

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-nice3point-revit-skills-revit-addin-bundle
- Seller: https://agentstack.voostack.com/s/nice3point
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.