Infrastructure catchall
Skill Chipagosfinest/enterprise-team/enterprise-team/skills/infrastructure-catchall
Hire a whole company with one plugin. 75 specialized AI agents across Engineering, Product, Infrastructure, Data, Security, Marketing, Sales, Finance, Legal, and People.
npx -y skills add Chipagosfinest/enterprise-team --skill infrastructure-catchallAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.9 KB, as published. Nobody here has run it
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.