[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783VZQPP8Z0DMPTEWYNPEEW":3,"skill-same:01M783VZQPP8Z0DMPTEWYNPEEW":72},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M783VZQPP8Z0DMPTEWYNPEEW","senior-devops",null,"Comprehensive DevOps skill for CI\u002FCD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.","motivatedc-creator\u002FSaafy","motivatedc-creator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250662783?v=4","01M782H2D8C7XJGXMJC3YHQAWK","Happy Haris","01M782H2ERMBYEM1NSPPPC06S0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"senior-devops\"\ndescription: Comprehensive DevOps skill for CI\u002FCD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.\n---\n\n# Senior Devops\n\nComplete toolkit for senior devops with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Pipeline Generator — scaffolds CI\u002FCD pipelines for GitHub Actions or CircleCI\npython scripts\u002Fpipeline_generator.py .\u002Fapp --platform=github --stages=build,test,deploy\n\n# Script 2: Terraform Scaffolder — generates and validates IaC modules for AWS\u002FGCP\u002FAzure\npython scripts\u002Fterraform_scaffolder.py .\u002Finfra --provider=aws --module=ecs-service --verbose\n\n# Script 3: Deployment Manager — generates deployment manifests + runbooks with rollback support\npython3 scripts\u002Fdeployment_manager.py deploy --env=staging --image=app:1.2.3 --strategy=blue-green --verbose --json\n```\n\n## Core Capabilities\n\n### 1. Pipeline Generator\n\nScaffolds CI\u002FCD pipeline configurations for GitHub Actions or CircleCI, with stages for build, test, security scan, and deploy.\n\n**Example — GitHub Actions workflow:**\n```yaml\n# .github\u002Fworkflows\u002Fci.yml\nname: CI\u002FCD Pipeline\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n    branches: [main]\n\njobs:\n  build-and-test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Set up Node.js\n        uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: '20'\n          cache: 'npm'\n      - run: npm ci\n      - run: npm run lint\n      - run: npm test -- --coverage\n      - name: Upload coverage\n        uses: codecov\u002Fcodecov-action@v4\n\n  build-docker:\n    needs: build-and-test\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Build and push image\n        uses: docker\u002Fbuild-push-action@v5\n        with:\n          push: ${{ github.ref == 'refs\u002Fheads\u002Fmain' }}\n          tags: ghcr.io\u002F${{ github.repository }}:${{ github.sha }}\n\n  deploy:\n    needs: build-docker\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    runs-on: ubuntu-latest\n    steps:\n      - name: Deploy to ECS\n        run: |\n          aws ecs update-service \\\n            --cluster production \\\n            --service app-service \\\n            --force-new-deployment\n```\n\n**Usage:**\n```bash\npython scripts\u002Fpipeline_generator.py \u003Cproject-path> --platform=github|circleci --stages=build,test,deploy\n```\n\n### 2. Terraform Scaffolder\n\nGenerates, validates, and plans Terraform modules. Enforces consistent module structure and runs `terraform validate` + `terraform plan` before any apply.\n\n**Example — AWS ECS service module:**\n```hcl\n# modules\u002Fecs-service\u002Fmain.tf\nresource \"aws_ecs_task_definition\" \"app\" {\n  family                   = var.service_name\n  requires_compatibilities = [\"FARGATE\"]\n  network_mode             = \"awsvpc\"\n  cpu                      = var.cpu\n  memory                   = var.memory\n\n  container_definitions = jsonencode([{\n    name      = var.service_name\n    image     = var.container_image\n    essential = true\n    portMappings = [{\n      containerPort = var.container_port\n      protocol      = \"tcp\"\n    }]\n    environment = [for k, v in var.env_vars : { name = k, value = v }]\n    logConfiguration = {\n      logDriver = \"awslogs\"\n      options = {\n        awslogs-group         = \"\u002Fecs\u002F${var.service_name}\"\n        awslogs-region        = var.aws_region\n        awslogs-stream-prefix = \"ecs\"\n      }\n    }\n  }])\n}\n\nresource \"aws_ecs_service\" \"app\" {\n  name            = var.service_name\n  cluster         = var.cluster_id\n  task_definition = aws_ecs_task_definition.app.arn\n  desired_count   = var.desired_count\n  launch_type     = \"FARGATE\"\n\n  network_configuration {\n    subnets          = var.private_subnet_ids\n    security_groups  = [aws_security_group.app.id]\n    assign_public_ip = false\n  }\n\n  load_balancer {\n    target_group_arn = aws_lb_target_group.app.arn\n    container_name   = var.service_name\n    container_port   = var.container_port\n  }\n}\n```\n\n**Usage:**\n```bash\npython scripts\u002Fterraform_scaffolder.py \u003Ctarget-path> --provider=aws|gcp|azure --module=ecs-service|gke-deployment|aks-service [--verbose]\n```\n\n### 3. Deployment Manager\n\nGenerates Kubernetes deployment manifests and ordered kubectl runbooks for blue\u002Fgreen or rolling strategies, with health-check gates before traffic switches and rollback runbooks. The tool writes manifests and prints the commands — it never applies them to a cluster itself, so every change gets a human review.\n\n**Example — Kubernetes blue\u002Fgreen deployment (blue-slot specific elements):**\n```yaml\n# k8s\u002Fdeployment-blue.yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: app-blue\n  labels:\n    app: myapp\n    slot: blue      # slot label distinguishes blue from green\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: myapp\n      slot: blue\n  template:\n    metadata:\n      labels:\n        app: myapp\n        slot: blue\n    spec:\n      containers:\n        - name: app\n          image: ghcr.io\u002Forg\u002Fapp:1.2.3\n          readinessProbe:       # gate: pod must pass before traffic switches\n            httpGet:\n              path: \u002Fhealthz\n              port: 8080\n            initialDelaySeconds: 10\n            periodSeconds: 5\n          resources:\n            requests:\n              cpu: \"250m\"\n              memory: \"256Mi\"\n            limits:\n              cpu: \"500m\"\n              memory: \"512Mi\"\n```\n\n**Usage:**\n```bash\npython scripts\u002Fdeployment_manager.py deploy \\\n  --env=staging|production \\\n  --image=app:1.2.3 \\\n  --strategy=blue-green|rolling \\\n  --health-check-url=https:\u002F\u002Fapp.example.com\u002Fhealthz\n\npython scripts\u002Fdeployment_manager.py rollback --env=production --to-version=1.2.2\npython scripts\u002Fdeployment_manager.py --analyze --env=production   # audit current state\n```\n\n## Resources\n\n- Pattern Reference: `references\u002Fcicd_pipeline_guide.md` — detailed CI\u002FCD patterns, best practices, anti-patterns\n- Workflow Guide: `references\u002Finfrastructure_as_code.md` — IaC step-by-step processes, optimization, troubleshooting\n- Technical Guide: `references\u002Fdeployment_strategies.md` — deployment strategy configs, security considerations, scalability\n- Tool Scripts: `scripts\u002F` directory\n\n## Development Workflow\n\n### 1. Infrastructure Changes (Terraform)\n\n```bash\n# Scaffold or update module\npython scripts\u002Fterraform_scaffolder.py .\u002Finfra --provider=aws --module=ecs-service --verbose\n\n# Validate and plan — review diff before applying\nterraform -chdir=infra init\nterraform -chdir=infra validate\nterraform -chdir=infra plan -out=tfplan\n\n# Apply only after plan review\nterraform -chdir=infra apply tfplan\n\n# Verify resources are healthy\naws ecs describe-services --cluster production --services app-service \\\n  --query 'services[0].{Status:status,Running:runningCount,Desired:desiredCount}'\n```\n\n### 2. Application Deployment\n\n```bash\n# Generate or update pipeline config\npython scripts\u002Fpipeline_generator.py . --platform=github --stages=build,test,security,deploy\n\n# Build and tag image\ndocker build -t ghcr.io\u002Forg\u002Fapp:$(git rev-parse --short HEAD) .\ndocker push ghcr.io\u002Forg\u002Fapp:$(git rev-parse --short HEAD)\n\n# Deploy with health-check gate\npython scripts\u002Fdeployment_manager.py deploy \\\n  --env=production \\\n  --image=app:$(git rev-parse --short HEAD) \\\n  --strategy=blue-green \\\n  --health-check-url=https:\u002F\u002Fapp.example.com\u002Fhealthz\n\n# Verify pods are running\nkubectl get pods -n production -l app=myapp\nkubectl rollout status deployment\u002Fapp-blue -n production\n\n# Switch traffic after verification\nkubectl patch service app-svc -n production \\\n  -p '{\"spec\":{\"selector\":{\"slot\":\"blue\"}}}'\n```\n\n### 3. Rollback Procedure\n\n```bash\n# Immediate rollback via deployment manager\npython scripts\u002Fdeployment_manager.py rollback --env=production --to-version=1.2.2\n\n# Or via kubectl\nkubectl rollout undo deployment\u002Fapp -n production\nkubectl rollout status deployment\u002Fapp -n production\n\n# Verify rollback succeeded\nkubectl get pods -n production -l app=myapp\ncurl -sf https:\u002F\u002Fapp.example.com\u002Fhealthz || echo \"ROLLBACK FAILED — escalate\"\n```\n\n## Multi-Cloud Cross-References\n\nUse these companion skills for cloud-specific deep dives:\n\n| Skill | Cloud | Use When |\n|-------|-------|----------|\n| **aws-solution-architect** | AWS | ECS\u002FEKS, Lambda, VPC design, cost optimization |\n| **azure-cloud-architect** | Azure | AKS, App Service, Virtual Networks, Azure DevOps |\n| **gcp-cloud-architect** | GCP | GKE, Cloud Run, VPC, Cloud Build *(coming soon)* |\n\n**Multi-cloud vs single-cloud decision:**\n- **Single-cloud** (default) — lower operational complexity, deeper managed-service integration, better cost leverage with committed-use discounts\n- **Multi-cloud** — required when mandated by compliance\u002Fdata residency, acquiring companies on different clouds, or needing best-of-breed services across providers (e.g., AWS for compute + GCP for ML)\n- **Hybrid** — on-prem + cloud; use when regulated workloads must stay on-prem while burst\u002Fnon-sensitive workloads run in the cloud\n\n> Start single-cloud. Add a second cloud only when there is a concrete business or compliance driver — not for theoretical redundancy.\n\n---\n\n## Cloud-Agnostic IaC\n\n### Terraform \u002F OpenTofu (Default Choice)\n\nTerraform (or its open-source fork OpenTofu) is the recommended IaC tool for most teams:\n- Single language (HCL) across AWS, Azure, GCP, and 3,000+ providers\n- State management with remote backends (S3, GCS, Azure Blob)\n- Plan-before-apply workflow prevents drift surprises\n- Cross-reference **terraform-patterns** for module structure, state isolation, and CI\u002FCD integration\n\n### Pulumi (Programming Language IaC)\n\nChoose Pulumi when the team strongly prefers TypeScript, Python, Go, or C# over HCL:\n- Full programming language — loops, conditionals, unit tests native\n- Same cloud provider coverage as Terraform\n- Easier onboarding for dev teams that resist learning HCL\n\n### When to Use Cloud-Native IaC\n\n| Tool | Use When |\n|------|----------|\n| **CloudFormation** | AWS-only shop; need native AWS support (StackSets, Service Catalog) |\n| **Bicep** | Azure-only shop; simpler syntax than ARM templates |\n| **Cloud Deployment Manager** | GCP-only; rare — most GCP teams prefer Terraform |\n\n> **Rule of thumb:** Use Terraform\u002FOpenTofu unless you are 100% committed to a single cloud AND the cloud-native tool offers a feature Terraform cannot replicate (e.g., AWS Service Catalog integration).\n\n---\n\n## Troubleshooting\n\nCheck the comprehensive troubleshooting section in `references\u002Fdeployment_strategies.md`.\n","# Senior Devops\n\nComplete toolkit for senior devops with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Pipeline Generator — scaffolds CI\u002FCD pipelines for GitHub Actions or CircleCI\npython scripts\u002Fpipeline_generator.py .\u002Fapp --platform=github --stages=build,test,deploy\n\n# Script 2: Terraform Scaffolder — generates and validates IaC modules for AWS\u002FGCP\u002FAzure\npython scripts\u002Fterraform_scaffolder.py .\u002Finfra --provider=aws --module=ecs-service --verbose\n\n# Script 3: Deployment Manager — generates deployment manifests + runbooks with rollback support\npython3 scripts\u002Fdeployment_manager.py deploy --env=staging --image=app:1.2.3 --strategy=blue-green --verbose --json\n```\n\n## Core Capabilities\n\n### 1. Pipeline Generator\n\nScaffolds CI\u002FCD pipeline configurations for GitHub Actions or CircleCI, with stages for build, test, security scan, and deploy.\n\n**Example — GitHub Actions workflow:**\n```yaml\n# .github\u002Fworkflows\u002Fci.yml\nname: CI\u002FCD Pipeline\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n    branches: [main]\n\njobs:\n  build-and-test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Set up Node.js\n        uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: '20'\n          cache: 'npm'\n      - run: npm ci\n      - run: npm run lint\n      - run: npm test -- --coverage\n      - name: Upload coverage\n        uses: codecov\u002Fcodecov-action@v4\n\n  build-docker:\n    needs: build-and-test\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Build and push image\n        uses: docker\u002Fbuild-push-action@v5\n        with:\n          push: ${{ github.ref == 'refs\u002Fheads\u002Fmain' }}\n          tags: ghcr.io\u002F${{ github.repository }}:${{ github.sha }}\n\n  deploy:\n    needs: build-docker\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    runs-on: ubuntu-latest\n    steps:\n      - name: Deploy to ECS\n        run: |\n          aws ecs update-service \\\n            --cluster production \\\n            --service app-service \\\n            --force-new-deployment\n```\n\n**Usage:**\n```bash\npython scripts\u002Fpipeline_generator.py \u003Cproject-path> --platform=github|circleci --stages=build,test,deploy\n```\n\n### 2. Terraform Scaffolder\n\nGenerates, validates, and plans Terraform modules. Enforces consistent module structure and runs `terraform validate` + `terraform plan` before any apply.\n\n**Example — AWS ECS service module:**\n```hcl\n# modules\u002Fecs-service\u002Fmain.tf\nresource \"aws_ecs_task_definition\" \"app\" {\n  family                   = var.service_name\n  requires_compatibilities = [\"FARGATE\"]\n  network_mode             = \"awsvpc\"\n  cpu                      = var.cpu\n  memory                   = var.memory\n\n  container_definitions = jsonencode([{\n    name      = var.service_name\n    image     = var.container_image\n    essential = true\n    portMappings = [{\n      containerPort = var.container_port\n      protocol      = \"tcp\"\n    }]\n    environment = [for k, v in var.env_vars : { name = k, value = v }]\n    logConfiguration = {\n      logDriver = \"awslogs\"\n      options = {\n        awslogs-group         = \"\u002Fecs\u002F${var.service_name}\"\n        awslogs-region        = var.aws_region\n        awslogs-stream-prefix = \"ecs\"\n      }\n    }\n  }])\n}\n\nresource \"aws_ecs_service\" \"app\" {\n  name            = var.service_name\n  cluster         = var.cluster_id\n  task_definition = aws_ecs_task_definition.app.arn\n  desired_count   = var.desired_count\n  launch_type     = \"FARGATE\"\n\n  network_configuration {\n    subnets          = var.private_subnet_ids\n    security_groups  = [aws_security_group.app.id]\n    assign_public_ip = false\n  }\n\n  load_balancer {\n    target_group_arn = aws_lb_target_group.app.arn\n    container_name   = var.service_name\n    container_port   = var.container_port\n  }\n}\n```\n\n**Usage:**\n```bash\npython scripts\u002Fterraform_scaffolder.py \u003Ctarget-path> --provider=aws|gcp|azure --module=ecs-service|gke-deployment|aks-service [--verbose]\n```\n\n### 3. Deployment Manager\n\nGenerates Kubernetes deployment manifests and ordered kubectl runbooks for blue\u002Fgreen or rolling strategies, with health-check gates before traffic switches and rollback runbooks. The tool writes manifests and prints the commands — it never applies them to a cluster itself, so every change gets a human review.\n\n**Example — Kubernetes blue\u002Fgreen deployment (blue-slot specific elements):**\n```yaml\n# k8s\u002Fdeployment-blue.yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: app-blue\n  labels:\n    app: myapp\n    slot: blue      # slot label distinguishes blue from green\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: myapp\n      slot: blue\n  template:\n    metadata:\n      labels:\n        app: myapp\n        slot: blue\n    spec:\n      containers:\n        - name: app\n          image: ghcr.io\u002Forg\u002Fapp:1.2.3\n          readinessProbe:       # gate: pod must pass before traffic switches\n            httpGet:\n              path: \u002Fhealthz\n              port: 8080\n            initialDelaySeconds: 10\n            periodSeconds: 5\n          resources:\n            requests:\n              cpu: \"250m\"\n              memory: \"256Mi\"\n            limits:\n              cpu: \"500m\"\n              memory: \"512Mi\"\n```\n\n**Usage:**\n```bash\npython scripts\u002Fdeployment_manager.py deploy \\\n  --env=staging|production \\\n  --image=app:1.2.3 \\\n  --strategy=blue-green|rolling \\\n  --health-check-url=https:\u002F\u002Fapp.example.com\u002Fhealthz\n\npython scripts\u002Fdeployment_manager.py rollback --env=production --to-version=1.2.2\npython scripts\u002Fdeployment_manager.py --analyze --env=production   # audit current state\n```\n\n## Resources\n\n- Pattern Reference: `references\u002Fcicd_pipeline_guide.md` — detailed CI\u002FCD patterns, best practices, anti-patterns\n- Workflow Guide: `references\u002Finfrastructure_as_code.md` — IaC step-by-step processes, optimization, troubleshooting\n- Technical Guide: `references\u002Fdeployment_strategies.md` — deployment strategy configs, security considerations, scalability\n- Tool Scripts: `scripts\u002F` directory\n\n## Development Workflow\n\n### 1. Infrastructure Changes (Terraform)\n\n```bash\n# Scaffold or update module\npython scripts\u002Fterraform_scaffolder.py .\u002Finfra --provider=aws --module=ecs-service --verbose\n\n# Validate and plan — review diff before applying\nterraform -chdir=infra init\nterraform -chdir=infra validate\nterraform -chdir=infra plan -out=tfplan\n\n# Apply only after plan review\nterraform -chdir=infra apply tfplan\n\n# Verify resources are healthy\naws ecs describe-services --cluster production --services app-service \\\n  --query 'services[0].{Status:status,Running:runningCount,Desired:desiredCount}'\n```\n\n### 2. Application Deployment\n\n```bash\n# Generate or update pipeline config\npython scripts\u002Fpipeline_generator.py . --platform=github --stages=build,test,security,deploy\n\n# Build and tag image\ndocker build -t ghcr.io\u002Forg\u002Fapp:$(git rev-parse --short HEAD) .\ndocker push ghcr.io\u002Forg\u002Fapp:$(git rev-parse --short HEAD)\n\n# Deploy with health-check gate\npython scripts\u002Fdeployment_manager.py deploy \\\n  --env=production \\\n  --image=app:$(git rev-parse --short HEAD) \\\n  --strategy=blue-green \\\n  --health-check-url=https:\u002F\u002Fapp.example.com\u002Fhealthz\n\n# Verify pods are running\nkubectl get pods -n production -l app=myapp\nkubectl rollout status deployment\u002Fapp-blue -n production\n\n# Switch traffic after verification\nkubectl patch service app-svc -n production \\\n  -p '{\"spec\":{\"selector\":{\"slot\":\"blue\"}}}'\n```\n\n### 3. Rollback Procedure\n\n```bash\n# Immediate rollback via deployment manager\npython scripts\u002Fdeployment_manager.py rollback --env=production --to-version=1.2.2\n\n# Or via kubectl\nkubectl rollout undo deployment\u002Fapp -n production\nkubectl rollout status deployment\u002Fapp -n production\n\n# Verify rollback succeeded\nkubectl get pods -n production -l app=myapp\ncurl -sf https:\u002F\u002Fapp.example.com\u002Fhealthz || echo \"ROLLBACK FAILED — escalate\"\n```\n\n## Multi-Cloud Cross-References\n\nUse these companion skills for cloud-specific deep dives:\n\n| Skill | Cloud | Use When |\n|-------|-------|----------|\n| **aws-solution-architect** | AWS | ECS\u002FEKS, Lambda, VPC design, cost optimization |\n| **azure-cloud-architect** | Azure | AKS, App Service, Virtual Networks, Azure DevOps |\n| **gcp-cloud-architect** | GCP | GKE, Cloud Run, VPC, Cloud Build *(coming soon)* |\n\n**Multi-cloud vs single-cloud decision:**\n- **Single-cloud** (default) — lower operational complexity, deeper managed-service integration, better cost leverage with committed-use discounts\n- **Multi-cloud** — required when mandated by compliance\u002Fdata residency, acquiring companies on different clouds, or needing best-of-breed services across providers (e.g., AWS for compute + GCP for ML)\n- **Hybrid** — on-prem + cloud; use when regulated workloads must stay on-prem while burst\u002Fnon-sensitive workloads run in the cloud\n\n> Start single-cloud. Add a second cloud only when there is a concrete business or compliance driver — not for theoretical redundancy.\n\n---\n\n## Cloud-Agnostic IaC\n\n### Terraform \u002F OpenTofu (Default Choice)\n\nTerraform (or its open-source fork OpenTofu) is the recommended IaC tool for most teams:\n- Single language (HCL) across AWS, Azure, GCP, and 3,000+ providers\n- State management with remote backends (S3, GCS, Azure Blob)\n- Plan-before-apply workflow prevents drift surprises\n- Cross-reference **terraform-patterns** for module structure, state isolation, and CI\u002FCD integration\n\n### Pulumi (Programming Language IaC)\n\nChoose Pulumi when the team strongly prefers TypeScript, Python, Go, or C# over HCL:\n- Full programming language — loops, conditionals, unit tests native\n- Same cloud provider coverage as Terraform\n- Easier onboarding for dev teams that resist learning HCL\n\n### When to Use Cloud-Native IaC\n\n| Tool | Use When |\n|------|----------|\n| **CloudFormation** | AWS-only shop; need native AWS support (StackSets, Service Catalog) |\n| **Bicep** | Azure-only shop; simpler syntax than ARM templates |\n| **Cloud Deployment Manager** | GCP-only; rare — most GCP teams prefer Terraform |\n\n> **Rule of thumb:** Use Terraform\u002FOpenTofu unless you are 100% committed to a single cloud AND the cloud-native tool offers a feature Terraform cannot replicate (e.g., AWS Service Catalog integration).\n\n---\n\n## Troubleshooting\n\nCheck the comprehensive troubleshooting section in `references\u002Fdeployment_strategies.md`.\n",{"name":5,"description":7},"main","55ae24ca5523c0499dd70b2874ef674a0e66a85b","engineering-team\u002Fskills\u002Fsenior-devops","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator","2026-07-04 02:45:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add motivatedc-creator\u002FSaafy --skill senior-devops",{"tool":36,"command":37},"bunx","bunx skills add motivatedc-creator\u002FSaafy --skill senior-devops",{"tool":39,"command":40},"pnpm","pnpm dlx skills add motivatedc-creator\u002FSaafy --skill senior-devops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002FSKILL.md",true,[44,50,54,58,64,68],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fcicd_pipeline_guide.md","REFERENCE","参考文档",1610,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002Freferences\u002Fcicd_pipeline_guide.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdeployment_strategies.md",1612,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002Freferences\u002Fdeployment_strategies.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Finfrastructure_as_code.md",1613,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002Freferences\u002Finfrastructure_as_code.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Fdeployment_manager.py","SCRIPT","脚本",9835,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002Fscripts\u002Fdeployment_manager.py",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Fpipeline_generator.py",7786,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002Fscripts\u002Fpipeline_generator.py",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fterraform_scaffolder.py",12219,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsenior-devops\u002Fscripts\u002Fterraform_scaffolder.py",[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78558T3RQ22S1B5H0FJAY1Y","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7854YEAAV883M2PKS04TQEK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7854NCGDBQ6Q0QG2YY4VHSX","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M78549YZMPYGC1F6S7ZJ4VF8","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M78541PWEQMBPN91PEZZK8H7","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7853P7CWJNW5G0Z99YB6H5D","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]