[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSTXVEKH684FJN78PNGQ73":3,"skill-same:01M6FSTXVEKH684FJN78PNGQ73":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6FSTXVEKH684FJN78PNGQ73","vercel-automation",null,"Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fvercel-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"automation","vercel automation","vercel","domains","MCP","via","env","composio","community","manage","deployments","automate","projects","first","Tools","dns","env vars","search","teams","tasks","2026-11-10 10:12:30",false,"---\nname: vercel-automation\ndescription: \"Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Vercel Automation via Rube MCP\n\nAutomate Vercel platform operations through Composio's Vercel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Vercel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Vercel OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Monitor and Inspect Deployments\n\n**When to use**: User wants to list, inspect, or debug deployments\n\n**Tool sequence**:\n1. `VERCEL_LIST_ALL_DEPLOYMENTS` or `VERCEL_GET_DEPLOYMENTS` - List deployments with filters [Required]\n2. `VERCEL_GET_DEPLOYMENT` or `VERCEL_GET_DEPLOYMENT_DETAILS` - Get specific deployment info [Optional]\n3. `VERCEL_GET_DEPLOYMENT_LOGS` or `VERCEL_GET_RUNTIME_LOGS` - View build\u002Fruntime logs [Optional]\n4. `VERCEL_GET_DEPLOYMENT_EVENTS` - Get deployment event timeline [Optional]\n5. `VERCEL_LIST_DEPLOYMENT_CHECKS` - View deployment check results [Optional]\n\n**Key parameters**:\n- `projectId`: Filter deployments by project\n- `state`: Filter by deployment state (e.g., 'READY', 'ERROR', 'BUILDING')\n- `limit`: Number of deployments to return\n- `target`: Filter by environment ('production', 'preview')\n- `deploymentId` or `idOrUrl`: Specific deployment identifier\n\n**Pitfalls**:\n- Deployment IDs and URLs are both accepted as identifiers in most endpoints\n- Build logs and runtime logs are separate; use the appropriate tool\n- `VERCEL_GET_DEPLOYMENT_LOGS` returns build logs; `VERCEL_GET_RUNTIME_LOGS` returns serverless function logs\n- Deployment events include status transitions and are useful for debugging timing issues\n\n### 2. Create and Manage Deployments\n\n**When to use**: User wants to trigger a new deployment\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - Find the target project [Prerequisite]\n2. `VERCEL_CREATE_NEW_DEPLOYMENT` - Trigger a new deployment [Required]\n3. `VERCEL_GET_DEPLOYMENT` - Monitor deployment progress [Optional]\n\n**Key parameters**:\n- `name`: Project name for the deployment\n- `target`: Deployment target ('production' or 'preview')\n- `gitSource`: Git repository source with ref\u002Fbranch info\n- `files`: Array of file objects for file-based deployments\n\n**Pitfalls**:\n- Either `gitSource` or `files` must be provided, not both\n- Git-based deployments require proper repository integration\n- Production deployments update the production domain alias automatically\n- Deployment creation is asynchronous; poll with GET_DEPLOYMENT for status\n\n### 3. Manage Environment Variables\n\n**When to use**: User wants to add, list, or remove environment variables for a project\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - Find the project ID [Prerequisite]\n2. `VERCEL_LIST_ENV_VARIABLES` - List existing env vars [Required]\n3. `VERCEL_ADD_ENVIRONMENT_VARIABLE` - Add a new env var [Optional]\n4. `VERCEL_DELETE_ENVIRONMENT_VARIABLE` - Remove an env var [Optional]\n\n**Key parameters**:\n- `projectId`: Target project identifier\n- `key`: Environment variable name\n- `value`: Environment variable value\n- `target`: Array of environments ('production', 'preview', 'development')\n- `type`: Variable type ('plain', 'secret', 'encrypted', 'sensitive')\n\n**Pitfalls**:\n- Environment variable names must be unique per target environment\n- `type: 'secret'` variables cannot be read back after creation; only the ID is returned\n- Deleting an env var requires both `projectId` and the env var `id` (not the key name)\n- Changes require a new deployment to take effect\n\n### 4. Manage Domains and DNS\n\n**When to use**: User wants to configure custom domains or manage DNS records\n\n**Tool sequence**:\n1. `VERCEL_GET_DOMAIN` - Check domain status and configuration [Required]\n2. `VERCEL_GET_DOMAIN_CONFIG` - Get DNS\u002FSSL configuration details [Optional]\n3. `VERCEL_LIST_PROJECT_DOMAINS` - List domains attached to a project [Optional]\n4. `VERCEL_GET_DNS_RECORDS` - List DNS records for a domain [Optional]\n5. `VERCEL_CREATE_DNS_RECORD` - Add a new DNS record [Optional]\n6. `VERCEL_UPDATE_DNS_RECORD` - Modify an existing DNS record [Optional]\n\n**Key parameters**:\n- `domain`: Domain name (e.g., 'example.com')\n- `name`: DNS record name\u002Fsubdomain\n- `type`: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV')\n- `value`: DNS record value\n- `ttl`: Time-to-live in seconds\n\n**Pitfalls**:\n- Domain must be added to the Vercel account before DNS management\n- SSL certificates are auto-provisioned but may take time for new domains\n- CNAME records at the apex domain are not supported; use A records instead\n- MX records require priority values\n\n### 5. Manage Projects\n\n**When to use**: User wants to list, inspect, or update project settings\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - List all projects [Required]\n2. `VERCEL_GET_PROJECT` - Get detailed project information [Optional]\n3. `VERCEL_UPDATE_PROJECT` - Modify project settings [Optional]\n\n**Key parameters**:\n- `idOrName`: Project ID or name for lookup\n- `name`: Project name for updates\n- `framework`: Framework preset (e.g., 'nextjs', 'vite', 'remix')\n- `buildCommand`: Custom build command override\n- `rootDirectory`: Root directory if not repo root\n\n**Pitfalls**:\n- Project names are globally unique within a team\u002Faccount\n- Changing framework settings affects subsequent deployments\n- `rootDirectory` is relative to the repository root\n\n### 6. Team Management\n\n**When to use**: User wants to view team info or list team members\n\n**Tool sequence**:\n1. `VERCEL_LIST_TEAMS` - List all teams the user belongs to [Required]\n2. `VERCEL_GET_TEAM` - Get detailed team information [Optional]\n3. `VERCEL_GET_TEAM_MEMBERS` - List members of a specific team [Optional]\n\n**Key parameters**:\n- `teamId`: Team identifier\n- `limit`: Number of results per page\n- `role`: Filter members by role\n\n**Pitfalls**:\n- Team operations require appropriate team-level permissions\n- Personal accounts have no teams; team endpoints return empty results\n- Member roles include 'OWNER', 'MEMBER', 'DEVELOPER', 'VIEWER'\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call VERCEL_LIST_PROJECTS\n2. Find project by name in response\n3. Extract id field for subsequent operations\n```\n\n**Domain -> DNS Records**:\n```\n1. Call VERCEL_GET_DNS_RECORDS with domain name\n2. Extract record IDs for update\u002Fdelete operations\n```\n\n### Pagination\n\n- Use `limit` parameter to control page size\n- Check response for pagination tokens or `next` fields\n- Continue fetching until no more pages are indicated\n\n## Known Pitfalls\n\n**Deployment States**:\n- States include: INITIALIZING, ANALYZING, BUILDING, DEPLOYING, READY, ERROR, CANCELED, QUEUED\n- Only READY deployments are live and serving traffic\n- ERROR deployments should be inspected via logs for failure details\n\n**Environment Variables**:\n- Secret type vars are write-only; values cannot be retrieved after creation\n- Env vars are scoped to environments (production, preview, development)\n- A redeployment is needed for env var changes to take effect\n\n**Rate Limits**:\n- Vercel API has rate limits per endpoint\n- Implement backoff on 429 responses\n- Batch operations where possible to reduce API calls\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | VERCEL_LIST_PROJECTS | limit |\n| Get project details | VERCEL_GET_PROJECT | idOrName |\n| Update project | VERCEL_UPDATE_PROJECT | idOrName, name, framework |\n| List deployments | VERCEL_LIST_ALL_DEPLOYMENTS | projectId, state, limit |\n| Get deployment | VERCEL_GET_DEPLOYMENT | idOrUrl |\n| Create deployment | VERCEL_CREATE_NEW_DEPLOYMENT | name, target, gitSource |\n| Deployment logs | VERCEL_GET_DEPLOYMENT_LOGS | deploymentId |\n| Runtime logs | VERCEL_GET_RUNTIME_LOGS | deploymentId |\n| List env vars | VERCEL_LIST_ENV_VARIABLES | projectId |\n| Add env var | VERCEL_ADD_ENVIRONMENT_VARIABLE | projectId, key, value, target |\n| Delete env var | VERCEL_DELETE_ENVIRONMENT_VARIABLE | projectId, id |\n| Get domain | VERCEL_GET_DOMAIN | domain |\n| Get domain config | VERCEL_GET_DOMAIN_CONFIG | domain |\n| List DNS records | VERCEL_GET_DNS_RECORDS | domain |\n| Create DNS record | VERCEL_CREATE_DNS_RECORD | domain, name, type, value |\n| Update DNS record | VERCEL_UPDATE_DNS_RECORD | domain, recordId |\n| List project domains | VERCEL_LIST_PROJECT_DOMAINS | projectId |\n| List teams | VERCEL_LIST_TEAMS | (none) |\n| Get team | VERCEL_GET_TEAM | teamId |\n| Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Vercel Automation via Rube MCP\n\nAutomate Vercel platform operations through Composio's Vercel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Vercel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Vercel OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Monitor and Inspect Deployments\n\n**When to use**: User wants to list, inspect, or debug deployments\n\n**Tool sequence**:\n1. `VERCEL_LIST_ALL_DEPLOYMENTS` or `VERCEL_GET_DEPLOYMENTS` - List deployments with filters [Required]\n2. `VERCEL_GET_DEPLOYMENT` or `VERCEL_GET_DEPLOYMENT_DETAILS` - Get specific deployment info [Optional]\n3. `VERCEL_GET_DEPLOYMENT_LOGS` or `VERCEL_GET_RUNTIME_LOGS` - View build\u002Fruntime logs [Optional]\n4. `VERCEL_GET_DEPLOYMENT_EVENTS` - Get deployment event timeline [Optional]\n5. `VERCEL_LIST_DEPLOYMENT_CHECKS` - View deployment check results [Optional]\n\n**Key parameters**:\n- `projectId`: Filter deployments by project\n- `state`: Filter by deployment state (e.g., 'READY', 'ERROR', 'BUILDING')\n- `limit`: Number of deployments to return\n- `target`: Filter by environment ('production', 'preview')\n- `deploymentId` or `idOrUrl`: Specific deployment identifier\n\n**Pitfalls**:\n- Deployment IDs and URLs are both accepted as identifiers in most endpoints\n- Build logs and runtime logs are separate; use the appropriate tool\n- `VERCEL_GET_DEPLOYMENT_LOGS` returns build logs; `VERCEL_GET_RUNTIME_LOGS` returns serverless function logs\n- Deployment events include status transitions and are useful for debugging timing issues\n\n### 2. Create and Manage Deployments\n\n**When to use**: User wants to trigger a new deployment\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - Find the target project [Prerequisite]\n2. `VERCEL_CREATE_NEW_DEPLOYMENT` - Trigger a new deployment [Required]\n3. `VERCEL_GET_DEPLOYMENT` - Monitor deployment progress [Optional]\n\n**Key parameters**:\n- `name`: Project name for the deployment\n- `target`: Deployment target ('production' or 'preview')\n- `gitSource`: Git repository source with ref\u002Fbranch info\n- `files`: Array of file objects for file-based deployments\n\n**Pitfalls**:\n- Either `gitSource` or `files` must be provided, not both\n- Git-based deployments require proper repository integration\n- Production deployments update the production domain alias automatically\n- Deployment creation is asynchronous; poll with GET_DEPLOYMENT for status\n\n### 3. Manage Environment Variables\n\n**When to use**: User wants to add, list, or remove environment variables for a project\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - Find the project ID [Prerequisite]\n2. `VERCEL_LIST_ENV_VARIABLES` - List existing env vars [Required]\n3. `VERCEL_ADD_ENVIRONMENT_VARIABLE` - Add a new env var [Optional]\n4. `VERCEL_DELETE_ENVIRONMENT_VARIABLE` - Remove an env var [Optional]\n\n**Key parameters**:\n- `projectId`: Target project identifier\n- `key`: Environment variable name\n- `value`: Environment variable value\n- `target`: Array of environments ('production', 'preview', 'development')\n- `type`: Variable type ('plain', 'secret', 'encrypted', 'sensitive')\n\n**Pitfalls**:\n- Environment variable names must be unique per target environment\n- `type: 'secret'` variables cannot be read back after creation; only the ID is returned\n- Deleting an env var requires both `projectId` and the env var `id` (not the key name)\n- Changes require a new deployment to take effect\n\n### 4. Manage Domains and DNS\n\n**When to use**: User wants to configure custom domains or manage DNS records\n\n**Tool sequence**:\n1. `VERCEL_GET_DOMAIN` - Check domain status and configuration [Required]\n2. `VERCEL_GET_DOMAIN_CONFIG` - Get DNS\u002FSSL configuration details [Optional]\n3. `VERCEL_LIST_PROJECT_DOMAINS` - List domains attached to a project [Optional]\n4. `VERCEL_GET_DNS_RECORDS` - List DNS records for a domain [Optional]\n5. `VERCEL_CREATE_DNS_RECORD` - Add a new DNS record [Optional]\n6. `VERCEL_UPDATE_DNS_RECORD` - Modify an existing DNS record [Optional]\n\n**Key parameters**:\n- `domain`: Domain name (e.g., 'example.com')\n- `name`: DNS record name\u002Fsubdomain\n- `type`: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV')\n- `value`: DNS record value\n- `ttl`: Time-to-live in seconds\n\n**Pitfalls**:\n- Domain must be added to the Vercel account before DNS management\n- SSL certificates are auto-provisioned but may take time for new domains\n- CNAME records at the apex domain are not supported; use A records instead\n- MX records require priority values\n\n### 5. Manage Projects\n\n**When to use**: User wants to list, inspect, or update project settings\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - List all projects [Required]\n2. `VERCEL_GET_PROJECT` - Get detailed project information [Optional]\n3. `VERCEL_UPDATE_PROJECT` - Modify project settings [Optional]\n\n**Key parameters**:\n- `idOrName`: Project ID or name for lookup\n- `name`: Project name for updates\n- `framework`: Framework preset (e.g., 'nextjs', 'vite', 'remix')\n- `buildCommand`: Custom build command override\n- `rootDirectory`: Root directory if not repo root\n\n**Pitfalls**:\n- Project names are globally unique within a team\u002Faccount\n- Changing framework settings affects subsequent deployments\n- `rootDirectory` is relative to the repository root\n\n### 6. Team Management\n\n**When to use**: User wants to view team info or list team members\n\n**Tool sequence**:\n1. `VERCEL_LIST_TEAMS` - List all teams the user belongs to [Required]\n2. `VERCEL_GET_TEAM` - Get detailed team information [Optional]\n3. `VERCEL_GET_TEAM_MEMBERS` - List members of a specific team [Optional]\n\n**Key parameters**:\n- `teamId`: Team identifier\n- `limit`: Number of results per page\n- `role`: Filter members by role\n\n**Pitfalls**:\n- Team operations require appropriate team-level permissions\n- Personal accounts have no teams; team endpoints return empty results\n- Member roles include 'OWNER', 'MEMBER', 'DEVELOPER', 'VIEWER'\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call VERCEL_LIST_PROJECTS\n2. Find project by name in response\n3. Extract id field for subsequent operations\n```\n\n**Domain -> DNS Records**:\n```\n1. Call VERCEL_GET_DNS_RECORDS with domain name\n2. Extract record IDs for update\u002Fdelete operations\n```\n\n### Pagination\n\n- Use `limit` parameter to control page size\n- Check response for pagination tokens or `next` fields\n- Continue fetching until no more pages are indicated\n\n## Known Pitfalls\n\n**Deployment States**:\n- States include: INITIALIZING, ANALYZING, BUILDING, DEPLOYING, READY, ERROR, CANCELED, QUEUED\n- Only READY deployments are live and serving traffic\n- ERROR deployments should be inspected via logs for failure details\n\n**Environment Variables**:\n- Secret type vars are write-only; values cannot be retrieved after creation\n- Env vars are scoped to environments (production, preview, development)\n- A redeployment is needed for env var changes to take effect\n\n**Rate Limits**:\n- Vercel API has rate limits per endpoint\n- Implement backoff on 429 responses\n- Batch operations where possible to reduce API calls\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | VERCEL_LIST_PROJECTS | limit |\n| Get project details | VERCEL_GET_PROJECT | idOrName |\n| Update project | VERCEL_UPDATE_PROJECT | idOrName, name, framework |\n| List deployments | VERCEL_LIST_ALL_DEPLOYMENTS | projectId, state, limit |\n| Get deployment | VERCEL_GET_DEPLOYMENT | idOrUrl |\n| Create deployment | VERCEL_CREATE_NEW_DEPLOYMENT | name, target, gitSource |\n| Deployment logs | VERCEL_GET_DEPLOYMENT_LOGS | deploymentId |\n| Runtime logs | VERCEL_GET_RUNTIME_LOGS | deploymentId |\n| List env vars | VERCEL_LIST_ENV_VARIABLES | projectId |\n| Add env var | VERCEL_ADD_ENVIRONMENT_VARIABLE | projectId, key, value, target |\n| Delete env var | VERCEL_DELETE_ENVIRONMENT_VARIABLE | projectId, id |\n| Get domain | VERCEL_GET_DOMAIN | domain |\n| Get domain config | VERCEL_GET_DOMAIN_CONFIG | domain |\n| List DNS records | VERCEL_GET_DNS_RECORDS | domain |\n| Create DNS record | VERCEL_CREATE_DNS_RECORD | domain, name, type, value |\n| Update DNS record | VERCEL_UPDATE_DNS_RECORD | domain, recordId |\n| List project domains | VERCEL_LIST_PROJECT_DOMAINS | projectId |\n| List teams | VERCEL_LIST_TEAMS | (none) |\n| Get team | VERCEL_GET_TEAM | teamId |\n| Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":49,"source":32,"requires":50,"description":7},"unknown",{"mcp":51},[52],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fvercel-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add reikiplanet\u002Fdaoskills --skill vercel-automation",{"tool":67,"command":68},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill vercel-automation",{"tool":70,"command":71},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill vercel-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fvercel-automation\u002FSKILL.md",true,[],[76,102,114,128,148,171],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[83,84,85,86,87,88,32,89,90,91,92,93,94,95,96,97,98,99,100,101],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[109,110,100,111,112,32,90,91,92,86,113,87],"ar","vr ar","interaction","requirements","performance",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":44},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[116,121,122,123,124,125,32,126,92,36,127,86],"project scaffolding","From Scratch","tech","project","scaffolding","use","applications",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":44},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[135,136,137,138,139,32,140,141,142,143,126,144,145,146,147],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":44},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,32,92,86,163,87,164,165,166,167,168,169,170],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":44},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[178,179,180,181,182,183,184,185,168,126,186,187,188,32,189,190,191,165,192,193],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]