agentleFS
Sign inStart free
rade-nugrohorade-nugroho/Agentic-Enteprises-Skill/cloud-system-administrator/SKILL.md

cloud-system-administrator

Skill9 starsChanged 6 months agoMITView on GitHub

Guides cloud system administration—day-2 operations on AWS, GCP, and Azure: access requests and IAM role assignment, key and certificate rotation, OS patching and maintenance windows, backup and restore execution, monitoring and alert triage, quota and limit increases, runbooks, change records, and on-call troubleshooting of cloud control-plane and managed-service issues. Use when operating an existing cloud estate, fulfilling access tickets, running restores, responding to cloud infra alerts, or executing hygiene cleanup—not for greenfield VPC/service build-out (cloud-engineer), cloud architecture ADRs (cloud-architect), enterprise CCoE programs (enterprise-cloud-architect), CI/CD pipelines (devops), Kubernetes cluster admin (cluster-deployment-engineer), or designing SEV/on-call programs (incident-management-engineer).

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Run patch and maintenance windows for VMs and managed instance groups

    line 21

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

Cloud System Administrator

When to Use

  • Process access requests — IAM roles, group membership, break-glass (per policy)
  • Execute credential rotation — access keys, service account keys, certificates
  • Run patch and maintenance windows for VMs and managed instance groups
  • Operate backups — snapshots, retention checks, test restores
  • Triage alerts — CPU, disk, quota, health checks; escalate per runbook
  • Handle incidents — connectivity, permission denied, throttling, regional outages
  • Request quota/limit increases and track vendor cases
  • Perform hygiene — orphaned volumes, old snapshots, untagged resources, idle compute
  • Maintain runbooks and execute change tickets for routine infra changes
  • Support audit — access reviews, log exports, evidence for reviewers

When NOT to Use

  • Design landing zones, migration, or reference architecture → cloud-architect, enterprise-cloud-architect
  • Build new VPC, RDS, or serverless stacks from requirements → cloud-engineer
  • Terraform module libraries and platform IaC → infrastructure-engineer
  • Pipeline failures and GitOps sync → devops
  • K8s cluster upgrades and Helm → cluster-deployment-engineer
  • Define SEV levels, paging policy, postmortem program → incident-management-engineer
  • Security program, IdP design, SIEM → information-security-engineer
  • Entitlement design, access review campaigns, federation architecture → iam-specialist
  • Application bug fixes → senior-software-engineer
  • GL reconciliation of cloud invoices → compute-accounting-manager

Related skills

NeedSkill
New cloud build and deep service configcloud-engineer
Cloud architecturecloud-architect
Enterprise cloud governanceenterprise-cloud-architect
CI/CD and delivery SREdevops
Kubernetes operationscluster-deployment-engineer
Incident program designincident-management-engineer
Security architectureinformation-security-engineer
IAM governance, reviews, PAM policy (not ticket execution)iam-specialist
Compliance evidencecompliance-engineer
BCM program, RTO/RPO, restore-test criteria, cyber recovery sequencingbcm-disaster-recovery-specialist
Customer-facing support ticketssupport-engineer
Status/comms for major outagescommunication-lead

Core Workflows

1. Scope and operations model

Responsibilities, escalation, change control.

See references/cloud_sysadmin_scope.md.

2. IAM and access operations

Requests, reviews, rotation.

See references/iam_access_operations.md.

3. Compute and OS maintenance

Patching, instances, disks.

See references/compute_os_maintenance.md.

4. Monitoring and incident response

Alerts, triage, runbooks.

See references/monitoring_incident_response.md.

5. Backup and restore operations

Snapshots, drills, recovery steps.

See references/backup_restore_operations.md.

6. Operational hygiene

Quotas, certs, cleanup, DNS ops.

See references/operational_hygiene.md.

Outputs

  • Completed change — ticket ID, steps, rollback noted
  • Access grant record — who, what role, expiry if temporary
  • Incident timeline — detection, actions, resolution, follow-ups
  • Restore report — RPO achieved, data validated
  • Hygiene report — resources removed, savings estimate
  • Runbook update — gaps found during incident

Principles

  • Least privilege — grant minimum role; time-bound elevation
  • Change control — no prod change without ticket and rollback
  • Automate repeat work — scripts over manual clicks where safe
  • Document actions — audit trail in ticket and logs
  • Escalate architecture — recurring failures may need cloud-engineer or cloud-architect

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.

Reviews can't be read right now.

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.

Check your setup, free