[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD8YHPH499JMDAC0KVD6QQ":3,"skill-same:01M6XD8YHPH499JMDAC0KVD6QQ":103},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6XD8YHPH499JMDAC0KVD6QQ","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\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\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","my","reviews","account context","problem","deep","read","Bash","design","lambda","iam","audit","issues","debugging","architecture review","architecture","review","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:388eecd762f062c54f24ead8ae0509e0ecc0d47b63e6ca26f62f047382e067de source=skills\u002Faws-specialist\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash\nargument-hint: \u003Caccount context, service, or problem description>\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\".\nname: aws-specialist\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",{"name":5,"description":49,"allowed-tools":50,"argument-hint":51},"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","plugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill aws-specialist",{"tool":65,"command":66},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill aws-specialist",{"tool":68,"command":69},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill aws-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002FSKILL.md",true,[73,79,83,87,91,95,99],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fcompute.md","REFERENCE","参考文档",2468,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002Freferences\u002Fcompute.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fiac-patterns.md",3119,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002Freferences\u002Fiac-patterns.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fiam.md",2945,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002Freferences\u002Fiam.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fnetworking.md",3078,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002Freferences\u002Fnetworking.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fobservability.md",2726,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002Freferences\u002Fobservability.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fserverless.md",2642,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002Freferences\u002Fserverless.md",{"path":100,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fstorage.md",3149,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Faws-specialist\u002Freferences\u002Fstorage.md",[104,135,164,185,204,221],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":115,"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",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[106,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":147,"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",[141,144],{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":145,"categoryName":146,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000037","律师与法务",[38,148,116,43,149,150,34,151,152,153,154,155,156,157,158,159,160,161,162,163],"veracity audit","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","at","invoke","when",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"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",[],[171,172,173,116,43,174,175,38,34,176,33,177,153,178,179,180,181,182,183,184],"spec","validate","validate spec","run","acceptance","work","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":194,"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",[191],{"categoryNo":192,"categoryName":193,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[195,25,196,43,197,40,174,38,198,34,33,199,200,178,32,201,182,202,161,203],"terragrunt","terragrunt specialist","orchestration","analysis","dependency","hooks","dry","remote","hierarchy",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":215,"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",[210,213,214],{"categoryNo":211,"categoryName":212,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":192,"categoryName":193,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[216,217,25,116,35,43,218,42,41,40,38,34,33,152,219,220,32,31,182,161],"terraform","terraform specialist","workflows","test coverage","workspaces",{"skillNo":222,"name":171,"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":230,"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",[226,227],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":228,"categoryName":229,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000032","设计师",[171,35,231,42,232,233,234,235,236,237,238,239,240,241,242,133,243,244,245,246],"component","create","plan","projects","write","interactive","use","document","specification","triggers","opus","technical specification","trade-offs","technical plan","outputs","frontier"]