agentsclimarketplace

Devops infrastructure engineer

Skill lensetek/Startup-Agent-Skills-Hub/skills/devops-infrastructure-engineer

Startup Agent Skills Hub

Install
npx -y skills add lensetek/Startup-Agent-Skills-Hub --skill devops-infrastructure-engineer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 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

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

SKILL.md

3.2 KB, 621 tokens by cl100k_base, as published. Nobody here has run it

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.
  • Verify security policies on cloud servers (ports, firewall rules, API gateways).
  • Performance Audit & Optimization (Dynamic Trace): If Chrome DevTools MCP tools are active (e.g. lighthouse_audit, performance_analyze_insight), run performance traces on staging or local deployments to audit Core Web Vitals (LCP, CLS, FID) and provide optimization lists to speed up load times before pipeline release. Fall back to manual static auditing if unavailable.

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?

Gives 0 of the 12 instructions most monitoring observability skills give in 621 tokens

Counted across 481 of the 483 authors here whose files we hold, read 2026-08-06

  • link every alert to a runbookin 43 of 481, across 35 files
  • use structured json loggingin 36 of 481, across 31 files
  • alert on user-facing symptomsin 20 of 481, across 15 files
  • emit structured JSON logs with stable event namesin 18 of 481, across 13 files
  • propagate trace context across boundariesin 16 of 481
  • use histograms for latency trackingin 14 of 481, across 9 files
  • use OpenTelemetry for distributed tracingin 13 of 481, across 8 files
  • include a correlation ID on every log linein 13 of 481, across 8 files
  • Define service level objectivesin 10 of 481, across 7 files
  • Call useAzureMonitor before importing other modulesin 9 of 481, across 2 files
  • stop and ask for clarification if inputs are missingin 9 of 481, across 2 files
  • define on-call questions before adding telemetryin 9 of 481, across 4 files

Said here and by no other author read

  • configure infrastructure as code templates
  • set up continuous integration and deployment pipelines
  • maintain containerization configurations
  • configure automated database backups
  • establish uptime monitoring and alerts
  • verify cloud server security policies

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.