opencode-starterkit 1.0.1

package/baseline/skill/v0/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: v0
+description: AI-powered UI generation via v0 MCP. Create chats, generate React components, get design assistance. Use when building UI components, dashboards, or need AI design help.
+mcp:
+  v0:
+    command: npx
+    args: ["mcp-remote", "https://mcp.v0.dev", "--header", "Authorization: Bearer ${V0_API_KEY}"]
+    env:
+      V0_API_KEY: "${V0_API_KEY}"
+version: 1.0.0
+tags: [ui, mcp, design]
+dependencies: []
+---
+
+# v0 AI Code Generation (MCP)
+
+## When to Use
+
+- When you need AI-generated UI components or chat-based design iteration via v0.
+
+## When NOT to Use
+
+- When you need to implement UI from a fixed design system without AI generation.
+
+
+## Prerequisites
+
+Set your v0 API key as an environment variable:
+
+```bash
+export V0_API_KEY="your-v0-api-key"
+```
+
+To get your v0 API key:
+
+1. Go to [v0 account settings](https://v0.app/chat/settings/keys)
+2. Create a new API key
+3. Copy and set as environment variable
+
+## Quick Start
+
+After loading this skill, list available tools:
+
+```
+skill_mcp(skill_name="v0", list_tools=true)
+```
+
+Then invoke tools:
+
+```
+skill_mcp(skill_name="v0", tool_name="create_chat", arguments='{"prompt": "Create a React dashboard component with a sidebar"}')
+```
+
+## Available Tools
+
+### create_chat
+
+Create a new v0 chat with a prompt.
+
+| Parameter | Type   | Required | Description                        |
+| --------- | ------ | -------- | ---------------------------------- |
+| `prompt`  | string | Yes      | The prompt for v0 to generate code |
+
+**Example:**
+
+```
+skill_mcp(skill_name="v0", tool_name="create_chat", arguments='{"prompt": "Build a responsive navbar with dark mode toggle"}')
+```
+
+### get_chat
+
+Get details about an existing chat.
+
+| Parameter | Type   | Required | Description    |
+| --------- | ------ | -------- | -------------- |
+| `chatId`  | string | Yes      | The v0 chat ID |
+
+**Example:**
+
+```
+skill_mcp(skill_name="v0", tool_name="get_chat", arguments='{"chatId": "abc123"}')
+```
+
+### find_chats
+
+Search through your v0 chats.
+
+| Parameter | Type   | Required | Description  |
+| --------- | ------ | -------- | ------------ |
+| `query`   | string | No       | Search query |
+
+**Example:**
+
+```
+skill_mcp(skill_name="v0", tool_name="find_chats", arguments='{"query": "React components"}')
+```
+
+### send_message
+
+Continue a conversation in an existing chat.
+
+| Parameter | Type   | Required | Description     |
+| --------- | ------ | -------- | --------------- |
+| `chatId`  | string | Yes      | The v0 chat ID  |
+| `message` | string | Yes      | Message to send |
+
+**Example:**
+
+```
+skill_mcp(skill_name="v0", tool_name="send_message", arguments='{"chatId": "abc123", "message": "Add dark mode support"}')
+```
+
+## Workflow
+
+### 1. Generate a New Component
+
+```
+# Create a new chat with your requirements
+skill_mcp(skill_name="v0", tool_name="create_chat", arguments='{"prompt": "Create a modern pricing table with 3 tiers using Tailwind CSS"}')
+
+# The response includes a chat ID and generated code
+```
+
+### 2. Iterate on Design
+
+```
+# Send follow-up messages to refine
+skill_mcp(skill_name="v0", tool_name="send_message", arguments='{"chatId": "chat-id-here", "message": "Make the recommended tier more prominent with a gradient border"}')
+```
+
+### 3. Search Previous Work
+
+```
+# Find relevant previous chats
+skill_mcp(skill_name="v0", tool_name="find_chats", arguments='{"query": "dashboard"}')
+```
+
+## Use Cases
+
+- **Component Generation**: Create React/Next.js components from descriptions
+- **UI Prototyping**: Rapidly prototype UI ideas
+- **Design Iteration**: Refine designs through conversation
+- **Code Assistance**: Get help with Tailwind CSS, responsive design, etc.
+
+## Tips
+
+- **Be specific** in prompts - include framework (React, Next.js), styling (Tailwind, CSS), and functionality details
+- **Iterate** using `send_message` rather than creating new chats for refinements
+- **Search first** with `find_chats` to reuse previous work
+- **Include context** about your existing design system or component patterns
+
+## Troubleshooting
+
+**"Invalid API key"**: Ensure `V0_API_KEY` environment variable is set correctly.
+
+**"Rate limit exceeded"**: v0 has usage limits. Wait a few minutes or check your plan.
+
+**"Chat not found"**: Verify the chat ID is correct. Use `find_chats` to list available chats.

package/baseline/skill/v1-run/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: v1-run
+description: npm package intelligence via MCP. Real-time versions, vulnerability data, health scores, and package comparisons. Use when selecting npm packages, checking for vulnerabilities, or comparing alternatives.
+version: 1.0.0
+tags: [integration, mcp, research]
+dependencies: []
+---
+
+# v1.run MCP
+
+## When to Use
+
+- When you need real-time npm package health, vulnerabilities, or comparisons.
+
+## When NOT to Use
+
+- When package selection or security analysis is not in scope.
+
+
+## Overview
+
+v1.run is an MCP-first npm registry by Midday.ai that provides:
+
+- **Real-time version data** - No hallucinated packages
+- **Security vulnerabilities** - From OSV database
+- **Health scores** - Automated 0-100 scoring
+- **Package comparisons** - 50+ pre-built categories
+
+## MCP Endpoint
+
+**URL**: `https://api.v1.run/mcp`
+
+**Authentication**: None required (public API)
+
+## Configuration
+
+v1.run MCP is pre-configured as a skill. Load it with:
+
+```typescript
+skill({ name: "v1-run" });
+```
+
+### Manual Setup (if needed)
+
+```json
+{
+  "mcpServers": {
+    "v1": {
+      "url": "https://api.v1.run/mcp"
+    }
+  }
+}
+```
+
+## Available Tools
+
+| Tool                    | Description                                                                                                       |
+| ----------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `get_package_health`    | Comprehensive health assessment (primary tool) - version, vulns, score, downloads, TS support, AI recommendations |
+| `get_package_version`   | Get latest version of a package                                                                                   |
+| `check_deprecated`      | Check if package is deprecated + get alternatives                                                                 |
+| `check_types`           | Check TypeScript support (bundled or @types)                                                                      |
+| `check_vulnerabilities` | Security vulnerabilities from OSV database                                                                        |
+| `find_alternatives`     | Find alternative packages with recommendations                                                                    |
+| `compare_packages`      | Side-by-side comparison (2-5 packages)                                                                            |
+
+## Health Score System
+
+Packages are scored 0-100 based on:
+
+| Factor      | Weight | Measures                                |
+| ----------- | ------ | --------------------------------------- |
+| Downloads   | 20%    | Weekly downloads + trend direction      |
+| Bundle Size | 20%    | Smaller gzip = higher score             |
+| Freshness   | 25%    | Recent commits and releases             |
+| Community   | 10%    | Stars, contributors                     |
+| Quality     | 25%    | TypeScript, ESM, security, tree-shaking |
+
+## Usage Examples
+
+### Check Package Health
+
+```typescript
+// Get comprehensive health info for a package (primary tool)
+skill_mcp({ skill_name: "v1-run", tool_name: "get_package_health", arguments: '{"name": "zod"}' });
+```
+
+Response includes:
+
+- Latest version
+- Known vulnerabilities (CVEs)
+- Health score (0-100) with grade
+- Weekly downloads + trend
+- TypeScript support
+- Maintenance status
+- AI recommendation
+
+### Check for Deprecation
+
+```typescript
+// Check if package is deprecated and get alternatives
+skill_mcp({
+  skill_name: "v1-run",
+  tool_name: "check_deprecated",
+  arguments: '{"name": "request"}',
+});
+```
+
+### Check Vulnerabilities
+
+```typescript
+// Check specific version for security issues
+skill_mcp({
+  skill_name: "v1-run",
+  tool_name: "check_vulnerabilities",
+  arguments: '{"name": "lodash", "version": "4.17.20"}',
+});
+```
+
+### Find Alternatives
+
+```typescript
+// Find alternative packages
+skill_mcp({
+  skill_name: "v1-run",
+  tool_name: "find_alternatives",
+  arguments: '{"name": "moment"}',
+});
+```
+
+### Compare Packages
+
+```typescript
+// Compare similar packages (2-5 packages)
+skill_mcp({
+  skill_name: "v1-run",
+  tool_name: "compare_packages",
+  arguments: '{"packages": ["zod", "yup", "joi", "valibot"]}',
+});
+```
+
+## Pre-built Categories (50+)
+
+v1.run includes comparisons for popular package categories:
+
+- **HTTP clients**: axios, got, ky, node-fetch
+- **Date libraries**: moment, date-fns, dayjs, luxon
+- **Validation**: zod, yup, joi, ajv, valibot
+- **State management**: redux, zustand, jotai, recoil
+- **ORM**: prisma, drizzle, typeorm, sequelize
+- **Testing**: vitest, jest, mocha, ava
+- **Bundlers**: vite, esbuild, webpack, rollup
+- **Logging**: pino, winston, bunyan
+
+## When to Use
+
+Use v1.run MCP when:
+
+1. **Choosing between packages** - Get objective comparisons
+2. **Checking for vulnerabilities** - Before adding dependencies
+3. **Evaluating maintenance** - Is the package actively maintained?
+4. **Finding alternatives** - Discover better options for a package
+
+## Best Practices
+
+1. **Always check health** before adding new dependencies
+2. **Compare alternatives** when multiple packages solve the same problem
+3. **Verify TypeScript support** for TypeScript projects
+4. **Check bundle size** for frontend applications
+
+## Documentation
+
+- [v1.run](https://v1.run)
+- [GitHub: midday-ai/v1](https://github.com/midday-ai/v1)
+- [MCP Documentation](https://modelcontextprotocol.io)

package/baseline/skill/v1-run/mcp.json

@@ -0,0 +1,6 @@
+{
+	"v1": {
+		"command": "npx",
+		"args": ["-y", "mcp-remote", "https://api.v1.run/mcp"]
+	}
+}

package/baseline/skill/vercel-deploy-claimable/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: vercel-deploy-claimable
+description: Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
+version: 1.0.0
+tags: [devops, integration]
+dependencies: []
+metadata:
+  author: vercel
+  version: "1.0.0"
+---
+
+# Vercel Deploy
+
+## When to Use
+
+- When the user requests deploying a project to Vercel and needs preview/claim links.
+
+## When NOT to Use
+
+- When deployment is not requested or targets a non-Vercel platform.
+
+
+## How It Works
+
+1. Packages your project into a tarball (excludes `node_modules` and `.git`)
+2. Auto-detects framework from `package.json`
+3. Uploads to deployment service
+4. Returns **Preview URL** (live site) and **Claim URL** (transfer to your Vercel account)
+
+## Usage
+
+```bash
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh [path]
+```
+
+**Arguments:**
+
+- `path` - Directory to deploy, or a `.tgz` file (defaults to current directory)
+
+**Examples:**
+
+```bash
+# Deploy current directory
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh
+
+# Deploy specific project
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project
+
+# Deploy existing tarball
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project.tgz
+```
+
+## Output
+
+```
+Preparing deployment...
+Detected framework: nextjs
+Creating deployment package...
+Deploying...
+✓ Deployment successful!
+
+Preview URL: https://skill-deploy-abc123.vercel.app
+Claim URL:   https://vercel.com/claim-deployment?code=...
+```
+
+The script also outputs JSON to stdout for programmatic use:
+
+```json
+{
+  "previewUrl": "https://skill-deploy-abc123.vercel.app",
+  "claimUrl": "https://vercel.com/claim-deployment?code=...",
+  "deploymentId": "dpl_...",
+  "projectId": "prj_..."
+}
+```
+
+## Framework Detection
+
+The script auto-detects frameworks from `package.json`. Supported frameworks include:
+
+- **React**: Next.js, Gatsby, Create React App, Remix, React Router
+- **Vue**: Nuxt, Vitepress, Vuepress, Gridsome
+- **Svelte**: SvelteKit, Svelte, Sapper
+- **Other Frontend**: Astro, Solid Start, Angular, Ember, Preact, Docusaurus
+- **Backend**: Express, Hono, Fastify, NestJS, Elysia, h3, Nitro
+- **Build Tools**: Vite, Parcel
+- **And more**: Blitz, Hydrogen, RedwoodJS, Storybook, Sanity, etc.
+
+For static HTML projects (no `package.json`), framework is set to `null`.
+
+## Static HTML Projects
+
+For projects without a `package.json`:
+
+- If there's a single `.html` file not named `index.html`, it gets renamed automatically
+- This ensures the page is served at the root URL (`/`)
+
+## Present Results to User
+
+Always show both URLs:
+
+```
+✓ Deployment successful!
+
+Preview URL: https://skill-deploy-abc123.vercel.app
+Claim URL:   https://vercel.com/claim-deployment?code=...
+
+View your site at the Preview URL.
+To transfer this deployment to your Vercel account, visit the Claim URL.
+```
+
+## Troubleshooting
+
+### Network Egress Error
+
+If deployment fails due to network restrictions (common on claude.ai), tell the user:
+
+```
+Deployment failed due to network restrictions. To fix this:
+
+1. Go to https://claude.ai/settings/capabilities
+2. Add *.vercel.com to the allowed domains
+3. Try deploying again
+```