Agent skill · Audited from source
Vellum Change Review
skill · vellum-ai/vellum-assistantMIT licenceAudited 14 Oct 2026 · source 19bc86343b63
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 19bc86343b63 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks…
Cite
Cite this page
ModelsAtlas. “Vellum Change Review (vellum-ai/vellum-assistant)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/vellum-ai/vellum-change-review
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 5 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (5)
LOWInventory / provenanceinv.symlink · assistant/CLAUDE.md
assistant/CLAUDE.md
- Why
- link not followed
- Fix
- —
LOWInventory / provenanceinv.symlink · assistant/src/approvals/CLAUDE.md
assistant/src/approvals/CLAUDE.md
- Why
- link not followed
- Fix
- —
LOWInventory / provenanceinv.symlink · assistant/src/notifications/CLAUDE.md
assistant/src/notifications/CLAUDE.md
- Why
- link not followed
- Fix
- —
LOWInventory / provenanceinv.symlink · assistant/src/runtime/CLAUDE.md
assistant/src/runtime/CLAUDE.md
- Why
- link not followed
- Fix
- —
LOWInventory / provenanceinv.symlink · gateway/CLAUDE.md
gateway/CLAUDE.md
- Why
- link not followed
- Fix
- —
Audit 0.4.1 · source sha 19bc86343b63 · 14 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishervellum-ai GitHub organizationOwner of the repository this skill is read from
- Source foldervellum-ai/vellum-assistant/.cursor/skills/vellum-change-reviewThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict19bc86343b63A new audit runs when the source changes
- Repository statusNot archivedLast push 1 day ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks…
--- name: vellum-change-review description: Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks for a code review, quality pass, or pre-merge check in this repository. --- # Vellum Change Review ## Review Stance Prioritize bugs, behavioral regressions, security risks, migration gaps, broken package boundaries, and missing tests. Findings come before summaries. Avoid cosmetic feedback unless it affects correctness, maintainability, or user experience. ## Required Checks 1. Inspect the actual diff before judging the change. 2. Identify which packages are affected: `assistant`, `gateway`, `clients`, `cli`, `skills`, `packages`, or `meta`. 3. Check package boundaries: - `assistant` must not import from `gateway` by relative path. - `gateway` must not import from `assistant` by relative path. - `assistant` and `skills` must not import each other directly. - Runtime code must not import from `meta`. 4. Check persistence changes: - DB schema or data changes need append-only DB migrations. - Workspace path, format, or file changes need append-only workspace migrations. - Migrations must be idempotent and registered. 5. Check feature flags: - New assistant flags must be declared in `meta/feature-flags/feature-flag-registry.json`. - Default-disabled or rollout-only features must not ship user-facing release notes. - New flags may require a companion platform PR. 6. Check user-facing text: - User-facing copy should say "assistant", not "daemon". - Examples must use generic names, emails, phone numbers, and IDs. 7. Check LLM/provider usage: - LLM calls must go through the provider abstraction. - Comments and logs should use provider-agnostic wording. 8. Check tests and verification: - Look for focused tests covering changed behavior. - Prefer scoped `bun test path/to/test.ts`; never suggest broad `bun test`. - Suggest `bunx tsc --noEmit` when type-level risk is broad. ## Review Output Use this structure: ```markdown ## Findings - [severity] `path`: issue, impact, and concrete fix. ## Open Questions - Any uncertainty that affects correctness or review confidence. ## Verification Gaps - Tests or checks that still need to run. ``` If no issues are found, say that clearly and still mention residual risk or unrun checks.
Excerpt, first 2,471 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 19bc863
git clone https://github.com/vellum-ai/vellum-assistant git -C vellum-assistant checkout 19bc86343b63
The author documents no install command, so this uses the repository directly. Our verdict covers commit 19bc86343b63 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
19bc86343b63
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/vellum-ai/vellum-change-review/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All coding & review skills →vellum-ai/vellum-assistant
Set up, authenticate, and run external coding agents (Claude Code, Codex) via the Agent Client Protocol
vellum-ai/vellum-assistant
Shop on Amazon and Amazon Fresh through your browser
vellum-ai/vellum-assistant
Record and analyze API surfaces of web services
vellum-ai/vellum-assistant
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill…
vellum-ai/vellum-assistant
Drive a specific named macOS app via raw input bypassing the Accessibility tree
vellum-ai/vellum-assistant
Import conversation history from ChatGPT into Vellum
Add this badge to your README
[](https://modelsatlas.com/skills/vellum-ai/vellum-change-review/)
<a href="https://modelsatlas.com/skills/vellum-ai/vellum-change-review/"><img src="https://modelsatlas.com/skills/vellum-ai/vellum-change-review/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Vellum Change Review
What does the Vellum Change Review skill do?
Is Vellum Change Review safe to install?
What can Vellum Change Review access on my machine?
How current is this page?
Sources
- github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/v — the audited source at commit 19bc86343b63 and every finding aboveObserved · 14 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Vellum Change Review skill do?
- Is Vellum Change Review safe to install?
- What can Vellum Change Review access on my machine?