plugin/skills/cloud-platforms/SKILL.md
Use this skill when authoring or running a workflow that needs cloud-platform-specific commands, or when reviewing such workflows for platform coverage — as a knowledge module (not a workflow itself) providing platform-specific CLI commands, managed service patterns, networking, IAM, observability, and operational procedures across GCP, Azure, and AWS. Loaded by `/analyze-prod`, `/infra-change`, `/deploy-production`, and similar workflows.
npx skillsauth add avav25/ai-assets cloud-platformsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pluggable cloud platform knowledge modules. Each resource file contains platform-specific patterns for one cloud provider.
CLAUDE.md tech stack declaration to identify which cloud platform(s) are in use| Signal in CLAUDE.md / Project | Platform | Resource File |
|---|---|---|
| GCP, Google Cloud, GKE, Cloud SQL, Cloud Build, gcloud, Artifact Registry | Google Cloud Platform | gcp-reference.md |
| Azure, AKS, Azure SQL, Azure DevOps, az CLI, ACR, Azure Monitor | Microsoft Azure | azure-reference.md |
| AWS, EKS, RDS, CodePipeline, aws CLI, ECR, CloudWatch | Amazon Web Services | aws-reference.md |
If CLAUDE.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.
Each reference file follows a consistent structure:
Agent(devops-engineer), Agent(sre-engineer), Agent(cloud-architect)/analyze-prod, /bugfix, /infra-change, /deploy-productiondeployment-procedures skill (rollback procedures)development
Use this skill when running the recurring (daily) knowledge-base rescan for a repo that already has knowledge/.knowledge-sync.yml — the main-thread dispatcher that reads the config, computes the git delta since last_scanned_sha, maps changed paths to affected doc areas, early-exits cheaply when nothing changed, then fans out one Agent(content-writer) per affected area, applies the propose/direct update policy, advances the baseline only on success, and writes an L4 run log — all with the G1 untrusted-content choke-point, secret-scan, deny-list, and budget controls woven in. For first-time setup use /knowledge-sync-init.
development
Use this skill when bootstrapping scheduled knowledge-base sync for a repo that has no knowledge/.knowledge-sync.yml yet — to run one-time setup that detects the knowledge_root from CLAUDE.md/AGENTS.md, maps doc areas to source globs, records opt-in external sources (Linear/Notion/WebFetch, all disabled by default), captures a baseline last_scanned_sha, sets the per-area update policy, generates or seeds knowledge/CONVENTIONS.md, provisions the L4 memory dir, and offers to register the daily routine. Routes ongoing recurring sync operations to /knowledge-sync.
tools
Use this skill when bootstrapping a target repository to be ai-skills-aware — on the first run of any ai-skills workflow in a fresh repo, when adopting the ai-skills plugin in an existing repo, or after upgrading to a plugin version that adds new memory paths or templates, including when the user does not say "init" but asks to "set up" or "onboard" the repo — to detect codebase type, create CLAUDE.md + AGENTS.md scaffolding, initialize the .ai-skills-memory/ directory tree from L1 templates, and configure .gitignore. Idempotent — safe to re-run. Accepts `--codebase-type <type>` and `--overwrite`. Not for re-initializing only memory — use `/memory-init` instead.
tools
Use this skill when extending, repairing, or improving plugin assets, when ingesting a `/feedback` report as a fix-cycle backlog, or when you do not remember which lower-level command is right for the job — the umbrella workflow for ai-skills plugin-asset authoring and maintenance: creating, auditing, fixing, improving, refactoring, and migrating skills, agents, rules, hooks, prompts, schemas, and rubrics inside the plugin. Auto-classifies the request, loads the right knowledge skills (`@prompt-engineering`, `@context-engineering`, `@team-protocols`), and spawns the right subagents (`prompt-engineer`, `system-architect`, `python-engineer`, `software-engineer`, `qa-engineer`, `eval-judge`) via the `Agent` tool.