[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7RQVRBK4QPBF9RMM42E9W":3,"skill-same:01M6H7RQVRBK4QPBF9RMM42E9W":70},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6H7RQVRBK4QPBF9RMM42E9W","terraform-expert",null,"Use when implementing terraform 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\u002Fterraform-expert\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36],"terraform","expert","terraform expert","codex","cloud","Production","use","devops","patterns","infra","with","kit","implementing","2026-11-10 10:12:30",false,"---\nname: terraform-expert\ndescription: Use when implementing terraform functionality with production-grade patterns and safeguards.\nmetadata:\n  hermes:\n    tags: [codex-agent, devops-cloud-infra]\n    source: codex-field-kit\u002Fdevops-cloud-infra\n---\n\n# Terraform Expert\n\n## Focus Areas\n\n- Write clean and maintainable Terraform configuration files.\n- Use variables and outputs effectively for reusability.\n- Implement state management best practices.\n- Utilize modules for efficient code reuse.\n- Understand Terraform's resource lifecycle and dependencies.\n- Secure sensitive data using environment variables and secret managers.\n- Optimize performance for large-scale deployments.\n- Utilize Terraform Cloud and remote backends for collaboration.\n- Integrate with CI\u002FCD pipelines for automated provisioning.\n- Keep Terraform versions and providers up to date for security.\n\n## Approach\n\n- Start with defining resources in a main.tf file.\n- Separate configurations into logical files and directories.\n- Use descriptive naming conventions for clarity.\n- Regularly run `terraform fmt` to enforce standard formatting.\n- Plan infrastructure changes using `terraform plan` before applying.\n- Validate configurations with `terraform validate` during development.\n- Use `terraform import` to bring existing infrastructure under Terraform management.\n- Implement drift detection using `terraform refresh`.\n- Automate regular state backups for disaster recovery.\n- Document infrastructure with inline comments and READMEs.\n\n## Quality Checklist\n\n- Configurations adhere to DRY principles, minimizing redundancy.\n- All sensitive data is securely handled and not hardcoded.\n- Terraform version is defined and consistent across environments.\n- Resources are organized into reusable modules with clear interfaces.\n- Output values are used effectively for cross-module communication.\n- Correctly handle provider configurations and authentication.\n- Use lifecycle rules to handle resource creation and deletion order.\n- Maintain detailed and updated documentation within the codebase.\n- Regularly review and refactor Terraform code for improvements.\n- Ensure compliance with organizational policies and standards.\n\n## Output\n\n- Infrastructure provisioned using reliable and maintainable code.\n- State files securely stored with restricted access.\n- Automated CI\u002FCD processes for infrastructure delivery.\n- Clear, organized repository structure for Terraform files.\n- Detailed documentation for each module and resource.\n- Regular infrastructure audits and compliance checks.\n- Effective cost management through efficient resource allocation.\n- Rapid recovery processes for state file corruption scenarios.\n- Consistent development workflows among team members.\n- Automated notifications for policy violations or critical changes.\n\n","# Terraform Expert\n\n## Focus Areas\n\n- Write clean and maintainable Terraform configuration files.\n- Use variables and outputs effectively for reusability.\n- Implement state management best practices.\n- Utilize modules for efficient code reuse.\n- Understand Terraform's resource lifecycle and dependencies.\n- Secure sensitive data using environment variables and secret managers.\n- Optimize performance for large-scale deployments.\n- Utilize Terraform Cloud and remote backends for collaboration.\n- Integrate with CI\u002FCD pipelines for automated provisioning.\n- Keep Terraform versions and providers up to date for security.\n\n## Approach\n\n- Start with defining resources in a main.tf file.\n- Separate configurations into logical files and directories.\n- Use descriptive naming conventions for clarity.\n- Regularly run `terraform fmt` to enforce standard formatting.\n- Plan infrastructure changes using `terraform plan` before applying.\n- Validate configurations with `terraform validate` during development.\n- Use `terraform import` to bring existing infrastructure under Terraform management.\n- Implement drift detection using `terraform refresh`.\n- Automate regular state backups for disaster recovery.\n- Document infrastructure with inline comments and READMEs.\n\n## Quality Checklist\n\n- Configurations adhere to DRY principles, minimizing redundancy.\n- All sensitive data is securely handled and not hardcoded.\n- Terraform version is defined and consistent across environments.\n- Resources are organized into reusable modules with clear interfaces.\n- Output values are used effectively for cross-module communication.\n- Correctly handle provider configurations and authentication.\n- Use lifecycle rules to handle resource creation and deletion order.\n- Maintain detailed and updated documentation within the codebase.\n- Regularly review and refactor Terraform code for improvements.\n- Ensure compliance with organizational policies and standards.\n\n## Output\n\n- Infrastructure provisioned using reliable and maintainable code.\n- State files securely stored with restricted access.\n- Automated CI\u002FCD processes for infrastructure delivery.\n- Clear, organized repository structure for Terraform files.\n- Detailed documentation for each module and resource.\n- Regular infrastructure audits and compliance checks.\n- Effective cost management through efficient resource allocation.\n- Rapid recovery processes for state file corruption scenarios.\n- Consistent development workflows among team members.\n- Automated notifications for policy violations or critical changes.\n\n",{"name":5,"metadata":42,"description":7},{"hermes":43},{"tags":44,"source":47},[45,46],"codex-agent","devops-cloud-infra","codex-field-kit\u002Fdevops-cloud-infra","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fterraform-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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill terraform-expert",{"tool":62,"command":63},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill terraform-expert",{"tool":65,"command":66},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill terraform-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fterraform-expert\u002FSKILL.md",true,[],[71,101,120,130,155,182],{"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":80,"publishedAt":37},"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",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":37},"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",[],[108,109,110,111,112,113,114,115,116,117,118,119],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":37},"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",[],[127,108,128,113,129],"super swarm spark","spark","commands",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":37},"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",[],[137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,27,154],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":37},"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",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[165,166,167,95,168,169,170,171,117,172,173,174,175,176,177,30,178,179,180,181],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":183,"name":110,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":37},"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",[],[110,188,117,189,34,190,88,115,129,191,192,30,193,194,195,196,197,152,86,198],"outline","atomic","sprints","draft","me","write","phased implementation","plan","help","planning","design"]