菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Read, search, send, and manage messages across Gmail, Outlook, Telegram, and other platforms
An on-demand personal daily briefing — weather, headlines, the shape of your day, and one thing worth your attention — in a sharp executive-assistant voice. The general-purpose morning brief; richer work or admin digests compose it as their general layer.
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
Delegate a big or high-stakes job to a fleet of parallel subagents, orchestrated deterministically; runs unattended and reports back
Manage contacts, communication channels, access control, and invite links
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 whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use, or to edit an app they already built here. Do NOT reach for a ui_show dynamic_page to fake an artifact — build a real persistent app here. NOT for complex, multi-user, or shippable products — those go to a real project folder with a coding agent (see Scope below).
| 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. |
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 Useruser@example.com, alice@example.org555-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.