Stats
Actions
Tags
From silver-bullet
Maps IaC toolchain and cloud provider context to the best available plugin skill. Used by the devops-cycle workflow at DISCUSS, PLAN, EXECUTE, VERIFY, and FINALIZATION trigger points.
How this skill is triggered — by the user, by Claude, or both
Slash command
/silver-bullet:devops-skill-routerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Maps the current DevOps context (IaC tool, cloud provider, task type) to the best
Maps the current DevOps context (IaC tool, cloud provider, task type) to the best available plugin skill. Silver Bullet's devops-cycle workflow references this router at contextual trigger points — it is NOT a required workflow step.
When to use: The devops-cycle workflow invokes this router automatically at trigger points (DISCUSS, PLAN, EXECUTE, VERIFY, FINALIZATION). Also invocable it directly to find the best skill for a specific DevOps task.
Read .silver-bullet.json and check the devops_plugins section:
"devops_plugins": {
"hashicorp": true/false,
"awslabs": true/false,
"pulumi": true/false,
"devops-skills": true/false,
"wshobson": true/false
}
If devops_plugins is missing or the config doesn't exist, assume all are false.
Determine which context applies from the current task, user discussion, or file being worked on. Multiple contexts can apply simultaneously.
Use the routing table below. For each context, try skills in priority order. If a candidate skill's plugin is not installed or the skill cannot be invoked, STOP and notify the user instead of proceeding silently. If no plugin is available for a context, offer the user: A. Install the plugin and retry first, B. Continue with an explicitly approved Silver Bullet degraded path, C. Switch to a different workflow or stop.
| Context | Trigger | Priority 1 | Priority 2 | Priority 3 |
|---|---|---|---|---|
| Terraform HCL authoring | .tf files, HCL code, Terraform plans | hashicorp: terraform-code-generation | devops-skills: iac-terraform | (none — stop and ask) |
| Terraform module design | Creating reusable modules, module registry | hashicorp: terraform-module-generation | devops-skills: iac-terraform | (none) |
| Terraform provider dev | Writing custom TF providers | hashicorp: terraform-provider-development | (none) | |
| Terragrunt | terragrunt.hcl, multi-env Terraform | devops-skills: iac-terraform | (none) | |
| Pulumi programs | Pulumi TypeScript/Python/Go IaC | pulumi: pulumi-best-practices | pulumi: pulumi-component | (none) |
| Pulumi components | ComponentResource authoring | pulumi: pulumi-component | pulumi: pulumi-best-practices | (none) |
| Pulumi Automation API | Programmatic Pulumi (CI/CD integration) | pulumi: pulumi-automation-api | (none) | |
| CDK / CloudFormation | AWS CDK constructs, CF templates | awslabs: deploy-on-aws | (none) |
| Context | Trigger | Priority 1 | Priority 2 |
|---|---|---|---|
| Terraform → Pulumi | Migrating from TF to Pulumi | pulumi: pulumi-terraform-to-pulumi | (none) |
| CDK → Pulumi | Migrating from AWS CDK to Pulumi | pulumi: pulumi-cdk-to-pulumi | (none) |
| CloudFormation → Pulumi | Migrating CF to Pulumi | pulumi: cloudformation-to-pulumi | (none) |
| ARM/Bicep → Pulumi | Migrating Azure ARM to Pulumi | pulumi: pulumi-arm-to-pulumi | (none) |
| GCP → AWS migration | Migrating GCP infra to AWS | awslabs: migration-to-aws | (none) |
| Context | Trigger | Priority 1 | Priority 2 |
|---|---|---|---|
| AWS architecture | Deploy to AWS, architecture decisions | awslabs: deploy-on-aws | devops-skills: aws-cost-optimization |
| AWS serverless | Lambda, API Gateway, Step Functions, EventBridge | awslabs: aws-serverless | (none) |
| AWS databases | RDS, DynamoDB, Aurora DSQL | awslabs: databases-on-aws | (none) |
| AWS geospatial | Maps, geocoding, routing | awslabs: amazon-location-service | (none) |
| AWS Amplify | Full-stack apps with Amplify | awslabs: aws-amplify | (none) |
| AWS cost optimization | Cloud spend, unused resources | devops-skills: aws-cost-optimization | awslabs: deploy-on-aws |
| Context | Trigger | Priority 1 | Priority 2 |
|---|---|---|---|
| K8s troubleshooting | Pod failures, CrashLoopBackOff, OOM, cluster issues | devops-skills: k8s-troubleshooter | wshobson: kubernetes-operations |
| K8s manifests / Helm | Writing Deployments, Services, Helm charts | wshobson: kubernetes-operations | devops-skills: k8s-troubleshooter |
| K8s security | RBAC, NetworkPolicies, PodSecurityPolicies | wshobson: kubernetes-operations | devops-skills: k8s-troubleshooter |
| Context | Trigger | Priority 1 | Priority 2 |
|---|---|---|---|
| CI/CD pipelines | GitHub Actions, Jenkins, GitLab CI, CircleCI | devops-skills: ci-cd | (none) |
| GitOps | ArgoCD, Flux CD, multi-cluster sync | devops-skills: gitops-workflows | wshobson: kubernetes-operations |
| Context | Trigger | Priority 1 | Priority 2 |
|---|---|---|---|
| Monitoring / observability | Prometheus, Grafana, Datadog, SLOs, alerts | devops-skills: monitoring-observability | (none) |
| Packer images | Machine images, AMIs, Azure images | hashicorp: packer-builders | hashicorp: packer-hcp |
| Context | Trigger | Priority 1 | Priority 2 |
|---|---|---|---|
| Secrets management | Vault, secret rotation, env config | pulumi: pulumi-esc | (none) |
For the highest-priority available skill:
/<plugin-namespace>:<skill-name> (e.g., /hashicorp:terraform-code-generation)/<skill-name>@<plugin-name> (e.g., /terraform-code-generation@hashicorp)/<skill-name> (e.g., /terraform-code-generation)
Use whichever pattern works for the installed plugin version.Important: Routed skills are enrichments, not gates. A failed or missing plugin skill NEVER blocks the workflow. Only Silver Bullet's own quality gates and SB lifecycle steps are enforcement gates.
terraform-code-generation — Write HCL, generate Terraform configsterraform-module-generation — Create reusable Terraform modulesterraform-provider-development — Develop custom Terraform providerspacker-builders — Build machine images (AWS, Azure, Windows)packer-hcp — HCP Packer registry integrationdeploy-on-aws — AWS architecture recommendations, IaC generationaws-serverless — Lambda, API Gateway, EventBridge, Step Functionsdatabases-on-aws — Database design, Aurora DSQLmigration-to-aws — GCP-to-AWS infrastructure migrationamazon-location-service — Geospatial (maps, geocoding, routing)aws-amplify — Full-stack app developmentpulumi-best-practices — Pulumi program best practicespulumi-component — ComponentResource authoringpulumi-automation-api — Automation API patternspulumi-esc — Environments, Secrets, Configurationpulumi-terraform-to-pulumi — Migrate Terraform → Pulumipulumi-cdk-to-pulumi — Migrate AWS CDK → Pulumicloudformation-to-pulumi — Migrate CloudFormation → Pulumipulumi-arm-to-pulumi — Migrate Azure ARM/Bicep → Pulumiiac-terraform — Terraform/Terragrunt IaC managementk8s-troubleshooter — Kubernetes troubleshooting and diagnosticsaws-cost-optimization — AWS cost analysis and optimizationci-cd — CI/CD pipeline design and troubleshootinggitops-workflows — ArgoCD and Flux CD multi-clustermonitoring-observability — Metrics, alerts, dashboards, SLOskubernetes-operations — K8s manifests, Helm, GitOps, securitynpx claudepluginhub alo-exp/silver-bullet --plugin silver-bulletGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.