@vellumai/assistant 0.4.43 → 0.4.45

package/src/config/bundled-skills/document-writer/SKILL.md

@@ -1,195 +0,0 @@
----
-name: document-writer
-description: Create and edit long-form documents like blog posts, articles, essays, and reports using the built-in rich text editor
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"📝","vellum":{"display-name":"Document Writer","user-invocable":true}}
----
-
-You are helping your user write long-form content (blog posts, articles, essays, reports, documentation) using the built-in document editor. This skill should be used whenever the user asks to write, draft, or create any document-like content.
-
-## When to Use This Skill
-
-**ALWAYS use this skill when the user asks for:**
-- Blog posts
-- Articles
-- Essays
-- Reports
-- Guides or tutorials
-- Documentation
-- Any long-form written content (500+ words)
-
-**DO NOT use this skill for:**
-- Short responses or explanations (< 500 words)
-- Code snippets or technical implementations
-- Interactive apps or dashboards (use `app_create` instead)
-- Quick summaries
-
-## Workflow
-
-### Step 1: Create the Document
-
-Use `document_create` to open the built-in rich text editor:
-
-```json
-{
-  "title": "The title of the document (inferred from user's request)",
-  "initial_content": "Optional starting content in Markdown format"
-}
-```
-
-**Important:** The editor opens in the Documents tab of the Directory panel, with chat docked to the side. The user can see both the editor and chat simultaneously.
-
-### Step 2: Generate Content
-
-Write the content in **Markdown format**. Use proper structure:
-
-- `#` for main title
-- `##` for section headings
-- `###` for subsections
-- `**bold**` and `*italic*` for emphasis
-- ` ```language ` for code blocks
-- `[text](url)` for links
-- `- ` or `1. ` for lists
-- `> ` for blockquotes
-- Tables, images, and other Markdown features as appropriate
-
-**Quality standards:**
-- Write in clear, engaging prose appropriate for the content type
-- Use active voice and vary sentence structure
-- Break content into logical sections with descriptive headings
-- Include transitions between sections
-- For technical content: use code blocks with syntax highlighting
-- For data-heavy content: use Markdown tables
-
-### Step 3: Stream Content to Editor
-
-Use `document_update` to send content to the editor as you generate it:
-
-```json
-{
-  "surface_id": "doc-xyz",
-  "content": "# Main Title\n\nYour content here...",
-  "mode": "append"
-}
-```
-
-**Streaming strategy:**
-- Generate content in logical chunks (paragraphs or sections)
-- Use `mode: "append"` to stream chunks as you write
-- The content appears in real-time in the editor
-- Don't wait to generate everything before sending - stream it!
-
-### Step 4: Handle User Edits and Requests
-
-The user can request changes via the docked chat while viewing the document:
-
-**Common requests:**
-- "Make the intro shorter"
-- "Add a section about X"
-- "Change the tone to be more formal"
-- "Fix the grammar in paragraph 3"
-
-**How to respond:**
-- Acknowledge the request
-- Generate the updated content
-- Use `document_update` with:
-  - `mode: "replace"` for complete rewrites
-  - `mode: "append"` for additions at the end
-  - For edits in the middle: use `mode: "replace"` with the full updated document
-
-### Step 5: Finalize
-
-Once the user is satisfied:
-- Confirm the document is complete
-- Remind them that it's automatically saved in the Generated panel
-- Let them know they can continue editing manually or ask for more changes
-
-## Examples
-
-### Example 1: Blog Post Request
-
-**User:** "Write a blog post about the future of AI"
-
-**Your response:**
-```
-I'll create a document for your blog post about the future of AI.
-```
-
-Then:
-1. Call `document_create` with `title: "The Future of AI"`
-2. Generate content in chunks, calling `document_update` repeatedly:
-   - First chunk: `# The Future of AI\n\nArtificial intelligence is...`
-   - Second chunk: `## Current State\n\nToday, AI systems...`
-   - Third chunk: `## Emerging Trends\n\n1. **Multimodal AI**...`
-   - Continue until complete
-
-### Example 2: Edit Request
-
-**User (after initial creation):** "Add a section about ethical considerations"
-
-**Your response:**
-```
-I'll add a section on AI ethics.
-```
-
-Then:
-1. Call `document_update` with `mode: "append"` and content:
-   ```markdown
-   ## Ethical Considerations
-
-   As AI systems become more powerful, we must address...
-   ```
-
-### Example 3: Full Rewrite
-
-**User:** "Rewrite this in a more casual tone"
-
-**Your response:**
-```
-I'll rewrite the article in a more casual, conversational tone.
-```
-
-Then:
-1. Call `document_update` with `mode: "replace"` and the complete rewritten content
-
-## Important Notes
-
-- **Documents are automatically saved** and accessible via the Generated panel
-- The user can **manually edit documents** at any time - your role is to assist with generation and refinement
-- The editor supports **drag-and-drop images**, which are converted to base64 inline
-- **Word count is tracked** automatically and displayed to the user
-- **Toast UI Editor** is used, which provides both Markdown and WYSIWYG editing modes
-- Always **acknowledge the document creation** before calling `document_create`
-
-## Error Handling
-
-- If `document_create` fails, the user may not have the client connected. Ask them to check their connection.
-- If the user asks to edit a specific part but you don't have the full document context, ask them to clarify which section or provide more context.
-- If you're unsure about the content direction, ask clarifying questions before generating.
-
-## Anti-Patterns (DO NOT DO THIS)
-
-❌ **Don't use `app_create` for blog posts or articles**
-- Blog posts should use `document_create`, not `app_create`
-- Apps are for interactive content with state/data
-
-❌ **Don't write everything at once without streaming**
-- Use `document_update` with `mode: "append"` to stream chunks
-- Users want to see content appear in real-time
-
-❌ **Don't ask for explicit approval before creating the document**
-- If the user asks for a blog post, create it immediately
-- They can always request changes after
-
-❌ **Don't output the full content in chat**
-- The content goes in the document editor, not in the chat response
-- Just acknowledge what you're doing and stream to the editor
-
-## Success Criteria
-
-✅ Document editor opens in the Documents tab
-✅ Content appears in real-time as you generate it
-✅ User can see both the editor and chat side-by-side
-✅ Content is well-structured with proper Markdown formatting
-✅ User can request edits via chat and you respond appropriately
-✅ Final document is saved and accessible in Generated panel

package/src/config/bundled-skills/elevenlabs-voice/SKILL.md

@@ -1,140 +0,0 @@
----
-name: elevenlabs-voice
-description: Select and tune an ElevenLabs TTS voice — curated voice list, custom/cloned voices via API key, and tuning parameters
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"🗣️","vellum":{"display-name":"ElevenLabs Voice","user-invocable":true}}
----
-
-## Overview
-
-ElevenLabs provides text-to-speech voices for both **in-app TTS** and **phone calls**. The shared config key `elevenlabs.voiceId` controls the voice across all channels. Use the `voice_config_update` tool to change the voice — it writes to the config file and pushes to the macOS app via SSE in one call.
-
-## Choose a Voice
-
-Pick a voice that matches the your identity and the user's preferences. Offer to show the full list if they want to choose themselves.
-
-### Female voices
-
-| Voice     | Style                      | Voice ID               |
-| --------- | -------------------------- | ---------------------- |
-| Rachel    | Calm, warm, conversational | `21m00Tcm4TlvDq8ikWAM` |
-| Sarah     | Soft, young, approachable  | `EXAVITQu4vr4xnSDxMaL` |
-| Charlotte | Warm, Swedish-accented     | `XB0fDUnXU5powFXDhCwa` |
-| Alice     | Confident, British         | `Xb7hH8MSUJpSbSDYk0k2` |
-| Matilda   | Warm, friendly, young      | `XrExE9yKIg1WjnnlVkGX` |
-| Lily      | Warm, British              | `pFZP5JQG7iQjIQuC4Bku` |
-
-### Male voices
-
-| Voice   | Style                           | Voice ID               |
-| ------- | ------------------------------- | ---------------------- |
-| Antoni  | Warm, well-rounded              | `ErXwobaYiN019PkySvjV` |
-| Josh    | Deep, young, clear              | `TxGEqnHWrfWFTfGW9XjX` |
-| Arnold  | Crisp, narrative                | `VR6AewLTigWG4xSOukaG` |
-| Adam    | Deep, middle-aged, professional | `pNInz6obpgDQGcFmaJgB` |
-| Bill    | Trustworthy, American           | `pqHfZKP75CvOlQylNhV4` |
-| George  | Warm, British, distinguished    | `JBFqnCBsd6RMkjVDRZzb` |
-| Daniel  | Authoritative, British          | `onwK4e9ZLuTAKqWW03F9` |
-| Charlie | Casual, Australian              | `IKne3meq5aSn9XLyUdCD` |
-| Liam    | Young, articulate               | `TX3LPaxmHKxFdv7VOQHJ` |
-
-### Setting the voice
-
-To set the chosen voice, use `voice_config_update`. This writes to the config file (`elevenlabs.voiceId`) for phone calls **and** pushes to the macOS app via SSE (`ttsVoiceId`) for in-app TTS in one call:
-
-```
-voice_config_update setting="tts_voice_id" value="<selected-voice-id>"
-```
-
-Verify it worked:
-
-```bash
-assistant config get elevenlabs.voiceId
-```
-
-Tell the user what voice you chose and why, but also offer to show all available voices so they can choose for themselves.
-
-## ElevenLabs API Key Setup
-
-For advanced voice selection (browsing the full library, custom/cloned voices), the user needs an ElevenLabs API key. A free tier is available at https://elevenlabs.io.
-
-To collect the API key securely:
-
-```
-credential_store action="prompt" service="elevenlabs" field="api_key"
-```
-
-## Advanced Voice Selection (with API key)
-
-Users with an ElevenLabs API key can go beyond the curated list above.
-
-### Check for an existing key
-
-```bash
-assistant credentials inspect elevenlabs:api_key --json
-```
-
-### Browse the voice library
-
-```bash
-curl -s "https://api.elevenlabs.io/v2/voices?category=premade&page_size=50" \
-  -H "xi-api-key: $(assistant credentials reveal elevenlabs:api_key)" | python3 -m json.tool
-```
-
-### Search for a specific style
-
-```bash
-curl -s "https://api.elevenlabs.io/v2/voices?search=warm+female&page_size=10" \
-  -H "xi-api-key: $(assistant credentials reveal elevenlabs:api_key)" | python3 -m json.tool
-```
-
-### Custom and cloned voices
-
-If the user has created a custom voice or voice clone in their ElevenLabs account, they can use its voice ID directly. These voices work in both in-app TTS and Twilio ConversationRelay.
-
-### Preview voices
-
-Each voice in the API response includes a `preview_url` with an audio sample the user can listen to before deciding.
-
-### Set the chosen voice
-
-After the user picks a voice from the library:
-
-```
-voice_config_update setting="tts_voice_id" value="<selected-voice-id>"
-```
-
-## Voice Tuning
-
-Fine-tune how the selected voice sounds. These parameters apply to all ElevenLabs modes (in-app TTS and phone calls):
-
-```bash
-# Playback speed (0.7 = slower, 1.0 = normal, 1.2 = faster)
-assistant config set elevenlabs.speed 1.0
-
-# Stability (0.0 = more expressive/variable, 1.0 = more consistent/monotone)
-assistant config set elevenlabs.stability 0.5
-
-# Similarity boost (0.0 = more creative, 1.0 = closer to original voice)
-assistant config set elevenlabs.similarityBoost 0.75
-```
-
-Lower stability makes the voice more expressive but less predictable — good for conversational calls. Higher stability is better for scripted or formal contexts.
-
-## Voice Model Tuning
-
-By default, the system sends a **bare** `voiceId` to Twilio ConversationRelay (no model/tuning suffix). This is the safest default across voice IDs.
-
-To optionally force Twilio's extended voice spec, set a model ID:
-
-```bash
-assistant config set elevenlabs.voiceModelId "flash_v2_5"
-```
-
-When `voiceModelId` is set, the emitted voice string becomes: `voiceId-model-speed_stability_similarity`.
-
-To clear and revert to the bare voiceId default:
-
-```bash
-assistant config set elevenlabs.voiceModelId ""
-```

package/src/config/bundled-skills/email-setup/SKILL.md

@@ -1,68 +0,0 @@
----
-name: email-setup
-description: Create the assistant's own email address via the Vellum hosted API (one-time setup)
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"📧","vellum":{"display-name":"Email Setup","user-invocable":true}}
----
-
-You are setting up your own personal email address. This is a one-time operation — once you have an email, you do not need to run this again.
-
-## Prerequisites
-
-Only proceed if the user explicitly asks you to create or set up **your own** (the assistant's) email address — e.g., "set up your email", "create your email address", "I want you to have your own email". Generic email requests like "send an email", "check my email", or "set up email" are about the **user's Gmail** and should be handled by the Messaging skill, not this one. Do NOT proactively run this skill.
-
-## Step 1: Check if Email Already Exists
-
-Before doing anything, check whether you already have an email address configured:
-
-```bash
-assistant email status
-```
-
-Inspect `addresses` in the response. If at least one address exists, tell the user the existing address and stop — do NOT create another one.
-
-## Step 2: Create Your Email
-
-Create a new inbox through the CLI:
-
-```bash
-assistant email inbox create --username <your-username>
-```
-
-For `<your-username>`, use your assistant name (lowercased, alphanumeric only). Check your identity from `IDENTITY.md` or `USER.md` to determine your name. If you don't have a name yet, ask the user what username they'd like for your email.
-
-Use the returned `inbox.address` (or `inbox.id` if `address` is empty) as the created email address.
-
-## Step 3: Verify Status
-
-```bash
-assistant email status
-```
-
-Confirm the created inbox appears in `addresses`.
-
-## Step 4: Confirm Setup
-
-After the inbox is created and visible in status:
-
-1. Tell the user your new email address.
-2. Store a note in your memory or `USER.md` that your email has been provisioned so you remember it in future conversations.
-
-## Rules
-
-- **One-time only.** If an inbox already exists (Step 1), do not create another. Inform the user of the existing address.
-- **User-initiated only.** Never run this skill unless the user asks you to set up or create an email.
-- **No custom domains.** Use the default provider domain. Do not attempt domain setup.
-- **No API key prompting.** The email API key should already be configured. If the `assistant email` command fails with an API key error, tell the user the email integration is not yet configured and ask them to set it up.
-
-## Troubleshooting
-
-### API key not configured
-
-If you get an error about a missing API key, the email provider has not been set up. Tell the user:
-
-> "Email isn't configured yet. Please set up the email integration first."
-
-### Inbox creation failed
-
-If inbox creation returns an error (e.g. username taken), try a variation of the name (append a number or use a nickname) and retry once. If it still fails, report the error to the user.

package/src/config/bundled-skills/frontend-design/SKILL.md

@@ -1,44 +0,0 @@
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
-compatibility: "Designed for Vellum personal assistants"
-license: Complete terms in LICENSE.txt
-metadata: {"emoji":"🎨"}
----
-
-This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
-
-The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
-
-## Design Thinking
-
-Before coding, understand the context and commit to a BOLD aesthetic direction:
-- **Purpose**: What problem does this interface solve? Who uses it?
-- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
-- **Constraints**: Technical requirements (framework, performance, accessibility).
-- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
-
-**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
-
-Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
-- Production-grade and functional
-- Visually striking and memorable
-- Cohesive with a clear aesthetic point-of-view
-- Meticulously refined in every detail
-
-## Frontend Aesthetics Guidelines
-
-Focus on:
-- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
-- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
-- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
-- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
-- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
-
-NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
-
-Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
-
-**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
-
-Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/src/config/bundled-skills/frontend-design/icon.svg

@@ -1,16 +0,0 @@
-<svg viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
-  <rect x="0" y="0" width="16" height="16" fill="#f5f5f5"/>
-  <rect x="2" y="2" width="12" height="11" fill="#ffffff" stroke="#333333" stroke-width="1"/>
-  <rect x="2" y="2" width="12" height="2" fill="#ff6b6b"/>
-  <rect x="3" y="3" width="10" height="1" fill="#ffffff"/>
-  <rect x="3" y="5" width="2" height="1" fill="#4ecdc4"/>
-  <rect x="6" y="5" width="2" height="1" fill="#4ecdc4"/>
-  <rect x="9" y="5" width="2" height="1" fill="#4ecdc4"/>
-  <rect x="3" y="7" width="4" height="1" fill="#95e1d3"/>
-  <rect x="3" y="8" width="4" height="1" fill="#95e1d3"/>
-  <rect x="3" y="9" width="3" height="1" fill="#95e1d3"/>
-  <rect x="8" y="7" width="5" height="1" fill="#ffd93d"/>
-  <rect x="8" y="8" width="5" height="1" fill="#ffd93d"/>
-  <rect x="8" y="9" width="3" height="1" fill="#ffd93d"/>
-  <rect x="3" y="11" width="10" height="1" fill="#e8e8e8"/>
-</svg>