[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWXKAENP3PFFC5D34R9XD4":3,"skill-same:01M7EWXKAENP3PFFC5D34R9XD4":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7EWXKAENP3PFFC5D34R9XD4","api-connector-builder",null,"Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.","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-技能与代理开发\u002Fapi-connector-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: api-connector-builder\ndescription: Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.\norigin: ECC direct-port adaptation\nversion: \"1.0.0\"\n---\n\n# API Connector Builder\n\nUse this when the job is to add a repo-native integration surface, not just a generic HTTP client.\n\nThe point is to match the host repository's pattern:\n\n- connector layout\n- config schema\n- auth model\n- error handling\n- test style\n- registration\u002Fdiscovery wiring\n\n## When to Use\n\n- \"Build a Jira connector for this project\"\n- \"Add a Slack provider following the existing pattern\"\n- \"Create a new integration for this API\"\n- \"Build a plugin that matches the repo's connector style\"\n\n## Guardrails\n\n- do not invent a new integration architecture when the repo already has one\n- do not start from vendor docs alone; start from existing in-repo connectors first\n- do not stop at transport code if the repo expects registry wiring, tests, and docs\n- do not cargo-cult old connectors if the repo has a newer current pattern\n\n## Workflow\n\n### 1. Learn the house style\n\nInspect at least 2 existing connectors\u002Fproviders and map:\n\n- file layout\n- abstraction boundaries\n- config model\n- retry \u002F pagination conventions\n- registry hooks\n- test fixtures and naming\n\n### 2. Narrow the target integration\n\nDefine only the surface the repo actually needs:\n\n- auth flow\n- key entities\n- core read\u002Fwrite operations\n- pagination and rate limits\n- webhook or polling model\n\n### 3. Build in repo-native layers\n\nTypical slices:\n\n- config\u002Fschema\n- client\u002Ftransport\n- mapping layer\n- connector\u002Fprovider entrypoint\n- registration\n- tests\n\n### 4. Validate against the source pattern\n\nThe new connector should look obvious in the codebase, not imported from a different ecosystem.\n\n## Reference Shapes\n\n### Provider-style\n\n```text\nproviders\u002F\n  existing_provider\u002F\n    __init__.py\n    provider.py\n    config.py\n```\n\n### Connector-style\n\n```text\nintegrations\u002F\n  existing\u002F\n    client.py\n    models.py\n    connector.py\n```\n\n### TypeScript plugin-style\n\n```text\nsrc\u002Fintegrations\u002F\n  existing\u002F\n    index.ts\n    client.ts\n    types.ts\n    test.ts\n```\n\n## Quality Checklist\n\n- [ ] matches an existing in-repo integration pattern\n- [ ] config validation exists\n- [ ] auth and error handling are explicit\n- [ ] pagination\u002Fretry behavior follows repo norms\n- [ ] registry\u002Fdiscovery wiring is complete\n- [ ] tests mirror the host repo's style\n- [ ] docs\u002Fexamples are updated if expected by the repo\n\n## Related Skills\n\n- `backend-patterns`\n- `mcp-server-patterns`\n- `github-ops`\n\n","# API Connector Builder\n\nUse this when the job is to add a repo-native integration surface, not just a generic HTTP client.\n\nThe point is to match the host repository's pattern:\n\n- connector layout\n- config schema\n- auth model\n- error handling\n- test style\n- registration\u002Fdiscovery wiring\n\n## When to Use\n\n- \"Build a Jira connector for this project\"\n- \"Add a Slack provider following the existing pattern\"\n- \"Create a new integration for this API\"\n- \"Build a plugin that matches the repo's connector style\"\n\n## Guardrails\n\n- do not invent a new integration architecture when the repo already has one\n- do not start from vendor docs alone; start from existing in-repo connectors first\n- do not stop at transport code if the repo expects registry wiring, tests, and docs\n- do not cargo-cult old connectors if the repo has a newer current pattern\n\n## Workflow\n\n### 1. Learn the house style\n\nInspect at least 2 existing connectors\u002Fproviders and map:\n\n- file layout\n- abstraction boundaries\n- config model\n- retry \u002F pagination conventions\n- registry hooks\n- test fixtures and naming\n\n### 2. Narrow the target integration\n\nDefine only the surface the repo actually needs:\n\n- auth flow\n- key entities\n- core read\u002Fwrite operations\n- pagination and rate limits\n- webhook or polling model\n\n### 3. Build in repo-native layers\n\nTypical slices:\n\n- config\u002Fschema\n- client\u002Ftransport\n- mapping layer\n- connector\u002Fprovider entrypoint\n- registration\n- tests\n\n### 4. Validate against the source pattern\n\nThe new connector should look obvious in the codebase, not imported from a different ecosystem.\n\n## Reference Shapes\n\n### Provider-style\n\n```text\nproviders\u002F\n  existing_provider\u002F\n    __init__.py\n    provider.py\n    config.py\n```\n\n### Connector-style\n\n```text\nintegrations\u002F\n  existing\u002F\n    client.py\n    models.py\n    connector.py\n```\n\n### TypeScript plugin-style\n\n```text\nsrc\u002Fintegrations\u002F\n  existing\u002F\n    index.ts\n    client.ts\n    types.ts\n    test.ts\n```\n\n## Quality Checklist\n\n- [ ] matches an existing in-repo integration pattern\n- [ ] config validation exists\n- [ ] auth and error handling are explicit\n- [ ] pagination\u002Fretry behavior follows repo norms\n- [ ] registry\u002Fdiscovery wiring is complete\n- [ ] tests mirror the host repo's style\n- [ ] docs\u002Fexamples are updated if expected by the repo\n\n## Related Skills\n\n- `backend-patterns`\n- `mcp-server-patterns`\n- `github-ops`\n\n",{"name":5,"origin":24,"version":25,"description":7},"ECC direct-port adaptation","1.0.0","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fapi-connector-builder",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill api-connector-builder",{"tool":40,"command":41},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill api-connector-builder",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill api-connector-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fapi-connector-builder\u002FSKILL.md",true,[],[49,57,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"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",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":51,"nameZh":6,"description":52,"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":56},"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":56},"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":56},"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":56},"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":56},"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",[],[]]