Back to Skills Marketplace
Skill pack

Cloud Ops Assistant

Inspect AWS, Azure, and Google Cloud resources, diagnose configuration issues, and prepare approval-gated cloud operations.

v0.1.0 1 skill tools By Kendr awsazuregcpcloudoperationsdiagnosticsdevops
Publisher docsHosted archive

How to use it

  1. Open Kendr Desktop.
  2. Go to Skills, then Marketplace.
  3. Search for Cloud Ops Assistant or cloud-ops-assistant.
  4. Install the pack, then enable the pack or individual skills you want available in agentic mode.

Kendr Desktop compares the installed version with the hosted catalog version and offers an update when this pack changes.

Install source

Use this hosted archive when installing or updating the pack from Kendr Desktop.

https://kendr.org/api/skills/packs/cloud-ops-assistant/archive

Cloud Ops Assistant

Safely inspect and troubleshoot AWS, Azure, and Google Cloud resources using provider MCP packs before proposing changes.

Cloud Ops Assistant

Use this skill when the user asks for cloud inventory, account or subscription summaries, resource diagnostics, service health checks, quota context, IAM review, region checks, or change preparation across AWS, Azure, or Google Cloud.

Expected companion packs:

  • AWS Official MCP for AWS documentation and account operations.
  • Azure Official MCP for Azure resource, deployment, and diagnostic workflows.
  • Google Cloud Provider MCP for gcloud, observability, and storage workflows.
  • Terraform Review Assistant when the change is infrastructure-as-code driven.

Workflow:

  • Confirm target provider, account, subscription, project, region, and environment before querying.
  • Prefer read-only inventory and diagnostics before mutation.
  • Summarize resource identity, region, status, owner tags, recent changes, health signals, and obvious misconfiguration.
  • For multi-cloud questions, keep provider-specific facts separate and normalize only at the summary layer.
  • Mark missing credentials, missing permissions, and partial results clearly.

Actions:

  • Treat create, update, delete, IAM, network, quota, DNS, billing, key, secret, deploy, and storage-write operations as side-effecting.
  • Use Kendr approval before side-effecting cloud actions.
  • Do not print credentials, keys, access tokens, connection strings, or secret resource values.