[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B20FDAS8WPXF67GSVHYFCY":3,"skill-same:01M7B20FDAS8WPXF67GSVHYFCY":51},{"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":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7B20FDAS8WPXF67GSVHYFCY","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.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\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.\nmetadata:\n  version: \"1.0.0\"\n  origin: ECC direct-port adaptation\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,"metadata":24,"description":7},{"origin":25,"version":26},"ECC direct-port adaptation","1.0.0","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fapi-connector-builder",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill api-connector-builder",{"tool":43,"command":44},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill api-connector-builder",{"tool":46,"command":47},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill api-connector-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fapi-connector-builder\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]