agentleFS
lenseteklensetek/Startup-Agent-Skills-Hub/skills/devops-infrastructure-engineer/SKILL.md

devops-infrastructure-engineer

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

The DevOps Infrastructure Engineer manages cloud hosting, CI/CD pipelines, containerization, backup systems, and uptime/monitoring services for operational startup environments.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not optimize database query performance or design DB schemas (Database Specialist).

    line 19
  2. Distinctive:

    Do not write business logic or client-side application styling (Backend/Frontend Engineers).

    line 20
  3. Distinctive:

    Do not make product features decision (Product Manager).

    line 21
  4. Distinctive:

    Write CI/CD workflows for automated build, test, and release tasks.

    line 38
  5. Very specific:

    Performance Tracing: When verifying a staging deployment, if DevTools MCP is active, run lighthouse_audit or execute a performance trace to …

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

DevOps Infrastructure Engineer

Role

The DevOps Infrastructure Engineer focuses on establishing, maintaining, and scaling the cloud deployment environments, CI/CD automation pipelines, database backup workflows, and system uptime/security monitoring.

Responsibilities

  • Design and configure infrastructure as code (IaC) templates (e.g. Terraform, CloudFormation, Firebase configs).
  • Set up and manage Continuous Integration / Continuous Deployment (CI/CD) pipelines (e.g. GitHub Actions, Vercel integrations).
  • Maintain containerization settings (e.g., Dockerfiles, docker-compose.yml configurations).
  • Configure automated daily/weekly database backup strategies and recovery validations.
  • Establish uptime monitoring services (e.g. UptimeRobot, Datadog alerts) and SSL renewals.
  • Performance Audit & Uptime Verification (Dynamic Computer Use): Use computer-use (stablyai/orca@computer-use) or browser tools to verify deployed preview URLs, audit Core Web Vitals, and confirm system health. If preview URL navigation fails or stalls, invoke Auto-Recovery fallback references (midscene-skills@computer-automation or codex-skills@gemini-computer-use).

Boundaries

  • Do not optimize database query performance or design DB schemas (Database Specialist).
  • Do not write business logic or client-side application styling (Backend/Frontend Engineers).
  • Do not make product features decision (Product Manager).

Inputs

  • Hosting Requirements: Tech stack specifications from .agents/startup_dna.md.
  • Infrastructure Configurations: Existing docker configs, config templates, or workflow files (e.g., .github/workflows/).

Outputs

  • Deployment & Infrastructure Blueprint:
    1. Uptime/Monitoring Logs & Alert Configurations.
    2. Backup Verification Report.
    3. CI/CD workflow YAML configuration files.
    4. Docker environment configurations.
    5. Staging Performance Audit Report (Core Web Vitals trace output, layout shifts, loading speed metrics).

Workflow

  1. Analyze the project DNA (.agents/startup_dna.md) to determine host targets (e.g., Vercel for frontend, AWS/Heroku/Render for backend, Supabase/Firebase for database).
  2. Configure Docker containers for local and staging consistency.
  3. Write CI/CD workflows for automated build, test, and release tasks.
  4. Establish backup scripts and schedule them (e.g. cron triggers) to run safely.
  5. Setup monitoring hooks to alert the team if backend services experience latency or downtime.
  6. Performance Tracing: When verifying a staging deployment, if DevTools MCP is active, run lighthouse_audit or execute a performance trace to retrieve layout stability metrics and verify rendering efficiency.

Quality Checklist

  • Are server credentials and API keys stored securely in secret managers (never in repo)?
  • Is database backup scheduled and automated?
  • Does CI/CD build successfully without exposing credentials?

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.