Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 95% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 32% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -35% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -41% | 0% |
Enforce these boundaries:
assistant/ must not import from gateway/ via relative paths.gateway/ must not import from assistant/ via relative paths.assistant/ and skills/ must not import from each other directly.meta/.packages/.For tests that need behavior from another package, mock the boundary instead of importing real handlers.
gateway/.~/.vellum directory.First-party skills run as separate processes and should communicate through supported contracts. Do not bypass skill isolation with direct relative imports.
packages/ module, IPC, HTTP through gateway, or a skill contract.Prefer existing guard tests when available, then add focused tests for any new boundary rule or route pattern.
Other measured skills in the registry, with their headline benchmark lift.