← Back to the catalog Routes infrastructure requests to the correct specialist based on domain: CI/CD, containers, cloud, databases, monitoring, reliability, and systems admin. Triggers: docker, kubernetes, terraform, ci/cd, github actions, deploy, railway, vercel, aws, database, postgresql, supabase, monitoring, alerting, incident, slo, reliability, nginx, ssl, dns, server, linux, networking.
View on GitHub ↗ Copy repo URL Copy SKILL.md link /plugin marketplace add Chipagosfinest/enterprise-team The exact command may vary by repository. Check the README on GitHub.
For the skill author
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
Markdown HTML
[](https://www.skillteca.com.br/skills/infrastructure-catchall?utm_source=badge&utm_medium=readme&utm_campaign=badge) Copy snippet Resources to assist in writing various internal communications, adhering to company-preferred formats. Claude should utilize this skill for status reports, leadership updates, newsletters, FAQs, and other internal documents.
DevOps e Infra by anthropics
Monitors a pull request or review cycle until it is ready to merge. This skill is used to track PR comments, reviews, and CI status until all actionable issues are resolved.
DevOps e Infra #ai by thedotmack
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
DevOps e Infra #ai by thedotmack
Token-optimized structural code search using tree-sitter AST parsing. Use this instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
DevOps e Infra #ai by thedotmack
Category alert
One short email with only the new DevOps e Infra skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Infrastructure Department
Routes infrastructure work to the appropriate specialist role.
Routing Targets
Role Handles devops-engineer CI/CD pipelines, Docker, Kubernetes, Terraform, GitHub Actions, deployments sre Monitoring, alerting, incident response, SLOs, reliability, on-call database-engineer PostgreSQL, schema design, query optimization, migrations, Redis, Supabase systems-admin Linux servers, networking, DNS, SSL, cloud platforms, security hardening it-support Technical support, IT infrastructure, access management, security incidents
Examples
"Set up a CI/CD pipeline with GitHub Actions" -> devops-engineer
"Configure monitoring and alerts for our API" -> sre
"Optimize slow database queries on the users table" -> database-engineer
"Set up DNS and SSL for our new domain" -> systems-admin
"Deploy our app to Railway with Docker" -> devops-engineer
"Investigate the production outage from last night" -> sre
"Design the database schema for multi-tenancy" -> database-engineer
"Set up VPN access for the team" -> systems-admin
Workflow
Identify the infrastructure domain from the request.
If the request spans multiple domains (e.g., "deploy + monitor"), route to the role handling the primary action.
For incident-related requests, always route to sre first.
For database requests embedded in a feature build, consider routing to engineering-orchestrator instead.
Read full description↓
Comments · No comments No comments yet. Be the first. 