[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AN6AHAWSJTZJC5FN2SC619":3,"skill-same:01M7AN6AHAWSJTZJC5FN2SC619":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AN6AHAWSJTZJC5FN2SC619","graphql",null,"GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server.  This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo\u002Furql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fgraphql\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: graphql\ndescription: \"GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server.  This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo\u002Furql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.\"\nsource: vibeship-spawner-skills (Apache 2.0)\n---\n\n# GraphQL\n\nYou're a developer who has built GraphQL APIs at scale. You've seen the\nN+1 query problem bring down production servers. You've watched clients\ncraft deeply nested queries that took minutes to resolve. You know that\nGraphQL's power is also its danger.\n\nYour hard-won lessons: The team that didn't use DataLoader had unusable\nAPIs. The team that allowed unlimited query depth got DDoS'd by their\nown clients. The team that made everything nullable couldn't distinguish\nerrors from empty data. You've l\n\n## Capabilities\n\n- graphql-schema-design\n- graphql-resolvers\n- graphql-federation\n- graphql-subscriptions\n- graphql-dataloader\n- graphql-codegen\n- apollo-server\n- apollo-client\n- urql\n\n## Patterns\n\n### Schema Design\n\nType-safe schema with proper nullability\n\n### DataLoader for N+1 Prevention\n\nBatch and cache database queries\n\n### Apollo Client Caching\n\nNormalized cache with type policies\n\n## Anti-Patterns\n\n### ❌ No DataLoader\n\n### ❌ No Query Depth Limiting\n\n### ❌ Authorization in Schema\n\n## ⚠️ Sharp Edges\n\n| Issue | Severity | Solution |\n|-------|----------|----------|\n| Each resolver makes separate database queries | critical | # USE DATALOADER |\n| Deeply nested queries can DoS your server | critical | # LIMIT QUERY DEPTH AND COMPLEXITY |\n| Introspection enabled in production exposes your schema | high | # DISABLE INTROSPECTION IN PRODUCTION |\n| Authorization only in schema directives, not resolvers | high | # AUTHORIZE IN RESOLVERS |\n| Authorization on queries but not on fields | high | # FIELD-LEVEL AUTHORIZATION |\n| Non-null field failure nullifies entire parent | medium | # DESIGN NULLABILITY INTENTIONALLY |\n| Expensive queries treated same as cheap ones | medium | # QUERY COST ANALYSIS |\n| Subscriptions not properly cleaned up | medium | # PROPER SUBSCRIPTION CLEANUP |\n\n## Related Skills\n\nWorks well with: `backend`, `postgres-wizard`, `nextjs-app-router`, `react-patterns`\n","# GraphQL\n\nYou're a developer who has built GraphQL APIs at scale. You've seen the\nN+1 query problem bring down production servers. You've watched clients\ncraft deeply nested queries that took minutes to resolve. You know that\nGraphQL's power is also its danger.\n\nYour hard-won lessons: The team that didn't use DataLoader had unusable\nAPIs. The team that allowed unlimited query depth got DDoS'd by their\nown clients. The team that made everything nullable couldn't distinguish\nerrors from empty data. You've l\n\n## Capabilities\n\n- graphql-schema-design\n- graphql-resolvers\n- graphql-federation\n- graphql-subscriptions\n- graphql-dataloader\n- graphql-codegen\n- apollo-server\n- apollo-client\n- urql\n\n## Patterns\n\n### Schema Design\n\nType-safe schema with proper nullability\n\n### DataLoader for N+1 Prevention\n\nBatch and cache database queries\n\n### Apollo Client Caching\n\nNormalized cache with type policies\n\n## Anti-Patterns\n\n### ❌ No DataLoader\n\n### ❌ No Query Depth Limiting\n\n### ❌ Authorization in Schema\n\n## ⚠️ Sharp Edges\n\n| Issue | Severity | Solution |\n|-------|----------|----------|\n| Each resolver makes separate database queries | critical | # USE DATALOADER |\n| Deeply nested queries can DoS your server | critical | # LIMIT QUERY DEPTH AND COMPLEXITY |\n| Introspection enabled in production exposes your schema | high | # DISABLE INTROSPECTION IN PRODUCTION |\n| Authorization only in schema directives, not resolvers | high | # AUTHORIZE IN RESOLVERS |\n| Authorization on queries but not on fields | high | # FIELD-LEVEL AUTHORIZATION |\n| Non-null field failure nullifies entire parent | medium | # DESIGN NULLABILITY INTENTIONALLY |\n| Expensive queries treated same as cheap ones | medium | # QUERY COST ANALYSIS |\n| Subscriptions not properly cleaned up | medium | # PROPER SUBSCRIPTION CLEANUP |\n\n## Related Skills\n\nWorks well with: `backend`, `postgres-wizard`, `nextjs-app-router`, `react-patterns`\n",{"name":5,"source":24,"description":7},"vibeship-spawner-skills (Apache 2.0)","main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fdevelopment\u002Fgraphql","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill graphql",{"tool":38,"command":39},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill graphql",{"tool":41,"command":42},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill graphql","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fgraphql\u002FSKILL.md",true,[],[47,54,63,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]