agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/team-infrastructure/SKILL.md

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.

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
  1. Distinctive:

    Do not expand into application architecture under infrastructure review label.

    line 53
  2. Distinctive:

    Treat rollback failures and observability gaps as release blockers, not follow-ups.

    line 54

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Map release path, runtime dependencies, recovery path.
  2. Review deployment safety, observability, scale, security, data ops together.
  3. Make cost, risk, operational complexity trade-offs explicit.
  4. 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 fixes

Conflict 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.