[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BFP5PWJS2GJHERFX2BRM15":3,"skill-same:01M7BFP5PWJS2GJHERFX2BRM15":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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7BFP5PWJS2GJHERFX2BRM15","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.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\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","# 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",{"name":5,"origin":24,"version":25,"description":7},"ECC direct-port adaptation","1.0.0","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\u002Fapi-connector-builder",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill api-connector-builder",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill api-connector-builder",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill api-connector-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\u002Fapi-connector-builder\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"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},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]