[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DYPFBCERFQX5T2XFRCFTFC":3,"skill-same:01M6DYPFBCERFQX5T2XFRCFTFC":77},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6DYPFBCERFQX5T2XFRCFTFC","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.","Aceryoung\u002Ffamilyproject","Aceryoung","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75876477?v=4","01M6DY8Q14MHFC0JX3G14KK9CW","kkong","01M6DY8Q58SY27PE2AH6GFZP9Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fgraphql\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"GraphQL","introspection","contract","but","craft","apollo","queries","api documentation","schema design","schema","api","design","prevention","federation","data","server","integration","microservices","apache","documentation","2026-11-10 10:12:30",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":49,"description":7},"vibeship-spawner-skills (Apache 2.0)","main","483e87f6ad1460beac541f70200e988102e5c385","antigravity-awesome-skills-main\u002Fskills\u002Fgraphql","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject","https:\u002F\u002Ffamilyproject-iota.vercel.app","https:\u002F\u002Fgithub.com\u002FAceryoung","2026-09-04 09:36:44",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add Aceryoung\u002Ffamilyproject --skill graphql",{"tool":63,"command":64},"bunx","bunx skills add Aceryoung\u002Ffamilyproject --skill graphql",{"tool":66,"command":67},"pnpm","pnpm dlx skills add Aceryoung\u002Ffamilyproject --skill graphql","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fgraphql\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fgithub-api-cheatsheet.md","REFERENCE","参考文档",6092,"https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fgithub\u002Fgithub-repo-management\u002Freferences\u002Fgithub-api-cheatsheet.md",[78,106,139,159,173,198],{"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":87,"publishedAt":44},"01M6DZ9PNJVNQ1M7196KMPEHZC","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\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[88,89,90,91,92,93,94,27,95,96,97,98,99,100,101,102,42,103,104,105],"zapier make patterns","patterns","workflow","integrations","how to","apps","platform","build","complexity","power","simplicity","use","business","automate","how","code","automation","writing",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":118,"publishedAt":44},"01M6DZ9K3385QP8QC2F3ZHZH1W","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[112,115],{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138],"html injection testing","Cross Site Scripting and HTML Injection Testing","injection","scripting","site","html","testing","vectors","exploit","applications","xss","cookies","content","web","test","steal","client","via","security","vulnerabilities",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":154,"publishedAt":44},"01M6DZ9B72D51Q21DTFD63TVEN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[145,146,149],{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[105,155,156,99,157,158],"writing skills","deployment","editing","work",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":167,"publishedAt":44},"01M6DZ98HBB74FXZS78BATF6P5","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[165,166],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},[168,105,169,170,171,99,103,172],"writing plans","plans","requirements","task","spec",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":44},"01M6DZ94C3FCDXCTV795CTRP1V","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\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[179],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[181,104,90,182,183,184,42,185,186,187,188,189,190,191,192,193,194,195,196,197],"Workflow Automation","Production","flow","network","workflows","accessibility","ai agents","execution","scripts","worker","payment","n8n","money","resume","orchestrator","parallel","inngest",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":44},"01M6DZ90RQ8GCWE9CGPCMHMNDD","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[204],{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},[125,200,206,207,208,209,210,211,127,99,212,213,214,138,137],"penetration testing","wordpress","security assessment","sites","scan","pentest","user","plugins","assessment"]