@vellumai/assistant 0.4.43 → 0.4.45

package/src/config/bundled-skills/agentmail/SKILL.md

@@ -1,132 +0,0 @@
----
-name: agentmail
-description: Run email operations through a provider-agnostic CLI wrapper
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"📬","vellum":{"display-name":"Email CLI Ops","user-invocable":true}}
----
-
-## How to run
-
-`vellum` is your own CLI binary — it is already installed and available on the PATH.
-Run all commands via `bash`. Do NOT attempt to install, build, or locate the CLI — just execute it directly.
-
-Example: `bash("assistant email status --json")`
-
-Never use browser/computer-use unless user explicitly approves fallback.
-
-## When to Use This Skill
-
-This skill manages the **assistant's own** AgentMail address (`@agentmail.to`) — not the user's personal email. Only use this skill when the user explicitly asks the assistant to send email **from the assistant's own address**, manage the assistant's inbox, or perform operations on the assistant's AgentMail account. Generic email requests ("send an email", "check my email", "draft a reply") are about the **user's Gmail** and should be handled by the Messaging skill instead.
-
-## Rules
-
-- Always run `assistant email` commands via `bash` and parse JSON output.
-- Always do `assistant email status --json` preflight first.
-- Prefer `draft create` before any send — never bypass draft flow.
-- Require explicit user confirmation before `draft approve-send --confirm`.
-- When uncertain, draft to ops@ inbox and notify user.
-- Never send cold outreach without explicit user authorization.
-
-## API Key Setup
-
-If `assistant email status --json` returns an error about a missing API key, prompt the user for their AgentMail API key using the secure credential prompt. **Never ask the user to paste the key in chat.**
-
-Use `credential_store` with:
-- action: `prompt`
-- service: `agentmail`
-- field: `api_key`
-- label: `AgentMail API Key`
-- description: `Get your API key from console.agentmail.to`
-- placeholder: `am_us_...`
-- allowed_tools: `["bash"]`
-- usage_description: `AgentMail email operations via vellum CLI`
-
-After the credential is stored, retry `assistant email status --json` to confirm it works.
-
-## Workflow
-
-1. **Preflight:** `assistant email status --json` (if API key error, run API Key Setup above)
-2. **Quick inbox:** `assistant email inbox create --username <name>` (creates e.g. sam@agentmail.to — no custom domain needed)
-3. **Custom domain setup (optional):** domain -> dns -> verify -> inboxes -> webhook
-4. **Draft path:** `assistant email draft create ...` — always draft first
-5. **Send path:** show draft -> user confirms -> `draft approve-send --draft-id <id> --confirm`
-6. **Inbound triage:** list -> get -> summarize -> propose reply draft
-7. **Guardrails:** check with `guardrails get`, use `guardrails set` to change
-
-## Command Reference
-
-### Provider
-
-```
-assistant email provider get [--json]                         # Show active provider
-assistant email provider set <provider> [--json]               # Switch provider
-```
-
-### Status
-
-```
-assistant email status [--json]                               # Provider health + guardrails
-```
-
-### Inbox Management
-
-```
-assistant email inbox create --username <name> [--domain <d>] [--display-name <n>] [--json]   # Create a new inbox (e.g. --username sam)
-assistant email inbox list [--json]                                                            # List all inboxes
-```
-
-### Setup
-
-```
-assistant email setup domain --domain <d> [--dry-run] [--json]
-assistant email setup dns --domain <d> [--json]
-assistant email setup verify --domain <d> [--json]
-assistant email setup inboxes --domain <d> [--json]                                            # Creates standard hello@/support@/ops@ inboxes
-assistant email setup webhook --url <u> [--secret <s>] [--json]
-```
-
-### Drafts
-
-```
-assistant email draft create --from <addr> --to <addr> --subject <s> --body <b> [--cc <addr>] [--in-reply-to <msg-id>] [--json]
-assistant email draft list [--status pending|approved|sent|rejected] [--json]
-assistant email draft get <draft-id> [--json]
-assistant email draft approve-send --draft-id <id> --confirm [--json]
-assistant email draft reject --draft-id <id> [--reason <text>] [--json]
-assistant email draft delete <draft-id> [--json]
-```
-
-### Inbound
-
-```
-assistant email inbound list [--thread-id <id>] [--json]
-assistant email inbound get <message-id> [--json]
-```
-
-### Threads
-
-```
-assistant email thread list [--json]
-assistant email thread get <thread-id> [--json]
-```
-
-### Guardrails
-
-```
-assistant email guardrails get [--json]
-assistant email guardrails set --paused <true|false> --daily-cap <n> [--json]
-assistant email guardrails block <pattern> [--json]
-assistant email guardrails allow <pattern> [--json]
-assistant email guardrails rules [--json]
-assistant email guardrails unrule <rule-id> [--json]
-```
-
-## Output Format
-
-All commands output JSON (pretty-printed by default, compact with `--json`).
-Every response includes `ok: true|false`.
-
-Exit codes:
-- `0` = success (`ok: true`)
-- `1` = error (`ok: false, error: "..."`)
-- `2` = guardrail blocked (`ok: false, error: "outbound_paused|daily_cap_reached|address_blocked"`)

package/src/config/bundled-skills/agentmail/icon.svg

@@ -1,21 +0,0 @@
-<svg viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
-  <rect width="16" height="16" fill="#0a0e27"/>
-  <rect x="2" y="3" width="12" height="8" fill="#1e40af" stroke="#60a5fa" stroke-width="1"/>
-  <rect x="2" y="3" width="12" height="2" fill="#3b82f6"/>
-  <rect x="3" y="4" width="10" height="1" fill="#0a0e27"/>
-  <rect x="3" y="5" width="5" height="1" fill="#93c5fd"/>
-  <rect x="3" y="6" width="5" height="1" fill="#bfdbfe"/>
-  <rect x="9" y="5" width="3" height="1" fill="#bfdbfe"/>
-  <rect x="9" y="6" width="3" height="1" fill="#93c5fd"/>
-  <rect x="2" y="12" width="3" height="1" fill="#059669"/>
-  <rect x="3" y="13" width="2" height="1" fill="#10b981"/>
-  <rect x="2" y="14" width="1" height="1" fill="#10b981"/>
-  <rect x="3" y="14" width="1" height="1" fill="#34d399"/>
-  <rect x="6" y="12" width="8" height="1" fill="#1f2937"/>
-  <rect x="6" y="13" width="8" height="1" fill="#374151"/>
-  <rect x="6" y="14" width="8" height="1" fill="#1f2937"/>
-  <rect x="7" y="13" width="1" height="1" fill="#60a5fa"/>
-  <rect x="9" y="13" width="1" height="1" fill="#60a5fa"/>
-  <rect x="11" y="13" width="1" height="1" fill="#60a5fa"/>
-  <rect x="13" y="13" width="1" height="1" fill="#60a5fa"/>
-</svg>

package/src/config/bundled-skills/amazon/SKILL.md

@@ -1,137 +0,0 @@
----
-name: amazon
-description: Shop on Amazon and Amazon Fresh using the built-in CLI integration
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"📦","vellum":{"display-name":"Amazon","user-invocable":true}}
----
-
-You can shop on Amazon (and Amazon Fresh for groceries) for the user using the `assistant amazon` CLI.
-
-## CLI Setup
-
-**IMPORTANT: Always use `host_bash` (not `bash`) for all `assistant amazon` commands.** The Amazon CLI needs host access for session cookies and the `vellum` binary — neither of which are available inside the sandbox.
-
-`assistant amazon` is a built-in subcommand of the Vellum assistant CLI — it is NOT a separate tool you need to find or install. It should already be on your PATH. If `vellum` is not found, prepend `PATH="$HOME/.local/bin:$PATH"` to the command. Do NOT search for the binary, inspect wrapper scripts, or try to discover how the CLI works. Just run the commands as documented below.
-
-## Typical Flow — Regular Amazon Shopping
-
-When the user asks you to order something from Amazon:
-
-1. **Check session** — run `assistant amazon status --json`. If `loggedIn` is false or the session is expired, tell the user: "A Chrome window will open to the Amazon login page. Please sign in there — I'll detect your login automatically and minimize the window." Then run `assistant amazon refresh --json`. This starts a Ride Shotgun learn session that records your login and auto-stops once it detects you've signed in. The session is imported automatically. **This command blocks until login is complete — just wait for it.**
-
-2. **Search** — run `assistant amazon search "<query>" --json` to find matching products. Present the top results with ASIN, title, price, and Prime status. If the user named a specific product, pick the best match. If ambiguous, ask.
-
-3. **Product details** (if needed) — run `assistant amazon product <asin> --json` to get full details including price and variations. For products with variants (size, color, etc.), see the Variations section below.
-
-4. **Add to cart** — run `assistant amazon cart add --asin <asin> [--quantity <n>] --json`. The response includes the updated cart with all items.
-
-5. **Review cart** — run `assistant amazon cart view --json` and show the user what's in their cart with prices. Ask if they want to add anything else or proceed.
-
-6. **Payment methods** — run `assistant amazon payment-methods --json` to see saved cards.
-
-7. **Checkout summary** — run `assistant amazon checkout --json` to get order totals (subtotal, shipping, tax, total).
-
-8. **Place order** — after the user explicitly confirms, run `assistant amazon order place [--payment-method-id <id>] --json`. The response contains `orderId` on success.
-
-## Typical Flow — Amazon Fresh Groceries
-
-Amazon Fresh delivers groceries. The flow is the same as regular Amazon, with these additions:
-
-1. **Search Fresh** — use the `--fresh` flag: `assistant amazon search "<query>" --fresh --json`
-
-2. **Add Fresh items** — use the `--fresh` flag: `assistant amazon cart add --asin <asin> --fresh --json`
-
-3. **Select delivery slot** — Fresh orders require a delivery window:
-   - `assistant amazon fresh delivery-slots --json` — list available slots
-   - `assistant amazon fresh select-slot --slot-id <id> --json` — select a slot
-   - Do this BEFORE checkout.
-
-4. **Checkout and order** — same as regular Amazon.
-
-## Handling Variations
-
-Many Amazon products (clothing, electronics) have variations (size, color, style):
-
-1. Run `assistant amazon product <asin> --json` to get the product and its `variations[]` array
-2. Each variation has: `dimensionName` (e.g. "size"), `value` (e.g. "Large"), `asin` (child ASIN), `isAvailable`, `priceValue`
-3. Use the child ASIN when adding to cart: `assistant amazon cart add --asin <child-asin> --json`
-
-Alternatively, run `assistant amazon variations <asin> --json` to list just the variations.
-
-## Session Storage
-
-Session cookies are stored in the encrypted credential store under the key `amazon:session:cookies`. You can inspect the stored session with:
-
-```bash
-assistant credentials inspect amazon:session:cookies
-```
-
-Session capture (`assistant amazon refresh`) and session checks (`assistant amazon status`) use the credential store automatically — no manual file management is needed.
-
-## Important Behavior
-
-- **Chrome extension relay required.** The Amazon CLI uses `assistant browser chrome relay` internally for browser automation. The Chrome extension must be connected before Amazon commands will work. If a command fails with a connection error, tell the user: "Please open Chrome, click the Vellum extension icon, and click Connect — then I'll retry."
-- **Always confirm before placing order.** Never call `order place` without explicit user approval. Show the cart and total first.
-- **Be proactive.** If the user says "order AA batteries", don't ask clarifying questions upfront — search, find the product, and suggest it. Only ask when you need a choice the user hasn't specified.
-- **Handle expired sessions gracefully.** If any command returns `"error": "session_expired"`, run `assistant amazon refresh --json` to re-capture the session.
-- **Show prices.** Always show prices when presenting products or the cart summary.
-- **Use `--json` flag** on all commands for reliable parsing.
-- **Do NOT use the browser skill.** All Amazon interaction goes through the CLI, not browser automation.
-- **Rate limiting.** Amazon may rate-limit rapid sequential requests. Wait 8–10 seconds between cart operations. If you get a 403 error, wait 15–20 seconds and retry.
-- **Always-allow tip.** At the start of an ordering flow, suggest the user enable "always allow" for `assistant amazon` commands: "Tip: You can type 'a' to always allow `assistant amazon` commands for this session so you won't be prompted each time."
-- **Fresh slot required.** Amazon Fresh orders require a delivery slot to be selected before checkout. If the user skips this step, remind them to run `assistant amazon fresh delivery-slots --json` and select a slot.
-
-## Command Reference
-
-```
-assistant amazon status --json                     # Check if logged in
-assistant amazon refresh --json                    # Capture fresh session via Ride Shotgun
-assistant amazon login --recording <path>          # Import session from a recording file
-assistant amazon logout                            # Clear session
-
-assistant amazon search "<query>" [--fresh] [--limit <n>] --json
-assistant amazon product <asin> [--fresh] --json
-assistant amazon variations <asin> --json
-
-assistant amazon cart view --json
-assistant amazon cart add --asin <asin> [--quantity <n>] [--fresh] --json
-assistant amazon cart remove --cart-item-id <id> --json
-
-assistant amazon fresh delivery-slots --json
-assistant amazon fresh select-slot --slot-id <id> --json
-
-assistant amazon payment-methods --json
-assistant amazon checkout --json
-assistant amazon order place [--payment-method-id <id>] --json
-```
-
-## Example Interactions
-
-**User**: "Order a pack of AA batteries from Amazon"
-
-1. `assistant amazon status --json` → logged in
-2. `assistant amazon search "AA batteries" --json` → finds products
-3. Show top results: "Duracell AA 20-pack ($12.99, Prime), Amazon Basics AA 48-pack ($14.49, Prime)..."
-4. User picks Duracell → `assistant amazon cart add --asin B00000J1ER --json`
-5. `assistant amazon cart view --json` → show cart summary
-6. `assistant amazon checkout --json` → show total
-7. "Your cart has 1x Duracell AA Batteries 20-pack ($12.99), total $12.99 with free Prime shipping. Ready to order?"
-8. User confirms → `assistant amazon order place --json`
-
-**User**: "Order a large blue t-shirt from Amazon"
-
-1. `assistant amazon search "blue t-shirt" --json` → finds products
-2. User picks a shirt → `assistant amazon variations <parentAsin> --json` → shows Size + Color combinations
-3. Find the child ASIN for Large + Blue → `assistant amazon cart add --asin <childAsin> --json`
-
-**User**: "Order milk and eggs from Amazon Fresh"
-
-1. `assistant amazon status --json` → logged in
-2. `assistant amazon search "whole milk" --fresh --json` → Fresh results
-3. `assistant amazon cart add --asin <milkAsin> --fresh --json`
-4. `assistant amazon search "eggs" --fresh --json` → Fresh results
-5. `assistant amazon cart add --asin <eggsAsin> --fresh --json`
-6. `assistant amazon fresh delivery-slots --json` → show available slots
-7. User picks a slot → `assistant amazon fresh select-slot --slot-id <id> --json`
-8. `assistant amazon checkout --json` → show totals
-9. User confirms → `assistant amazon order place --json`

package/src/config/bundled-skills/amazon/icon.svg

@@ -1,13 +0,0 @@
-<svg viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
-  <rect width="16" height="16" fill="#ffffff"/>
-  <rect x="2" y="3" width="12" height="9" fill="#FF9900" stroke="#232F3E" stroke-width="1"/>
-  <rect x="3" y="4" width="10" height="7" fill="#FF9900"/>
-  <rect x="4" y="5" width="2" height="2" fill="#232F3E"/>
-  <rect x="7" y="5" width="2" height="2" fill="#232F3E"/>
-  <rect x="10" y="5" width="2" height="2" fill="#232F3E"/>
-  <rect x="4" y="8" width="2" height="2" fill="#232F3E"/>
-  <rect x="7" y="8" width="2" height="2" fill="#232F3E"/>
-  <rect x="10" y="8" width="2" height="2" fill="#232F3E"/>
-  <path d="M 3 13 Q 8 14 13 13" stroke="#232F3E" stroke-width="1" fill="none"/>
-  <rect x="2" y="13" width="12" height="1" fill="#232F3E"/>
-</svg>

package/src/config/bundled-skills/api-mapping/SKILL.md

@@ -1,78 +0,0 @@
----
-name: api-mapping
-description: Record and analyze API surfaces of web services
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"🗺️","vellum":{"display-name":"API Mapping","user-invocable":true}}
----
-
-You can record and analyze the API surface of any web service using the `map` CLI.
-
-## CLI Setup
-
-**IMPORTANT: Always use `host_bash` (not `bash`) for all `map` commands.** The API mapping CLI needs host access for Chrome CDP, network recording, and browser automation — none of which are available inside the sandbox.
-
-`map` is a standalone CLI tool installed at `~/.vellum/bin/map`. It should already be on your PATH. If `map` is not found, prepend `PATH="$HOME/.vellum/bin:$PATH"` to the command. Do NOT search for the binary or try to discover how the CLI works. Just run the commands as documented below.
-
-## Typical Flow
-
-When the user wants to map a web service's API (e.g. "Map the Notion API" or "Figure out how Figma's API works"):
-
-1. **Ask about the objective** — Ask the user: "What service do you want to map?" and "What are you trying to build or integrate with?" This helps focus the recording on the relevant parts of the API surface.
-
-2. **Choose mode** — Ask the user: "Should I browse automatically, or do you want to drive?" This determines whether to use auto mode or manual mode:
-   - **Auto mode**: The CLI launches a headless browser, navigates the service, and records API calls automatically. Best for broad discovery.
-   - **Manual mode**: A Chrome window opens for the user to interact with the service while the CLI records all API traffic in the background. Best for capturing a specific workflow.
-
-3. **Run the mapping** — Execute the appropriate `map` command:
-   - Auto mode: `map <domain> --json`
-   - Manual mode: `map <domain> --manual --json`
-   - For longer sessions: `map <domain> --duration 120 --json`
-
-4. **Wait for recording to complete** — In auto mode, the CLI will browse and record for the default duration (60 seconds) then stop. In manual mode, the CLI blocks until the user closes the browser or presses Ctrl+C. The command outputs a JSON summary of all discovered endpoints.
-
-5. **Analyze the API map** — Review the output and present findings to the user:
-   - List discovered endpoints grouped by resource type (e.g., `/api/v1/users`, `/api/v1/documents`)
-   - Note authentication patterns (Bearer tokens, cookies, API keys)
-   - Identify CRUD operations and their HTTP methods
-   - Highlight any WebSocket or streaming endpoints
-   - Call out rate limiting headers or pagination patterns
-
-6. **Offer next steps** — Based on the discovered API surface, offer to:
-   - Create CLI tools that wrap the discovered endpoints
-   - Generate TypeScript types from observed request/response payloads
-   - Build a focused integration for the user's specific use case
-   - Re-record with a longer duration or manual mode to capture more endpoints
-
-## Important Behavior
-
-- **Be proactive.** If the user names a service, start mapping immediately rather than asking unnecessary clarifying questions. Ask about mode preference, then go.
-- **Always use `--json` flag** on all commands for reliable parsing.
-- **Present findings clearly.** Group endpoints logically, show HTTP methods, and highlight the most useful ones for the user's stated objective.
-- **Suggest manual mode for authenticated services.** If auto mode returns mostly auth redirects or login pages, suggest switching to manual mode so the user can log in first.
-- **Handle errors gracefully.** If the domain is unreachable or the recording captures no API calls, suggest checking the domain, trying manual mode, or increasing the duration.
-
-## Command Reference
-
-```
-map <domain> --json                        # Auto mode: browse and record API calls (default 60s)
-map <domain> --manual --json               # Manual mode: user drives the browser, CLI records
-map <domain> --duration <secs> --json      # Auto mode with custom duration
-map <domain> --manual --duration <secs> --json  # Manual mode with custom timeout
-```
-
-## Example Interaction
-
-**User**: "Map the Notion API"
-
-1. Ask: "What are you trying to build with Notion? And should I browse automatically, or do you want to drive the browser?"
-2. User says: "I want to build a CLI to manage my pages. I'll drive."
-3. `map notion.com --manual --json` -> Chrome window opens
-4. Tell user: "A Chrome window is open. Log into Notion and do a representative workflow — create a page, edit it, maybe move it. I'll record all API calls in the background. Close the browser when you're done."
-5. User closes browser -> CLI outputs discovered endpoints
-6. Present findings: "I found 14 API endpoints. Here are the key ones for page management:
-   - `POST /api/v3/getSpaces` — lists workspaces
-   - `POST /api/v3/syncRecordValues` — fetches page content
-   - `POST /api/v3/submitTransaction` — creates/updates pages
-   - `POST /api/v3/enqueueTask` — async operations (export, duplicate)
-   Authentication: Cookie-based session with `token_v2`."
-7. Offer: "Want me to create a CLI tool that wraps these endpoints for managing Notion pages?"

package/src/config/bundled-skills/api-mapping/icon.svg

@@ -1,18 +0,0 @@
-<svg viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
-  <rect width="16" height="16" fill="#0f172a"/>
-  <rect x="2" y="2" width="12" height="12" fill="#1e293b"/>
-  <rect x="3" y="3" width="10" height="10" fill="#0f172a" stroke="#3b82f6" stroke-width="1"/>
-  <rect x="4" y="4" width="2" height="2" fill="#3b82f6"/>
-  <rect x="10" y="4" width="2" height="2" fill="#3b82f6"/>
-  <rect x="4" y="10" width="2" height="2" fill="#3b82f6"/>
-  <rect x="10" y="10" width="2" height="2" fill="#3b82f6"/>
-  <line x1="5" y1="5" x2="11" y2="5" stroke="#10b981" stroke-width="1"/>
-  <line x1="5" y1="5" x2="5" y2="11" stroke="#10b981" stroke-width="1"/>
-  <line x1="11" y1="5" x2="11" y2="11" stroke="#10b981" stroke-width="1"/>
-  <line x1="5" y1="11" x2="11" y2="11" stroke="#10b981" stroke-width="1"/>
-  <rect x="7" y="7" width="2" height="2" fill="#f59e0b"/>
-  <line x1="5" y1="8" x2="7" y2="8" stroke="#60a5fa" stroke-width="1"/>
-  <line x1="9" y1="8" x2="11" y2="8" stroke="#60a5fa" stroke-width="1"/>
-  <line x1="8" y1="5" x2="8" y2="7" stroke="#60a5fa" stroke-width="1"/>
-  <line x1="8" y1="9" x2="8" y2="11" stroke="#60a5fa" stroke-width="1"/>
-</svg>

package/src/config/bundled-skills/cli-discover/SKILL.md

@@ -1,68 +0,0 @@
----
-name: cli-discover
-description: Discover which CLI tools are installed, their versions, and authentication status
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"🔍","vellum":{"display-name":"CLI Discovery","user-invocable":false}}
----
-
-# CLI Discovery
-
-When you need to discover what CLI tools are available on the system, use `host_bash` to check directly. Do not use sandboxed `bash` for discovery — it may not see host-installed CLIs or auth state, leading to false negatives.
-
-## Checking if a CLI exists
-
-```bash
-which <name>        # returns path if found, exits non-zero if missing
-command -v <name>   # alternative, works in all POSIX shells
-```
-
-## Getting version info
-
-```bash
-<name> --version    # most CLIs support this flag
-```
-
-Use a 5-second timeout to avoid hanging on unresponsive CLIs.
-
-## Auth-check commands
-
-For CLIs that support authentication, check whether the user is logged in:
-
-| CLI | Auth check command |
-|-----|-------------------|
-| `gh` | `gh auth status` |
-| `aws` | `aws sts get-caller-identity` |
-| `gcloud` | `gcloud auth list --filter=status:ACTIVE --format=value(account)` |
-| `az` | `az account show` |
-| `vercel` | `vercel whoami` |
-| `netlify` | `netlify status` |
-| `fly` | `fly auth whoami` |
-| `heroku` | `heroku auth:whoami` |
-| `railway` | `railway whoami` |
-
-## Common CLIs worth checking
-
-When doing a broad discovery, check these categories:
-
-- **Version control & code hosting:** `gh`, `git`, `gitlab`
-- **Project management:** `linear`, `jira`
-- **Communication:** `slack`
-- **Cloud providers:** `aws`, `gcloud`, `az`
-- **Containers & infra:** `docker`, `kubectl`, `terraform`
-- **Runtimes & package managers:** `node`, `bun`, `deno`, `python3`, `pip3`
-- **HTTP clients:** `curl`, `httpie`
-- **Hosting & deploy:** `vercel`, `netlify`, `fly`, `heroku`, `railway`
-
-## Output format
-
-Report findings in markdown:
-
-```markdown
-## Available CLIs
-
-- **git** (/usr/bin/git) — git version 2.x.x
-- **gh** (/usr/bin/gh) — gh version 2.x.x [authenticated: user@example.com]
-- **bun** (~/.bun/bin/bun) — 1.x.x
-
-## Not found: jira, linear, slack
-```

package/src/config/bundled-skills/deploy-fullstack-vercel/SKILL.md

@@ -1,179 +0,0 @@
----
-name: deploy-fullstack-vercel
-description: Build and deploy a full-stack app (React frontend + Python/FastAPI backend) to Vercel as a serverless demo with seeded data
-compatibility: "Designed for Vellum personal assistants"
-metadata: {"emoji":"🚀","vellum":{"display-name":"Deploy Fullstack to Vercel"}}
----
-
-# Deploy Fullstack to Vercel
-
-Deploy a full-stack app with a React/Vite frontend and Python/FastAPI backend to Vercel as a serverless demo. No auth required — meant for demos, portfolio pieces, and quick showcases.
-
-## When to Use
-
-- User says "deploy this to Vercel", "host this", "publish this"
-- User has a project with a frontend + backend they want live
-- User wants a quick demo deployment (no persistent database needed)
-
-## Prerequisites
-
-- A project with a frontend (React/Vite) and backend (FastAPI/Python)
-- Vercel CLI installed (`npm install -g vercel`) and authenticated (`vercel login`)
-
-## Workflow
-
-### 1. Build the Frontend
-
-```bash
-cd <project>/frontend
-npm install
-npx vite build
-```
-
-This produces static files in `frontend/dist/`.
-
-### 2. Create the Vercel Deploy Directory
-
-```
-<project>/vercel-deploy/
-├── api/
-│   ├── index.py          ← FastAPI app wrapper (entry point)
-│   ├── database.py        ← DB config (use /tmp for SQLite)
-│   ├── models.py
-│   ├── schemas.py
-│   ├── seed_data.py       ← Must seed ALL required data (users, etc.)
-│   ├── routers/
-│   │   ├── __init__.py
-│   │   └── *.py
-│   └── requirements.txt   ← Python deps (fastapi, sqlalchemy, pydantic)
-├── index.html             ← From frontend/dist/
-├── assets/                ← From frontend/dist/assets/
-└── vercel.json
-```
-
-**Key steps:**
-```bash
-mkdir -p <project>/vercel-deploy/api
-
-# Copy frontend build output to deploy root
-cp -r <project>/frontend/dist/* <project>/vercel-deploy/
-
-# Copy backend files into api/
-cp <project>/backend/models.py <project>/vercel-deploy/api/
-cp <project>/backend/database.py <project>/vercel-deploy/api/
-cp <project>/backend/schemas.py <project>/vercel-deploy/api/
-cp <project>/backend/seed_data.py <project>/vercel-deploy/api/
-cp -r <project>/backend/routers <project>/vercel-deploy/api/
-cp <project>/backend/requirements.txt <project>/vercel-deploy/api/
-```
-
-### 3. Create api/index.py (Serverless Entry Point)
-
-```python
-import sys, os
-sys.path.insert(0, os.path.dirname(__file__))
-
-from fastapi import FastAPI
-from fastapi.middleware.cors import CORSMiddleware
-from database import engine, Base, SessionLocal
-from seed_data import seed_exercises, seed_default_user  # all seed functions
-from routers import users, exercises, workouts, schedule, progress
-
-# Create tables and seed on EVERY cold start
-Base.metadata.create_all(bind=engine)
-db = SessionLocal()
-try:
-    seed_exercises(db)
-    seed_default_user(db)  # IMPORTANT: seed all required data
-finally:
-    db.close()
-
-app = FastAPI(title="MyApp")
-
-app.add_middleware(
-    CORSMiddleware,
-    allow_origins=["*"],
-    allow_credentials=True,
-    allow_methods=["*"],
-    allow_headers=["*"],
-)
-
-app.include_router(users.router)
-# ... other routers
-
-@app.get("/api/health")
-def health_check():
-    return {"status": "ok"}
-```
-
-### 4. Update database.py for Vercel
-
-**Critical:** Vercel serverless functions can only write to `/tmp`. Update the SQLite path:
-
-```python
-SQLALCHEMY_DATABASE_URL = "sqlite:////tmp/app.db"
-```
-
-### 5. Seed ALL Required Data
-
-**This is the #1 gotcha.** Since `/tmp` is ephemeral, every cold start gets a fresh database. If your frontend assumes certain data exists (like user ID 1), you MUST seed it:
-
-```python
-def seed_default_user(db: Session):
-    count = db.query(UserProfile).count()
-    if count > 0:
-        return
-    user = UserProfile(name="Demo User", ...)
-    db.add(user)
-    db.commit()
-```
-
-### 6. Create vercel.json
-
-```json
-{
-  "rewrites": [
-    { "source": "/api/(.*)", "destination": "/api/index.py" },
-    { "source": "/((?!assets/).*)", "destination": "/index.html" }
-  ]
-}
-```
-
-This routes:
-- `/api/*` → Python serverless function
-- Everything else → React SPA (index.html)
-
-### 7. Deploy
-
-```bash
-cd <project>/vercel-deploy
-vercel --yes --prod
-```
-
-### 8. Verify
-
-```bash
-curl -s <deployed-url>/api/health
-# Should return: {"status":"ok"}
-```
-
-## Gotchas & Limitations
-
-| Issue | Solution |
-|-------|----------|
-| SQLite resets on cold start | Seed ALL required data in index.py startup |
-| No persistent storage | Acceptable for demos. For production, use Vercel Postgres or Supabase |
-| No auth | Fine for demos/portfolios. Add auth layer for real apps |
-| `requirements.txt` location | Must be inside `api/` folder (next to index.py) |
-| Module imports in routers | Use `sys.path.insert(0, os.path.dirname(__file__))` in index.py |
-| CORS | Set `allow_origins=["*"]` for demo deployments |
-| `--name` flag deprecated | Don't use `--name` with Vercel CLI, just deploy from the directory |
-
-## Vercel CLI Quick Reference
-
-```bash
-npm install -g vercel    # Install
-vercel login             # Authenticate (opens browser)
-vercel --yes --prod      # Deploy to production (skip prompts)
-vercel logs --project <name>  # Check function logs
-```