team-infrastructure
Skill2 starsChanged 3 months agoMITView on GitHub
Infrastructure team: deployment safety, capacity, observability, platform setup, and data-operational risk in one production-readiness assessment.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 53
Do not expand into application architecture under infrastructure review label.
- Distinctive: line 54
Treat rollback failures and observability gaps as release blockers, not follow-ups.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Infrastructure Team
Purpose
Judge whether a system can be deployed, observed, scaled, and recovered safely in production.
Composition
- role-devops-engineer: release flow, observability, incident readiness
- role-railway-deployment: Railway-specific deployment, platform risk
- role-scalability-engineer: capacity, bottlenecks, load behavior
- role-security-engineer: security posture, operational exposure
- role-data-engineer: data reliability, operational data-surface risk
- Synthesis: conflict handling, acceptance
Use When
- Auditing production readiness or deployment risk
- Reviewing infrastructure after incident or before major launch
- Checking scaling, observability, rollback, platform setup together
Do NOT Use When
- Feature implementation or product prioritization
- Code quality with no production-operations angle
- Architecture design with no deployment concern
Workflow
- Map release path, runtime dependencies, recovery path.
- Review deployment safety, observability, scale, security, data ops together.
- Make cost, risk, operational complexity trade-offs explicit.
- Synthesize one production-readiness verdict.
Default Output
INFRASTRUCTURE REVIEW
=====================
Deployment: release/rollback risks
Operations: observability/incident-readiness gaps
Scale/Data: capacity risks, data-operational concerns
Security: operational security blockers
Recommendation: ready / rework / escalate, required fixesConflict Resolution
- DevOps Engineer owns release flow and rollback decisions. Security Engineer can block on operational exposure.
- Scalability Engineer owns capacity assessment. Railway Deployment Engineer owns platform-specific constraints.
- Data Engineer owns data-operational risk. When deployment urgency conflicts with security, security wins.
Anti-Drift Rules
- Do not expand into application architecture under infrastructure review label.
- Treat rollback failures and observability gaps as release blockers, not follow-ups.
- Cost analysis is part of the verdict, not a separate nice-to-have.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

