Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vellum-ai/vellum-boundary-guard
Check Vellum Assistant architecture and package boundaries.
Passed 23 of 23 test cases with the skill, and 9 of 23 without it.
and 16 more in the full report
14 fixed9 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
An HTTP endpoint in gateway/routes.py needs user profile data models defined in assistant/types.py. Can we import them via relative paths from the gateway module?
| Checked | Without skill | With skill |
|---|---|---|
| State that gateway/ must not import from assistant/ via relative paths | Missed | Passed |
| Recommend placing shared data models in packages/ | Missed | Passed |
The instructions your model reads when the skill loads.
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.test cases passed, vs 9 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.