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