agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/cloud-platforms/SKILL.md

cloud-platforms

Skill2 starsChanged 6 months agoMITView on GitHub

Cloud platform reference modules — GCP, Azure, AWS. Provides platform-specific CLI commands, managed service patterns, networking, IAM, observability, and operational procedures. Activated when working with cloud infrastructure, production environments, managed databases, container orchestration, or cloud-native services. Detect the target platform from the project's `AGENTS.md` tech stack declaration.

2 other projects use 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, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Detect platform: Read the project's AGENTS.md tech stack declaration to identify which cloud platform(s) are in use

    line 17
  2. Distinctive:

    Load the right module: Read the corresponding resource file(s) below

    line 18
  3. Distinctive:

    Apply patterns: Use platform-specific CLI commands, service names, and operational patterns from the loaded module

    line 19
  4. Distinctive:

    If AGENTS.md does not declare a cloud platform, ask the user before proceeding with platform-specific operations.

    line 29
  5. Distinctive:

    If the project uses multi-cloud, load all relevant modules and apply patterns per service based on where it runs.

    line 31

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

Cloud Platforms

Pluggable cloud platform knowledge modules. Each resource file contains platform-specific patterns for one cloud provider.

How It Works

  1. Detect platform: Read the project's AGENTS.md tech stack declaration to identify which cloud platform(s) are in use
  2. Load the right module: Read the corresponding resource file(s) below
  3. Apply patterns: Use platform-specific CLI commands, service names, and operational patterns from the loaded module

Platform Detection Signals

Signal in AGENTS.md / ProjectPlatformResource File
GCP, Google Cloud, GKE, Cloud SQL, Cloud Build, gcloud, Artifact RegistryGoogle Cloud Platformgcp-reference.md
Azure, AKS, Azure SQL, Azure DevOps, az CLI, ACR, Azure MonitorMicrosoft Azureazure-reference.md
AWS, EKS, RDS, CodePipeline, aws CLI, ECR, CloudWatchAmazon Web Servicesaws-reference.md

If AGENTS.md does not declare a cloud platform, ask the user before proceeding with platform-specific operations.

If the project uses multi-cloud, load all relevant modules and apply patterns per service based on where it runs.

Module Structure

Each reference file follows a consistent structure:

  1. Core Platform — account/project structure, IAM, networking, secrets, tagging
  2. Container Orchestration — managed Kubernetes (GKE/AKS/EKS) patterns
  3. Managed Database — managed SQL service patterns and reliability
  4. CI/CD — platform-native build and deploy services
  5. Observability — monitoring, logging, alerting, dashboards
  6. CLI Reference — essential CLI commands for diagnostics and operations
  7. Security and Compliance — audit logging, encryption, network security

Integration

  • Used by roles: devops-engineer role, sre-engineer role, cloud-architect role
  • Used by workflows: analyze-prod skill, bugfix skill, infra-change skill, deploy-production skill, ml-pipeline skill
  • Complements: deployment-procedures skill (rollback procedures)

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.