infrastructure-catchall
starsforks
How to install infrastructure-catchall?
chipagosfinest/enterprise-team/infrastructure-catchall
$npx -y skills add Chipagosfinest/enterprise-team --skill infrastructure-catchallRoutes 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,
SKILL.md
| 1 | # Infrastructure Department |
| 2 | |
| 3 | Routes infrastructure work to the appropriate specialist role. |
| 4 | |
| 5 | ## Routing Targets |
| 6 | |
| 7 | | Role | Handles | |
| 8 | |---|---| |
| 9 | | devops-engineer | CI/CD pipelines, Docker, Kubernetes, Terraform, GitHub Actions, deployments | |
| 10 | | sre | Monitoring, alerting, incident response, SLOs, reliability, on-call | |
| 11 | | database-engineer | PostgreSQL, schema design, query optimization, migrations, Redis, Supabase | |
| 12 | | systems-admin | Linux servers, networking, DNS, SSL, cloud platforms, security hardening | |
| 13 | | it-support | Technical support, IT infrastructure, access management, security incidents | |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | - "Set up a CI/CD pipeline with GitHub Actions" -> devops-engineer |
| 18 | - "Configure monitoring and alerts for our API" -> sre |
| 19 | - "Optimize slow database queries on the users table" -> database-engineer |
| 20 | - "Set up DNS and SSL for our new domain" -> systems-admin |
| 21 | - "Deploy our app to Railway with Docker" -> devops-engineer |
| 22 | - "Investigate the production outage from last night" -> sre |
| 23 | - "Design the database schema for multi-tenancy" -> database-engineer |
| 24 | - "Set up VPN access for the team" -> systems-admin |
| 25 | |
| 26 | ## Workflow |
| 27 | |
| 28 | 1. Identify the infrastructure domain from the request. |
| 29 | 2. If the request spans multiple domains (e.g., "deploy + monitor"), route to the role handling the primary action. |
| 30 | 3. For incident-related requests, always route to sre first. |
| 31 | 4. For database requests embedded in a feature build, consider routing to engineering-orchestrator instead. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
