[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6KSZ2AWS7SP2WTH44QETR":3,"skill-same:01M7F6KSZ2AWS7SP2WTH44QETR":49},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F6KSZ2AWS7SP2WTH44QETR","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fvercel-automation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fvercel-automation",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill vercel-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill vercel-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill vercel-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fvercel-automation\u002FSKILL.md",true,[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"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":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]