[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NWQ4GXMQB5WK30MY112ZMB":3,"skill-same:01M6NWQ4GXMQB5WK30MY112ZMB":71},{"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":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6NWQ4GXMQB5WK30MY112ZMB","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.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-vercel\u002Fsickn33\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","search tools","MCP","for","domains","via","env","critical","community","manage","deployments","projects","first","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.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\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":33,"source":34,"date_added":49,"description":7},"2026-02-27","main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","integrate-vercel\u002Fsickn33\u002Fvercel-automation",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill vercel-automation",{"tool":63,"command":64},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill vercel-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill vercel-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-vercel\u002Fsickn33\u002Fvercel-automation\u002FSKILL.md",true,[],[72,106,120,139,160,186],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":86,"publishedAt":44},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[78,81],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[87,88,89,90,29,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105],"writing clearly and concisely","writing","concisely","text","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":44},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[113,114,88,115,116,97,117,118,119],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":44},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000038","人力资源",[130,131,132,133,134,135,136,137,34,138,104],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","onboarding",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":44},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[114,146,147,148,134,149,150,117,151,152,50,153,154,155,156,157,104,158,159],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":44},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[167,168,97,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":194,"publishedAt":44},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[192,193],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[195,196,179,156,88,197,94,198,199,200,201,202,203,204,205,101,206,207,105,208],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]