Vellum User Facing Copy

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

Gates applied: no behavioural pass.

assistant/CLAUDE.md

assistant/src/approvals/CLAUDE.md

assistant/src/notifications/CLAUDE.md

assistant/src/runtime/CLAUDE.md

gateway/CLAUDE.md

Audit 0.4.1 · source sha 19bc86343b63 · 14 Oct 2026Report an issue or request a re-scan

• Publishervellum-ai GitHub organizationOwner of the repository this skill is read from
• Source foldervellum-ai/vellum-assistant/.cursor/skills/vellum-user-facing-copyThe 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

Its description: Review Vellum Assistant user-facing copy, examples, docs, CLI output, UI strings, and assistant-facing release notes. Use when editing text users may read, including README files, SKILL.md files, CLI messages, route…

---
name: vellum-user-facing-copy
description: Review Vellum Assistant user-facing copy, examples, docs, CLI output, UI strings, and assistant-facing release notes. Use when editing text users may read, including README files, SKILL.md files, CLI messages, route errors, update bulletins, and client UI labels.
---

# Vellum User-Facing Copy

## Terminology

Use "assistant" in user-facing text. "Daemon" is an internal implementation detail and should only appear in internal code, internal comments, file paths, or architecture explanations intended for maintainers.

When unsure, ask: would a user ever read this? If yes, say "assistant".

## Generic Examples

Never include real personal data in examples, fixtures, tests, docs, or commit messages.

Use:

- Names: `Alice`, `Bob`, `Example User`
- Emails: `[email protected]`, `[email protected]`
- Phone numbers: `555-0100` through `555-0199`
- IDs: `user-123`, `org-abc`, `conv-xyz`

Avoid real names, personal emails, real phone numbers, account IDs, tokens, or private workspace paths.

## Release Notes

There is currently no release-note surfacing mechanism — the workspace-bulletin feature was removed. Do not add new release-note workspace migrations; the historical set is frozen.

## Error Messages

Good user-facing errors:

- explain what failed
- avoid exposing internals or secrets
- say what the user can do next when there is a clear action
- use consistent product terminology

Avoid stack traces, implementation-only vocabulary, and ambiguous "something went wrong" messages when a concrete cause is available.

## Review Workflow

1. Identify text users may read.
2. Check terminology, privacy, and clarity.
3. Check whether the copy implies unavailable or flagged behavior.
4. Preserve technical precision while removing internal jargon.
5. Recommend tests or snapshots when copy is part of a stable interface.

Excerpt, first 1,883 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.

git clone https://github.com/vellum-ai/vellum-assistant
git -C vellum-assistant checkout 19bc86343b63

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 19bc86343b63

Questions about Vellum User Facing Copy

• 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