[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H728D34MSYGMKBERVCP474":3,"skill-same:01M6H728D34MSYGMKBERVCP474":69},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H728D34MSYGMKBERVCP474","graphql-expert",null,"Use when implementing graphql functionality with production-grade patterns and safeguards.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fgraphql-expert\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35],"GraphQL","expert","graphql expert","codex","Production","api","use","backend","patterns","with","kit","implementing","2026-11-10 10:12:30",false,"---\nname: graphql-expert\ndescription: Use when implementing graphql functionality with production-grade patterns and safeguards.\nmetadata:\n  hermes:\n    tags: [codex-agent, backend-api]\n    source: codex-field-kit\u002Fbackend-api\n---\n\n# Graphql Expert\n\n## Focus Areas\n\n- Schema design with type safety and clear relationships\n- Query optimization for performance and efficiency\n- Best practices for designing scalable GraphQL APIs\n- Managing complex GraphQL queries and avoiding over-fetching\n- Effective use of GraphQL interfaces and unions\n- Security practices, including rate limiting and query complexity analysis\n- Implementing real-time data with GraphQL subscriptions\n- Thorough understanding of GraphQL introspection and its uses\n- Error handling strategies in GraphQL\n- Documentation strategies using GraphQL tools like SDL and GraphiQL\n\n## Approach\n\n- Begin with clear use cases before designing schema\n- Identify root types and connections for efficient queries\n- Utilize fragments to reduce query size and improve performance\n- Implement pagination with cursor-based approaches\n- Apply batching and caching to minimize database load\n- Use only necessary fields in the schema to avoid over-fetching\n- Regularly review and refine the schema with evolving needs\n- Ensure backward compatibility when updating the schema\n- Integrate linting tools to catch schema issues early\n- Monitor query performance and optimize as needed\n\n## Quality Checklist\n\n- Schema definitions are clear, concise, and well-documented\n- Queries fetch only required fields and data\n- API adheres to GraphQL best practices and standards\n- Efficient use of resolvers for optimal performance\n- Sufficient security measures are in place\n- Comprehensive tests cover all query and mutation scenarios\n- Subscriptions are implemented where real-time updates are needed\n- Full documentation for all schema types, queries, and mutations\n- API changes reviewed for backward compatibility\n- Robust error handling and meaningful response messages\n\n## Output\n\n- Well-structured GraphQL schemas and documentation\n- Optimized queries for improved performance\n- Secure and scalable GraphQL API implementation\n- Clear guidelines for clients on best practices in using the API\n- Automated tests for all aspects of the GraphQL implementation\n- Performance reports with suggestions for further optimization\n- Version control for schema changes with detailed changelog\n- Code examples demonstrating efficient use of the GraphQL API\n- GraphQL server configuration files with security settings\n- Monitoring and logging strategies for maintaining API health\n\n","# Graphql Expert\n\n## Focus Areas\n\n- Schema design with type safety and clear relationships\n- Query optimization for performance and efficiency\n- Best practices for designing scalable GraphQL APIs\n- Managing complex GraphQL queries and avoiding over-fetching\n- Effective use of GraphQL interfaces and unions\n- Security practices, including rate limiting and query complexity analysis\n- Implementing real-time data with GraphQL subscriptions\n- Thorough understanding of GraphQL introspection and its uses\n- Error handling strategies in GraphQL\n- Documentation strategies using GraphQL tools like SDL and GraphiQL\n\n## Approach\n\n- Begin with clear use cases before designing schema\n- Identify root types and connections for efficient queries\n- Utilize fragments to reduce query size and improve performance\n- Implement pagination with cursor-based approaches\n- Apply batching and caching to minimize database load\n- Use only necessary fields in the schema to avoid over-fetching\n- Regularly review and refine the schema with evolving needs\n- Ensure backward compatibility when updating the schema\n- Integrate linting tools to catch schema issues early\n- Monitor query performance and optimize as needed\n\n## Quality Checklist\n\n- Schema definitions are clear, concise, and well-documented\n- Queries fetch only required fields and data\n- API adheres to GraphQL best practices and standards\n- Efficient use of resolvers for optimal performance\n- Sufficient security measures are in place\n- Comprehensive tests cover all query and mutation scenarios\n- Subscriptions are implemented where real-time updates are needed\n- Full documentation for all schema types, queries, and mutations\n- API changes reviewed for backward compatibility\n- Robust error handling and meaningful response messages\n\n## Output\n\n- Well-structured GraphQL schemas and documentation\n- Optimized queries for improved performance\n- Secure and scalable GraphQL API implementation\n- Clear guidelines for clients on best practices in using the API\n- Automated tests for all aspects of the GraphQL implementation\n- Performance reports with suggestions for further optimization\n- Version control for schema changes with detailed changelog\n- Code examples demonstrating efficient use of the GraphQL API\n- GraphQL server configuration files with security settings\n- Monitoring and logging strategies for maintaining API health\n\n",{"name":5,"metadata":41,"description":7},{"hermes":42},{"tags":43,"source":46},[44,45],"codex-agent","backend-api","codex-field-kit\u002Fbackend-api","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fgraphql-expert",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill graphql-expert",{"tool":61,"command":62},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill graphql-expert",{"tool":64,"command":65},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill graphql-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fgraphql-expert\u002FSKILL.md",true,[],[70,100,119,129,154,181],{"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":79,"publishedAt":36},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":36},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":36},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[126,107,127,112,128],"super swarm spark","spark","commands",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":36},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,27,153],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":36},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[164,165,166,94,167,168,169,170,116,171,172,173,174,175,176,30,177,178,179,180],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":182,"name":109,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":36},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[109,187,116,188,33,189,87,114,128,190,191,30,192,193,194,195,196,151,85,197],"outline","atomic","sprints","draft","me","write","phased implementation","plan","help","planning","design"]