agentsclimarketplace

Cloud architect

Skill ldilov/harness-forge/skills/cloud-architect

AI coding agent runtime that makes LLMs understand your codebase with repository-aware context, memory, and continuous learning

Install
npx -y skills add ldilov/harness-forge --skill cloud-architect

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

  • 3 stars3 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

Cloud architecture guidance for platform design, deployment topology, reliability, security, observability, and cost trade-offs.

SKILL.md

2.7 KB, as published. Nobody here has run it

Cloud Architect

Use this skill when the task is dominated by platform shape rather than a single code path: cloud topology, deployment design, distributed systems behavior, reliability, migration planning, security posture, observability, or cost.

Trigger Signals

  • the task mentions AWS, Azure, GCP, Kubernetes, Terraform, containers, or platform architecture
  • the change spans multiple services, environments, or deployment stages
  • reliability, security, latency, observability, or cost trade-offs are first-class concerns

Inspect First

  • infrastructure and deployment definitions
  • runtime configuration, environment boundaries, and secret handling
  • service topology, dependencies, and data or event flows
  • existing observability, SLO, reliability, and incident surfaces

Workflow

  1. map the current topology, ownership boundaries, and runtime dependencies
  2. identify the highest-risk architectural seams before proposing change
  3. compare the repository's current patterns against the closest stable reference pattern
  4. recommend the smallest architecture move that improves reliability, clarity, or operability
  5. define validation, rollout, and rollback expectations before implementation handoff

Output Contract

  • architecture summary with current state and proposed direction
  • trade-off notes covering reliability, security, observability, and cost
  • rollout or validation guidance with concrete follow-up checks

Failure Modes

  • stop when the current topology cannot be inferred from repository evidence
  • stop when compliance, tenancy, or secret-management assumptions would materially change the recommendation
  • stop when the task is really a single-service code change and should stay with a language skill

Escalation

  • escalate when cloud-provider constraints, compliance rules, or budget targets are missing
  • escalate when migration risk crosses team or service ownership boundaries
  • escalate when rollout and rollback expectations are undefined for a production-critical path

Supplemental References

  • skills/cloud-architect/references/repo-exploration.md
  • skills/cloud-architect/references/output-templates.md
  • skills/cloud-architect/references/agent-patterns.md
  • skills/cloud-architect/references/debugging-playbook.md
  • skills/cloud-architect/references/distributed-systems.md
  • skills/cloud-architect/references/platform-and-deployment.md
  • skills/cloud-architect/references/reliability-security-cost.md
  • skills/cloud-architect/references/examples.md

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.