[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEH095F5C7YCQZ1RPSDQ7S":3,"skill-same:01M6AEH095F5C7YCQZ1RPSDQ7S":138},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6AEH095F5C7YCQZ1RPSDQ7S","devops-iac-engineer",null,"Implements infrastructure as code using Terraform, Kubernetes, and cloud platforms. Designs scalable architectures, CI\u002FCD pipelines, and observability solutions. Provides security-first DevOps practices and site reliability engineering guidance.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\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,37,38,39,40,41,42,43,44,45,46],"devops iac","engineer","devops iac engineer","devops","iac","solutions","kubernetes","CI\u002FCD","reliability engineering","Scalable","architectures","as","site reliability","reliability","engineering","ci","cloud","observability","infrastructure as code","terraform","code","infrastructure","security","2026-11-10 10:12:30",false,"---\nname: devops-iac-engineer\ndescription: Implements infrastructure as code using Terraform, Kubernetes, and cloud platforms. Designs scalable architectures, CI\u002FCD pipelines, and observability solutions. Provides security-first DevOps practices and site reliability engineering guidance.\n---\n\n# DevOps IaC Engineer\n\nThis Skill helps DevOps teams design, implement, and maintain cloud infrastructure using Infrastructure as Code principles. Use this when building cloud architectures, deploying containerized applications, setting up CI\u002FCD pipelines, or implementing observability and security practices.\n\n## Quick Navigation\n\n- **Terraform & IaC**: See [terraform.md](reference\u002Fterraform.md) for Terraform best practices and patterns\n- **Kubernetes & Containers**: See [kubernetes.md](reference\u002Fkubernetes.md) for container orchestration\n- **Cloud Platforms**: See [cloud_platforms.md](reference\u002Fcloud_platforms.md) for AWS, Azure, GCP guidance\n- **CI\u002FCD Pipelines**: See [cicd.md](reference\u002Fcicd.md) for pipeline design and GitOps\n- **Observability**: See [observability.md](reference\u002Fobservability.md) for monitoring and logging\n- **Security**: See [security.md](reference\u002Fsecurity.md) for DevSecOps practices\n- **Templates & Tools**: See [templates.md](reference\u002Ftemplates.md) for ready-to-use templates\n\n## Core Principles\n\n### Key DevOps Terminology (Consistent Throughout)\n- **Infrastructure as Code (IaC)**: Managing infrastructure through declarative code files\n- **GitOps**: Using Git as the single source of truth for infrastructure and applications\n- **Immutable Infrastructure**: Infrastructure components that are replaced rather than modified\n- **Service Mesh**: Infrastructure layer for service-to-service communication\n- **Observability**: Ability to understand system state from external outputs (logs, metrics, traces)\n- **SLI\u002FSLO\u002FSLA**: Service Level Indicators\u002FObjectives\u002FAgreements for reliability\n- **RTO\u002FRPO**: Recovery Time Objective\u002FRecovery Point Objective for disaster recovery\n\n### Workflow: Infrastructure Implementation\n\nWhen implementing infrastructure, follow this structured approach:\n\n1. **Understand Requirements**\n   - What is the business need? (new application, migration, scaling, compliance)\n   - What are the scale requirements? (traffic, data, geographic distribution)\n   - What are the constraints? (budget, timeline, regulatory)\n   - What are the dependencies? (existing systems, data sources)\n\n2. **Design Architecture**\n   - Choose appropriate cloud platform(s) and services\n   - Design for high availability and fault tolerance\n   - Plan network topology and security boundaries\n   - Identify data flows and storage requirements\n   - Document architecture with diagrams\n\n3. **Select IaC Tools**\n   - Terraform for multi-cloud infrastructure provisioning\n   - Kubernetes manifests\u002FHelm for container orchestration\n   - CI\u002FCD tool selection based on team and requirements\n   - Configuration management tools if needed\n\n4. **Implement Infrastructure**\n   - Create modular, reusable IaC code\n   - Follow security best practices (see [security.md](reference\u002Fsecurity.md))\n   - Implement proper state management and versioning\n   - Use consistent naming and tagging conventions\n   - Document code and create README files\n\n5. **Set Up Observability**\n   - Define SLIs and SLOs for critical services\n   - Implement logging, metrics, and tracing\n   - Create dashboards and alerts\n   - Set up log aggregation and analysis\n   - Plan on-call rotation and runbooks\n\n6. **Implement CI\u002FCD**\n   - Design deployment pipeline stages\n   - Implement automated testing (unit, integration, e2e)\n   - Set up GitOps workflows\n   - Configure deployment strategies (blue\u002Fgreen, canary)\n   - Implement rollback procedures\n\n7. **Test & Validate**\n   - Run infrastructure tests (security, compliance, cost)\n   - Perform disaster recovery drills\n   - Load testing and performance validation\n   - Security scanning and penetration testing\n   - Document test results and improvements\n\n8. **Deploy & Monitor**\n   - Execute phased rollout\n   - Monitor metrics and logs closely\n   - Validate against SLOs\n   - Document runbooks and troubleshooting guides\n   - Conduct post-deployment review\n\n### Decision Framework: Tool Selection\n\n**Multi-Cloud Requirements** → Terraform or Pulumi\n**AWS-Only** → Terraform, AWS CDK, or CloudFormation\n**Container Orchestration** → Kubernetes (EKS, GKE, AKS)\n**Simple Container Deployment** → ECS, Cloud Run, or App Service\n**Configuration Management** → Ansible or cloud-native solutions\n**GitOps Workflows** → ArgoCD or Flux\n**CI\u002FCD Pipelines** → GitHub Actions, GitLab CI, or Jenkins\n\n## Common Challenges & Solutions\n\n**Problem**: Infrastructure drift between code and reality\n**Solution**: Implement automated drift detection, use terraform plan in CI\u002FCD, enable read-only production access, maintain state file integrity\n\n**Problem**: Secrets management and credential exposure\n**Solution**: Use cloud-native secret managers (AWS Secrets Manager, HashiCorp Vault), implement SOPS for encrypted secrets in Git, use IRSA\u002Fworkload identity\n\n**Problem**: High cloud costs and unexpected bills\n**Solution**: Implement tagging strategy, use cost allocation tags, set up budget alerts, right-size resources, use spot instances, implement auto-scaling\n\n**Problem**: Complex Kubernetes configurations\n**Solution**: Use Helm charts for templating, implement Kustomize for environment-specific configs, follow GitOps patterns, use operators for complex workloads\n\n## Collaboration Tips\n\n- **With Development Teams**: Provide self-service platforms, document APIs, share infrastructure as reusable modules\n- **With Security Teams**: Implement policy as code, automate compliance checks, provide audit trails\n- **With SRE Teams**: Define SLIs\u002FSLOs together, share on-call responsibilities, collaborate on incident response\n- **With Finance Teams**: Provide cost visibility, forecast expenses, implement chargeback models\n\n---\n\n## Next Steps\n\n1. Start with [terraform.md](reference\u002Fterraform.md) if you're implementing infrastructure as code\n2. Use [kubernetes.md](reference\u002Fkubernetes.md) for container orchestration\n3. Reference [templates.md](reference\u002Ftemplates.md) for ready-to-use configurations\n4. Check [observability.md](reference\u002Fobservability.md) to set up monitoring\n\n**Note**: Always verify current infrastructure state, security requirements, and compliance needs before implementing changes. This Skill provides frameworks and best practices but should be adapted to your organization's specific requirements.\n","# DevOps IaC Engineer\n\nThis Skill helps DevOps teams design, implement, and maintain cloud infrastructure using Infrastructure as Code principles. Use this when building cloud architectures, deploying containerized applications, setting up CI\u002FCD pipelines, or implementing observability and security practices.\n\n## Quick Navigation\n\n- **Terraform & IaC**: See [terraform.md](reference\u002Fterraform.md) for Terraform best practices and patterns\n- **Kubernetes & Containers**: See [kubernetes.md](reference\u002Fkubernetes.md) for container orchestration\n- **Cloud Platforms**: See [cloud_platforms.md](reference\u002Fcloud_platforms.md) for AWS, Azure, GCP guidance\n- **CI\u002FCD Pipelines**: See [cicd.md](reference\u002Fcicd.md) for pipeline design and GitOps\n- **Observability**: See [observability.md](reference\u002Fobservability.md) for monitoring and logging\n- **Security**: See [security.md](reference\u002Fsecurity.md) for DevSecOps practices\n- **Templates & Tools**: See [templates.md](reference\u002Ftemplates.md) for ready-to-use templates\n\n## Core Principles\n\n### Key DevOps Terminology (Consistent Throughout)\n- **Infrastructure as Code (IaC)**: Managing infrastructure through declarative code files\n- **GitOps**: Using Git as the single source of truth for infrastructure and applications\n- **Immutable Infrastructure**: Infrastructure components that are replaced rather than modified\n- **Service Mesh**: Infrastructure layer for service-to-service communication\n- **Observability**: Ability to understand system state from external outputs (logs, metrics, traces)\n- **SLI\u002FSLO\u002FSLA**: Service Level Indicators\u002FObjectives\u002FAgreements for reliability\n- **RTO\u002FRPO**: Recovery Time Objective\u002FRecovery Point Objective for disaster recovery\n\n### Workflow: Infrastructure Implementation\n\nWhen implementing infrastructure, follow this structured approach:\n\n1. **Understand Requirements**\n   - What is the business need? (new application, migration, scaling, compliance)\n   - What are the scale requirements? (traffic, data, geographic distribution)\n   - What are the constraints? (budget, timeline, regulatory)\n   - What are the dependencies? (existing systems, data sources)\n\n2. **Design Architecture**\n   - Choose appropriate cloud platform(s) and services\n   - Design for high availability and fault tolerance\n   - Plan network topology and security boundaries\n   - Identify data flows and storage requirements\n   - Document architecture with diagrams\n\n3. **Select IaC Tools**\n   - Terraform for multi-cloud infrastructure provisioning\n   - Kubernetes manifests\u002FHelm for container orchestration\n   - CI\u002FCD tool selection based on team and requirements\n   - Configuration management tools if needed\n\n4. **Implement Infrastructure**\n   - Create modular, reusable IaC code\n   - Follow security best practices (see [security.md](reference\u002Fsecurity.md))\n   - Implement proper state management and versioning\n   - Use consistent naming and tagging conventions\n   - Document code and create README files\n\n5. **Set Up Observability**\n   - Define SLIs and SLOs for critical services\n   - Implement logging, metrics, and tracing\n   - Create dashboards and alerts\n   - Set up log aggregation and analysis\n   - Plan on-call rotation and runbooks\n\n6. **Implement CI\u002FCD**\n   - Design deployment pipeline stages\n   - Implement automated testing (unit, integration, e2e)\n   - Set up GitOps workflows\n   - Configure deployment strategies (blue\u002Fgreen, canary)\n   - Implement rollback procedures\n\n7. **Test & Validate**\n   - Run infrastructure tests (security, compliance, cost)\n   - Perform disaster recovery drills\n   - Load testing and performance validation\n   - Security scanning and penetration testing\n   - Document test results and improvements\n\n8. **Deploy & Monitor**\n   - Execute phased rollout\n   - Monitor metrics and logs closely\n   - Validate against SLOs\n   - Document runbooks and troubleshooting guides\n   - Conduct post-deployment review\n\n### Decision Framework: Tool Selection\n\n**Multi-Cloud Requirements** → Terraform or Pulumi\n**AWS-Only** → Terraform, AWS CDK, or CloudFormation\n**Container Orchestration** → Kubernetes (EKS, GKE, AKS)\n**Simple Container Deployment** → ECS, Cloud Run, or App Service\n**Configuration Management** → Ansible or cloud-native solutions\n**GitOps Workflows** → ArgoCD or Flux\n**CI\u002FCD Pipelines** → GitHub Actions, GitLab CI, or Jenkins\n\n## Common Challenges & Solutions\n\n**Problem**: Infrastructure drift between code and reality\n**Solution**: Implement automated drift detection, use terraform plan in CI\u002FCD, enable read-only production access, maintain state file integrity\n\n**Problem**: Secrets management and credential exposure\n**Solution**: Use cloud-native secret managers (AWS Secrets Manager, HashiCorp Vault), implement SOPS for encrypted secrets in Git, use IRSA\u002Fworkload identity\n\n**Problem**: High cloud costs and unexpected bills\n**Solution**: Implement tagging strategy, use cost allocation tags, set up budget alerts, right-size resources, use spot instances, implement auto-scaling\n\n**Problem**: Complex Kubernetes configurations\n**Solution**: Use Helm charts for templating, implement Kustomize for environment-specific configs, follow GitOps patterns, use operators for complex workloads\n\n## Collaboration Tips\n\n- **With Development Teams**: Provide self-service platforms, document APIs, share infrastructure as reusable modules\n- **With Security Teams**: Implement policy as code, automate compliance checks, provide audit trails\n- **With SRE Teams**: Define SLIs\u002FSLOs together, share on-call responsibilities, collaborate on incident response\n- **With Finance Teams**: Provide cost visibility, forecast expenses, implement chargeback models\n\n---\n\n## Next Steps\n\n1. Start with [terraform.md](reference\u002Fterraform.md) if you're implementing infrastructure as code\n2. Use [kubernetes.md](reference\u002Fkubernetes.md) for container orchestration\n3. Reference [templates.md](reference\u002Ftemplates.md) for ready-to-use configurations\n4. Check [observability.md](reference\u002Fobservability.md) to set up monitoring\n\n**Note**: Always verify current infrastructure state, security requirements, and compliance needs before implementing changes. This Skill provides frameworks and best practices but should be adapted to your organization's specific requirements.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add davila7\u002Fclaude-code-templates --skill devops-iac-engineer",{"tool":68,"command":69},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill devops-iac-engineer",{"tool":71,"command":72},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill devops-iac-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002FSKILL.md",true,[76,82,86,90,96,100,104,108,112,116,120,124,128,132],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"DIRECTORY_STRUCTURE.md","REFERENCE","参考文档",8574,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002FDIRECTORY_STRUCTURE.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"examples\u002Fkubernetes\u002Fcomplete-app.yaml",4323,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Fexamples\u002Fkubernetes\u002Fcomplete-app.yaml",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"examples\u002Fpipelines\u002Fgithub-actions.yml",4512,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Fexamples\u002Fpipelines\u002Fgithub-actions.yml",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"examples\u002Fterraform\u002Fmain.tf","OTHER","其他",2574,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Fexamples\u002Fterraform\u002Fmain.tf",{"path":97,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":98,"sourceHtmlUrl":99},"IMPLEMENTATION_GUIDE.md",11871,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002FIMPLEMENTATION_GUIDE.md",{"path":101,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":102,"sourceHtmlUrl":103},"README.md",9110,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002FREADME.md",{"path":105,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":106,"sourceHtmlUrl":107},"reference\u002Fcicd.md",15471,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Freference\u002Fcicd.md",{"path":109,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":110,"sourceHtmlUrl":111},"reference\u002Fcloud_platforms.md",16164,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Freference\u002Fcloud_platforms.md",{"path":113,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":114,"sourceHtmlUrl":115},"reference\u002Fkubernetes.md",20424,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Freference\u002Fkubernetes.md",{"path":117,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":118,"sourceHtmlUrl":119},"reference\u002Fobservability.md",14424,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Freference\u002Fobservability.md",{"path":121,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":122,"sourceHtmlUrl":123},"reference\u002Fsecurity.md",14095,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Freference\u002Fsecurity.md",{"path":125,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":126,"sourceHtmlUrl":127},"reference\u002Ftemplates.md",18509,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Freference\u002Ftemplates.md",{"path":129,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":130,"sourceHtmlUrl":131},"reference\u002Fterraform.md",16550,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Freference\u002Fterraform.md",{"path":133,"resourceType":134,"resourceTypeDesc":135,"sizeBytes":136,"sourceHtmlUrl":137},"scripts\u002Fdevops_utils.py","SCRIPT","脚本",14984,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fdevops-iac-engineer\u002Fscripts\u002Fdevops_utils.py",[139,169,195,228,263,287],{"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":148,"publishedAt":47},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":47},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[175],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[177,178,179,180,181,182,183,184,185,186,187,158,44,188,189,190,191,192,193,194],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":210,"publishedAt":47},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[201,204,205],{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":206,"categoryName":207,"taxonomyType":208,"taxonomyTypeDesc":209},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[211,212,213,214,215,216,217,154,218,219,220,221,222,223,224,157,225,226,158,227],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":232,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":239,"publishedAt":47},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[236],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,154,262],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":264,"name":265,"nameZh":6,"description":266,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":232,"licenseFileUrl":267,"sourceHtmlUrl":268,"categories":269,"keywords":274,"publishedAt":47},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[270,273],{"categoryNo":271,"categoryName":272,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},[275,276,277,278,279,241,280,250,251,281,282,283,284,154,285,160,286],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":288,"name":289,"nameZh":6,"description":290,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":232,"licenseFileUrl":291,"sourceHtmlUrl":292,"categories":293,"keywords":301,"publishedAt":47},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[294,297,298],{"categoryNo":295,"categoryName":296,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":299,"categoryName":300,"taxonomyType":208,"taxonomyTypeDesc":209},"01JBSEEDCAT000000000000036","内容创作者",[302,303,304,305,306,307,308,309,243,310,253,44,311,312,313,314,315,223,316,158,317,318,319,320,321,166,322],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]