personal-page
The personal-page skill populates a pre-built, dark cinematic landing page that showcases the user's biography, work history, and life areas. Use it whenever the user requests a personal page about themselves or asks to update existing content on their page. This skill handles content creation only (names, facts, verified details in third person), never design or layout changes, and requires editing the profile-data.ts file followed by an app_refresh call to publish the finished page.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/personal-page && cp -r /tmp/personal-page/assistant/src/config/bundled-skills/personal-page ~/.claude/skills/personal-pageSKILL.md
You fill in the user's personal page — a finished, cinematic dark landing page
that already lives in the workspace as the app `personal-page`. Your job is
**content, not construction**: the design is done.
If `/workspace/data/apps/personal-page/` does not exist, this skill does not
apply (the preseeded page is rolled out gradually) — build whatever the user
asked for with app-builder instead.
**Present it as yours.** To the user this is "the page you filled in for
them" — fine to acknowledge the page shell exists, but never narrate the
mechanics below (file paths, refresh calls, contracts) or your progress in
chat. Do the work, then one short line.
## How to populate it
1. Read `/workspace/data/apps/personal-page/src/profile-data.ts`. The contract
comment at the top explains every field and shows a worked example.
2. Overwrite the `profile` export with what you know or learned about the
user. Set `status: "ready"`. Touch ONLY this file — never the layout,
styles, animations, or media. Do NOT use `app_create`; the app exists.
3. Call `app_refresh` (app_id: `personal-page`). If it reports compile errors,
fix your profile-data.ts edit and refresh again. **`app_refresh` is the
only build step — never compile manually (no esbuild, bundlers, or build
commands in the terminal); the platform's compiler has the correct JSX
setup and a manual build will produce a broken page.**
4. As soon as the refresh is clean, call `app_open` (app_id: `personal-page`)
so the finished page is up and waiting — don't wait to be asked.
## Writing the content
- Facts beat adjectives: names, numbers, places. One fact per bullet.
- Only what you actually verified; write around gaps rather than inventing.
- Third person, warm but grounded. The page should feel like a profile in a
design magazine, not a résumé.
## Later edits
- Content tweaks ("add my marathon PR", "fix my title") → same flow: edit
`profile-data.ts`, `app_refresh`.
- Only if the user explicitly asks to change the **design or layout** may you
edit the other source files, following app-builder conventions.Set up, authenticate, and run external coding agents (Claude Code, Codex) via the Agent Client Protocol
Shop on Amazon and Amazon Fresh through your browser
Record and analyze API surfaces of web services
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. A one-off diagram, chart, or explainer that just accompanies an answer belongs to the visualize skill (ui_show visual), not an app. NOT for complex, multi-user, or shippable products — those go to a real project folder with a coding agent (see Scope below).
Drive a specific named macOS app via raw input bypassing the Accessibility tree
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum primitives. Handles single-source and multi-source migrations with a unified, deduplicated inventory.
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready text for search, Q&A, and summarization without building a custom parsing pipeline.
Import conversation history from ChatGPT into Vellum