[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDG5SD4G3ZM5X3HZ2NXF7W":3,"skill-same:01M6XDG5SD4G3ZM5X3HZ2NXF7W":121},{"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":70,"commitSha":71,"skillDirectory":72,"forksCount":14,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6XDG5SD4G3ZM5X3HZ2NXF7W","aws-specialist",null,"Deep-dive AWS architecture review, debugging, and service design. Use for structured investigations of AWS-specific issues, cost or IAM audits, and multi-service design reviews. Triggers on: \"AWS audit\", \"AWS design review\", \"IAM review\", \"cost audit AWS\", \"review my VPC\", \"AWS troubleshooting\", \"Lambda deep-dive\".","kaiohenricunha\u002Fdotbabel","kaiohenricunha","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69804490?v=4","01M6XCZD37W0KPCDGEA40Y610V","Kaio Cunha","01M6XCZD7SX714D114H3ZPNW09",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\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],"aws specialist","specialist","aws","vpc","at","reviews","2025","account context","problem","deep","Bash","design","lambda","iam","audit","issues","debugging","architecture review","architecture","review","2026-11-10 10:12:30",false,"---\nid: aws-specialist\nname: aws-specialist\ntype: skill\nversion: 1.0.0\ndomain:\n  - infra\nplatform:\n  - aws\ntask:\n  - debugging\n  - review\nmaturity: validated\nowner: \"@kaiohenricunha\"\ncreated: 2025-01-01T00:00:00.000Z\nupdated: 2026-04-17T00:00:00.000Z\ndescription: |\n  Deep-dive AWS architecture review, debugging, and service design. Use for structured investigations of AWS-specific issues, cost or IAM audits, and multi-service design reviews. Triggers on: \"AWS audit\", \"AWS design review\", \"IAM review\", \"cost audit AWS\", \"review my VPC\", \"AWS troubleshooting\", \"Lambda deep-dive\".\nargument-hint: \u003Caccount context, service, or problem description>\ntools: Read, Grep, Glob, Bash\nallowed-tools: Read Grep Glob Bash\neffort: max\nmodel: opus\ndotbabel:\n  compute:\n    mode: dynamic\n    requirement: deep\n    binding: consumer\n    rationale: Evidence-based investigation or evaluation must hold several technical constraints at once.\n---\n\n# AWS Specialist\n\nStructured investigation for AWS workloads. Five phases: gather context,\ndiagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — account context, service scope, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. Identify the account(s), region(s), and services in scope.\n2. Glob for IaC in the working directory: `**\u002F*.tf`, `**\u002F*.yaml` (SAM\u002FCloudFormation), `**\u002Fcdk.json`, `**\u002Ftemplate.yaml`.\n3. If AWS CLI access is available:\n   ```bash\n   aws sts get-caller-identity\n   aws configure list\n   ```\n4. Note the service scope (e.g. \"EKS cluster + VPC + IAM\" vs \"Lambda + API Gateway + DynamoDB\"). Scope commands to the relevant resource types.\n\n---\n\n## Phase 2: Diagnosis\n\n**Compute \u002F containers:**\n\n```bash\naws ec2 describe-instances --filters Name=instance-state-name,Values=running\naws ecs list-services --cluster \u003Cname>\naws eks describe-cluster --name \u003Cname>\n```\n\n**IAM \u002F identity:**\n\n```bash\naws iam list-policies --scope Local\naws iam get-role --role-name \u003Crole>\naws iam simulate-principal-policy --policy-source-arn \u003Carn> --action-names \u003Caction>\n```\n\n**Networking:**\n\n```bash\naws ec2 describe-vpcs\naws ec2 describe-route-tables\naws ec2 describe-security-groups\n```\n\n**Serverless \u002F events:**\n\n```bash\naws lambda list-functions\naws lambda get-function-configuration --function-name \u003Cname>\naws apigateway get-rest-apis\n```\n\n**Cost \u002F quotas:**\n\n```bash\naws service-quotas list-service-quotas --service-code ec2\naws ce get-cost-and-usage --time-period Start=\u003C>,End=\u003C> --granularity DAILY --metrics UnblendedCost\n```\n\n---\n\n## Phase 3: Design \u002F Root-Cause Analysis\n\nMap symptoms to causes:\n\n| Symptom                 | Common Causes                                          | Check                                             |\n| ----------------------- | ------------------------------------------------------ | ------------------------------------------------- |\n| 5xx from ALB            | Unhealthy targets, timeout mismatch, HTTP\u002FS misrouting | Target group health, ALB access logs              |\n| Lambda throttled        | Reserved concurrency, account-wide limit               | `aws lambda get-function-concurrency`             |\n| EKS pod IAM fails       | Missing IRSA, ServiceAccount annotation                | OIDC provider + trust policy on role              |\n| S3 AccessDenied         | Bucket policy, SCP, VPC endpoint policy                | Use `aws s3api get-bucket-policy` + IAM simulator |\n| RDS CPU spike           | Missing indexes, connection storm, runaway query       | Performance Insights, slow query log              |\n| CloudFront caching miss | Incorrect cache key, missing `Cache-Control`           | Check behaviors + origin headers                  |\n\nCite resource ARN or `file:line` for every finding.\n\n---\n\n## Phase 4: Recommendations\n\nOutput findings in priority order:\n\n```\n[CRITICAL] \u003Ctitle>\nResource: \u003CARN or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003CCLI output or code snippet>\nFix: \u003Cspecific change, with IaC diff if applicable>\nTrade-off: \u003Calternative and its downside, if meaningful>\n```\n\n- Order: CRITICAL → WARNING → INFO.\n- For IaC fixes, show the exact Terraform\u002FCDK\u002FCloudFormation diff.\n- Reference relevant docs in `references\u002F` where applicable.\n\n---\n\n## Phase 5: Verification\n\nAfter fixes are applied:\n\n1. Re-run the diagnostic command that surfaced the issue.\n2. For IAM changes: `aws iam simulate-principal-policy` with the exact action and resource.\n3. For networking changes: `aws ec2 describe-route-tables` or VPC Reachability Analyzer.\n4. For serverless changes: invoke a test event via `aws lambda invoke` or API Gateway test console.\n5. Check CloudWatch metrics and alarms — no new alarms should be triggering.\n\n---\n\n## Reference Docs\n\nConsult `references\u002F` for decision guides:\n\n| File               | When to use                                    |\n| ------------------ | ---------------------------------------------- |\n| `compute.md`       | EC2, ECS, EKS selection and sizing             |\n| `serverless.md`    | Lambda, API Gateway, EventBridge, SQS, SNS     |\n| `storage.md`       | S3, EBS, EFS, RDS, DynamoDB                    |\n| `networking.md`    | VPC, ALB\u002FNLB, Route53, CloudFront, PrivateLink |\n| `iam.md`           | Policies, roles, SCPs, permission boundaries   |\n| `observability.md` | CloudWatch, X-Ray, Container Insights          |\n| `iac-patterns.md`  | CloudFormation, CDK, SAM patterns              |\n","# AWS Specialist\n\nStructured investigation for AWS workloads. Five phases: gather context,\ndiagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — account context, service scope, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. Identify the account(s), region(s), and services in scope.\n2. Glob for IaC in the working directory: `**\u002F*.tf`, `**\u002F*.yaml` (SAM\u002FCloudFormation), `**\u002Fcdk.json`, `**\u002Ftemplate.yaml`.\n3. If AWS CLI access is available:\n   ```bash\n   aws sts get-caller-identity\n   aws configure list\n   ```\n4. Note the service scope (e.g. \"EKS cluster + VPC + IAM\" vs \"Lambda + API Gateway + DynamoDB\"). Scope commands to the relevant resource types.\n\n---\n\n## Phase 2: Diagnosis\n\n**Compute \u002F containers:**\n\n```bash\naws ec2 describe-instances --filters Name=instance-state-name,Values=running\naws ecs list-services --cluster \u003Cname>\naws eks describe-cluster --name \u003Cname>\n```\n\n**IAM \u002F identity:**\n\n```bash\naws iam list-policies --scope Local\naws iam get-role --role-name \u003Crole>\naws iam simulate-principal-policy --policy-source-arn \u003Carn> --action-names \u003Caction>\n```\n\n**Networking:**\n\n```bash\naws ec2 describe-vpcs\naws ec2 describe-route-tables\naws ec2 describe-security-groups\n```\n\n**Serverless \u002F events:**\n\n```bash\naws lambda list-functions\naws lambda get-function-configuration --function-name \u003Cname>\naws apigateway get-rest-apis\n```\n\n**Cost \u002F quotas:**\n\n```bash\naws service-quotas list-service-quotas --service-code ec2\naws ce get-cost-and-usage --time-period Start=\u003C>,End=\u003C> --granularity DAILY --metrics UnblendedCost\n```\n\n---\n\n## Phase 3: Design \u002F Root-Cause Analysis\n\nMap symptoms to causes:\n\n| Symptom                 | Common Causes                                          | Check                                             |\n| ----------------------- | ------------------------------------------------------ | ------------------------------------------------- |\n| 5xx from ALB            | Unhealthy targets, timeout mismatch, HTTP\u002FS misrouting | Target group health, ALB access logs              |\n| Lambda throttled        | Reserved concurrency, account-wide limit               | `aws lambda get-function-concurrency`             |\n| EKS pod IAM fails       | Missing IRSA, ServiceAccount annotation                | OIDC provider + trust policy on role              |\n| S3 AccessDenied         | Bucket policy, SCP, VPC endpoint policy                | Use `aws s3api get-bucket-policy` + IAM simulator |\n| RDS CPU spike           | Missing indexes, connection storm, runaway query       | Performance Insights, slow query log              |\n| CloudFront caching miss | Incorrect cache key, missing `Cache-Control`           | Check behaviors + origin headers                  |\n\nCite resource ARN or `file:line` for every finding.\n\n---\n\n## Phase 4: Recommendations\n\nOutput findings in priority order:\n\n```\n[CRITICAL] \u003Ctitle>\nResource: \u003CARN or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003CCLI output or code snippet>\nFix: \u003Cspecific change, with IaC diff if applicable>\nTrade-off: \u003Calternative and its downside, if meaningful>\n```\n\n- Order: CRITICAL → WARNING → INFO.\n- For IaC fixes, show the exact Terraform\u002FCDK\u002FCloudFormation diff.\n- Reference relevant docs in `references\u002F` where applicable.\n\n---\n\n## Phase 5: Verification\n\nAfter fixes are applied:\n\n1. Re-run the diagnostic command that surfaced the issue.\n2. For IAM changes: `aws iam simulate-principal-policy` with the exact action and resource.\n3. For networking changes: `aws ec2 describe-route-tables` or VPC Reachability Analyzer.\n4. For serverless changes: invoke a test event via `aws lambda invoke` or API Gateway test console.\n5. Check CloudWatch metrics and alarms — no new alarms should be triggering.\n\n---\n\n## Reference Docs\n\nConsult `references\u002F` for decision guides:\n\n| File               | When to use                                    |\n| ------------------ | ---------------------------------------------- |\n| `compute.md`       | EC2, ECS, EKS selection and sizing             |\n| `serverless.md`    | Lambda, API Gateway, EventBridge, SQS, SNS     |\n| `storage.md`       | S3, EBS, EFS, RDS, DynamoDB                    |\n| `networking.md`    | VPC, ALB\u002FNLB, Route53, CloudFront, PrivateLink |\n| `iam.md`           | Policies, roles, SCPs, permission boundaries   |\n| `observability.md` | CloudWatch, X-Ray, Container Insights          |\n| `iac-patterns.md`  | CloudFormation, CDK, SAM patterns              |\n",{"id":5,"name":5,"task":49,"type":50,"model":51,"owner":52,"tools":53,"domain":54,"effort":56,"created":57,"updated":58,"version":59,"dotbabel":60,"maturity":65,"platform":66,"description":67,"allowed-tools":68,"argument-hint":69},[40,43],"skill","opus","@kaiohenricunha","Read, Grep, Glob, Bash",[55],"infra","max",1735689600000,1776384000000,"1.0.0",{"compute":61},{"mode":62,"binding":63,"rationale":64,"requirement":33},"dynamic","consumer","Evidence-based investigation or evaluation must hold several technical constraints at once.","validated",[26],"Deep-dive AWS architecture review, debugging, and service design. Use for structured investigations of AWS-specific issues, cost or IAM audits, and multi-service design reviews. Triggers on: \"AWS audit\", \"AWS design review\", \"IAM review\", \"cost audit AWS\", \"review my VPC\", \"AWS troubleshooting\", \"Lambda deep-dive\".\n","Read Grep Glob Bash","\u003Caccount context, service, or problem description>","main","91c337164997b99943fbcc64e8e362577b67bc81","skills\u002Faws-specialist","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha","I'm a Platform\u002FInfra engineer who happens to work in cybersec and write Go code.","2026-10-26 14:12:51",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill aws-specialist",{"tool":83,"command":84},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill aws-specialist",{"tool":86,"command":87},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill aws-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002FSKILL.md",true,[91,97,101,105,109,113,117],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fcompute.md","REFERENCE","参考文档",2468,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002Freferences\u002Fcompute.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fiac-patterns.md",3119,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002Freferences\u002Fiac-patterns.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fiam.md",2945,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002Freferences\u002Fiam.md",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fnetworking.md",3078,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002Freferences\u002Fnetworking.md",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fobservability.md",2726,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002Freferences\u002Fobservability.md",{"path":114,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fserverless.md",2642,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002Freferences\u002Fserverless.md",{"path":118,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fstorage.md",3149,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Faws-specialist\u002Freferences\u002Fstorage.md",[122,153,181,201,220,237],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":133,"publishedAt":44},"01M6XDQ7QMASPFZ355MYKCD06T","yolo","Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fyolo\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[124,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":165,"publishedAt":44},"01M6XDQ1N21VE4KH98JWGZ7GN9","veracity-audit","Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace \u003Clabel> (single source end-to-end). Invoke when: \"audit pipeline\", \"veracity check\", \"scoring math correct?\", \"check gates\", \"trace source\", \"verify quality gates\", \"formula correct?\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fveracity-audit\u002FSKILL.md",[159,162],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":163,"categoryName":164,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000037","律师与法务",[38,166,134,43,167,168,34,169,170,171,172,173,174,175,176,177,178,28,179,180],"veracity audit","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","invoke","when",{"skillNo":182,"name":183,"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":44},"01M6XDPVDKBR376C06CEK9BC5S","validate-spec","Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs\u002Faudits\u002F. Use whenever the user asks to \"validate a spec\", \"audit a spec\", \"check if spec is implemented\", \"verify the spec is done\", \"is this spec really done\", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-spec\u002FSKILL.md",[],[188,189,190,134,43,191,192,38,34,193,194,195,171,56,196,197,198,30,199,200],"spec","validate","validate spec","run","acceptance","work","read","never","done","arch","line","spec-driven","closure",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":44},"01M6XDPMMECH82RAW553Y94HDS","terragrunt-specialist","Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: \"Terragrunt audit\", \"run-all review\", \"dependency block\", \"DRY pattern review\", \"env hierarchy audit\", \"mock_outputs\", \"terragrunt hooks\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterragrunt-specialist\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[211,25,212,43,213,40,191,38,214,34,194,215,216,56,33,217,30,218,28,219],"terragrunt","terragrunt specialist","orchestration","analysis","dependency","hooks","dry","remote","hierarchy",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":231,"publishedAt":44},"01M6XDPFJS2HGSE13RXF1HV8S7","terraform-specialist","Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: \"Terraform audit\", \"module review\", \"state management\", \"Terraform import\", \"workspace design\", \"provider config review\", \"Terraform testing\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-specialist\u002FSKILL.md",[226,229,230],{"categoryNo":227,"categoryName":228,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[232,233,25,134,35,43,234,42,41,40,38,34,194,170,235,236,33,32,30,28],"terraform","terraform specialist","workflows","test coverage","workspaces",{"skillNo":238,"name":188,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":246,"publishedAt":44},"01M6XDP7V6H8WYPSXVEKYE6HJ6","Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on \"let's spec this out\", \"create a spec\", \"design doc\", \"write a technical plan\", \"plan the architecture\". Works for greenfield and brownfield projects. Outputs to docs\u002Fspecs\u002F.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fspec\u002FSKILL.md",[242,243],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":244,"categoryName":245,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000032","设计师",[188,35,247,42,248,249,250,251,252,253,254,255,256,51,257,151,258,259,260,261],"component","create","plan","projects","write","interactive","use","document","specification","triggers","technical specification","trade-offs","technical plan","outputs","frontier"]