[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDJCE194860SP97EJA546D":3,"skill-same:01M6XDJCE194860SP97EJA546D":126},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":75,"commitSha":76,"skillDirectory":77,"forksCount":14,"repositoryHtmlUrl":78,"repositoryHomepageUrl":6,"ownerHtmlUrl":79,"ownerBlogUrl":6,"ownerDescription":80,"updatedAt":81,"install":82,"resources":95},"01M6XDJCE194860SP97EJA546D","gcp-specialist",null,"Deep-dive Google Cloud architecture review, debugging, and service design. Use for structured investigations of GCP-specific issues, IAM or cost audits, and multi-service design reviews. Triggers on: \"GCP audit\", \"GCP design review\", \"Workload Identity debug\", \"IAM review GCP\", \"review my GKE\", \"GCP troubleshooting\", \"Cloud Run 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\u002Fgcp-specialist\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"gcp specialist","specialist","gcp","iam","reviews","2025","problem","project","deep","Bash","gke","design","audit","issues","run","debugging","architecture review","architecture","google cloud","review","2026-11-10 10:12:30",false,"---\nid: gcp-specialist\nname: gcp-specialist\ntype: skill\nversion: 1.0.0\ndomain:\n  - infra\nplatform:\n  - gcp\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 Google Cloud architecture review, debugging, and service design. Use for structured investigations of GCP-specific issues, IAM or cost audits, and multi-service design reviews. Triggers on: \"GCP audit\", \"GCP design review\", \"Workload Identity debug\", \"IAM review GCP\", \"review my GKE\", \"GCP troubleshooting\", \"Cloud Run deep-dive\".\nargument-hint: \u003Cproject 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# GCP Specialist\n\nStructured investigation for Google Cloud workloads. Five phases: gather context,\ndiagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — project context, service scope, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. Identify the organization, folders, project(s), and services in scope.\n2. Glob for IaC in the working directory: `**\u002F*.tf`, `**\u002F*.yaml` (Config Connector), `**\u002F*.jinja` (Deployment Manager legacy).\n3. If gcloud CLI access is available:\n   ```bash\n   gcloud config list\n   gcloud projects list\n   gcloud auth list\n   ```\n4. List enabled APIs in the current project:\n   ```bash\n   gcloud services list --enabled --format=\"value(config.name)\"\n   ```\n\n---\n\n## Phase 2: Diagnosis\n\n**Compute \u002F containers:**\n\n```bash\ngcloud compute instances list\ngcloud container clusters list\ngcloud run services list\n```\n\n**IAM \u002F identity:**\n\n```bash\ngcloud projects get-iam-policy \u003Cproject>\ngcloud iam service-accounts list\ngcloud iam workload-identity-pools list --location=global\n```\n\n**Networking:**\n\n```bash\ngcloud compute networks list\ngcloud compute firewall-rules list\ngcloud compute routers list\n```\n\n**Serverless \u002F events:**\n\n```bash\ngcloud functions list\ngcloud pubsub topics list\ngcloud pubsub subscriptions list\n```\n\n**Cost \u002F quotas:**\n\n```bash\ngcloud compute project-info describe --format=\"yaml(quotas)\"\ngcloud logging read 'resource.type=\"gce_instance\"' --limit=20 --format=json\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| GKE pod AuthN fails    | Workload Identity not bound, KSA\u002FGSA annotation mismatch               | `kubectl describe sa` + `gcloud iam service-accounts get-iam-policy`     |\n| Cloud Run cold starts  | min-instances=0, cold container image                                  | `gcloud run services describe` → min-instances, image size               |\n| GCS AccessDenied       | Uniform vs fine-grained mismatch, missing `roles\u002Fstorage.objectViewer` | `gsutil iam get` + project-level IAM                                     |\n| Pub\u002FSub messages stuck | Subscription ack deadline too short, consumer crashed                  | `gcloud pubsub subscriptions describe` + dead-letter config              |\n| BigQuery slow query    | Missing clustering\u002Fpartitioning, full table scan                       | Query plan review, DRY_RUN pricing                                       |\n| VPC connectivity fail  | Firewall default-deny, missing Private Google Access                   | `gcloud compute firewall-rules list` + subnet Private Google Access flag |\n\nCite resource self-link 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: \u003Cself-link or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003Cgcloud output or code snippet>\nFix: \u003Cspecific change, with Terraform\u002FConfig Connector diff>\nTrade-off: \u003Calternative and its downside, if meaningful>\n```\n\n- Order: CRITICAL → WARNING → INFO.\n- For IaC fixes, show the exact Terraform or Config Connector 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 Workload Identity changes: `gcloud iam service-accounts get-iam-policy` and live pod token request.\n3. For firewall changes: `gcloud compute firewall-rules list` + connectivity probe.\n4. For IAM changes: `gcloud projects get-iam-policy --flatten=\"bindings[].members\"` to see effective membership.\n5. Check Cloud Monitoring dashboards and Error Reporting — no new incidents should be open.\n\n---\n\n## Reference Docs\n\nConsult `references\u002F` for decision guides:\n\n| File               | When to use                                              |\n| ------------------ | -------------------------------------------------------- |\n| `compute.md`       | GKE, Cloud Run, GCE selection and sizing                 |\n| `serverless.md`    | Cloud Functions, Pub\u002FSub, Cloud Tasks, Eventarc          |\n| `storage.md`       | GCS, Filestore, BigQuery, Cloud SQL, Spanner             |\n| `networking.md`    | VPC, Cloud Load Balancing, Cloud Armor, Cloud CDN        |\n| `iam.md`           | IAM hierarchy, Workload Identity, Service Accounts       |\n| `observability.md` | Cloud Monitoring, Logging, Trace, Error Reporting        |\n| `iac-patterns.md`  | Terraform, Config Connector, Deployment Manager patterns |\n","# GCP Specialist\n\nStructured investigation for Google Cloud workloads. Five phases: gather context,\ndiagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — project context, service scope, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. Identify the organization, folders, project(s), and services in scope.\n2. Glob for IaC in the working directory: `**\u002F*.tf`, `**\u002F*.yaml` (Config Connector), `**\u002F*.jinja` (Deployment Manager legacy).\n3. If gcloud CLI access is available:\n   ```bash\n   gcloud config list\n   gcloud projects list\n   gcloud auth list\n   ```\n4. List enabled APIs in the current project:\n   ```bash\n   gcloud services list --enabled --format=\"value(config.name)\"\n   ```\n\n---\n\n## Phase 2: Diagnosis\n\n**Compute \u002F containers:**\n\n```bash\ngcloud compute instances list\ngcloud container clusters list\ngcloud run services list\n```\n\n**IAM \u002F identity:**\n\n```bash\ngcloud projects get-iam-policy \u003Cproject>\ngcloud iam service-accounts list\ngcloud iam workload-identity-pools list --location=global\n```\n\n**Networking:**\n\n```bash\ngcloud compute networks list\ngcloud compute firewall-rules list\ngcloud compute routers list\n```\n\n**Serverless \u002F events:**\n\n```bash\ngcloud functions list\ngcloud pubsub topics list\ngcloud pubsub subscriptions list\n```\n\n**Cost \u002F quotas:**\n\n```bash\ngcloud compute project-info describe --format=\"yaml(quotas)\"\ngcloud logging read 'resource.type=\"gce_instance\"' --limit=20 --format=json\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| GKE pod AuthN fails    | Workload Identity not bound, KSA\u002FGSA annotation mismatch               | `kubectl describe sa` + `gcloud iam service-accounts get-iam-policy`     |\n| Cloud Run cold starts  | min-instances=0, cold container image                                  | `gcloud run services describe` → min-instances, image size               |\n| GCS AccessDenied       | Uniform vs fine-grained mismatch, missing `roles\u002Fstorage.objectViewer` | `gsutil iam get` + project-level IAM                                     |\n| Pub\u002FSub messages stuck | Subscription ack deadline too short, consumer crashed                  | `gcloud pubsub subscriptions describe` + dead-letter config              |\n| BigQuery slow query    | Missing clustering\u002Fpartitioning, full table scan                       | Query plan review, DRY_RUN pricing                                       |\n| VPC connectivity fail  | Firewall default-deny, missing Private Google Access                   | `gcloud compute firewall-rules list` + subnet Private Google Access flag |\n\nCite resource self-link 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: \u003Cself-link or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003Cgcloud output or code snippet>\nFix: \u003Cspecific change, with Terraform\u002FConfig Connector diff>\nTrade-off: \u003Calternative and its downside, if meaningful>\n```\n\n- Order: CRITICAL → WARNING → INFO.\n- For IaC fixes, show the exact Terraform or Config Connector 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 Workload Identity changes: `gcloud iam service-accounts get-iam-policy` and live pod token request.\n3. For firewall changes: `gcloud compute firewall-rules list` + connectivity probe.\n4. For IAM changes: `gcloud projects get-iam-policy --flatten=\"bindings[].members\"` to see effective membership.\n5. Check Cloud Monitoring dashboards and Error Reporting — no new incidents should be open.\n\n---\n\n## Reference Docs\n\nConsult `references\u002F` for decision guides:\n\n| File               | When to use                                              |\n| ------------------ | -------------------------------------------------------- |\n| `compute.md`       | GKE, Cloud Run, GCE selection and sizing                 |\n| `serverless.md`    | Cloud Functions, Pub\u002FSub, Cloud Tasks, Eventarc          |\n| `storage.md`       | GCS, Filestore, BigQuery, Cloud SQL, Spanner             |\n| `networking.md`    | VPC, Cloud Load Balancing, Cloud Armor, Cloud CDN        |\n| `iam.md`           | IAM hierarchy, Workload Identity, Service Accounts       |\n| `observability.md` | Cloud Monitoring, Logging, Trace, Error Reporting        |\n| `iac-patterns.md`  | Terraform, Config Connector, Deployment Manager patterns |\n",{"id":5,"name":5,"task":54,"type":55,"model":56,"owner":57,"tools":58,"domain":59,"effort":61,"created":62,"updated":63,"version":64,"dotbabel":65,"maturity":70,"platform":71,"description":72,"allowed-tools":73,"argument-hint":74},[44,48],"skill","opus","@kaiohenricunha","Read, Grep, Glob, Bash",[60],"infra","max",1735689600000,1776384000000,"1.0.0",{"compute":66},{"mode":67,"binding":68,"rationale":69,"requirement":37},"dynamic","consumer","Evidence-based investigation or evaluation must hold several technical constraints at once.","validated",[31],"Deep-dive Google Cloud architecture review, debugging, and service design. Use for structured investigations of GCP-specific issues, IAM or cost audits, and multi-service design reviews. Triggers on: \"GCP audit\", \"GCP design review\", \"Workload Identity debug\", \"IAM review GCP\", \"review my GKE\", \"GCP troubleshooting\", \"Cloud Run deep-dive\".\n","Read Grep Glob Bash","\u003Cproject context, service, or problem description>","main","91c337164997b99943fbcc64e8e362577b67bc81","skills\u002Fgcp-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":83,"prompt":93,"zipAvailable":94},[84,87,90],{"tool":85,"command":86},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill gcp-specialist",{"tool":88,"command":89},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill gcp-specialist",{"tool":91,"command":92},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill gcp-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002FSKILL.md",true,[96,102,106,110,114,118,122],{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fcompute.md","REFERENCE","参考文档",2874,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002Freferences\u002Fcompute.md",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fiac-patterns.md",2956,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002Freferences\u002Fiac-patterns.md",{"path":107,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fiam.md",3231,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002Freferences\u002Fiam.md",{"path":111,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fnetworking.md",3064,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002Freferences\u002Fnetworking.md",{"path":115,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fobservability.md",2818,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002Freferences\u002Fobservability.md",{"path":119,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fserverless.md",3034,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002Freferences\u002Fserverless.md",{"path":123,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fstorage.md",2934,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fgcp-specialist\u002Freferences\u002Fstorage.md",[127,154,182,201,220,237],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":49},"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",[133],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[129,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":166,"publishedAt":49},"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",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":164,"categoryName":165,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[41,167,135,48,168,169,38,170,171,172,173,174,175,176,36,177,178,179,180,181],"veracity audit","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","worker","end","at","invoke","when",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":49},"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",[],[189,190,191,135,48,43,192,41,38,193,194,195,172,61,196,197,198,34,199,200],"spec","validate","validate spec","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":49},"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,30,212,48,213,44,43,41,214,38,194,215,216,61,37,217,34,218,179,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":49},"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,30,135,40,48,234,46,45,44,41,38,194,171,235,236,37,35,34,179],"terraform","terraform specialist","workflows","test coverage","workspaces",{"skillNo":238,"name":189,"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":49},"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":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[189,40,247,46,248,249,250,251,252,253,254,255,256,56,257,152,258,259,260,261],"component","create","plan","projects","write","interactive","use","document","specification","triggers","technical specification","trade-offs","technical plan","outputs","frontier"]