Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vellum-ai/vellum-user-facing-copy
Review Vellum Assistant user-facing copy, examples, docs, CLI output, UI strings, and assistant-facing release notes.
Passed 18 of 22 test cases with the skill, and 3 of 22 without it.
and 21 more in the full report
15 fixed3 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a 4-word status bar indicator copy showing that the interactive agent component is currently waiting for input.
| Checked | Without skill | With skill |
|---|---|---|
| Refers to the entity as assistant in the microcopy | Missed | Passed |
The instructions your model reads when the skill loads.
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".
Never include real personal data in examples, fixtures, tests, docs, or commit messages.
Use:
Alice, Bob, Example User[email protected], [email protected]555-0100 through 555-0199user-123, org-abc, conv-xyzAvoid real names, personal emails, real phone numbers, account IDs, tokens, or private workspace paths.
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.
Good user-facing errors:
Avoid stack traces, implementation-only vocabulary, and ambiguous "something went wrong" messages when a concrete cause is available.
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.