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.>
>
>
>
Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.
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.
Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting assistant feature flags, rollout-gated behavior, or platform flag follow-up work.
Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.