Skip to content
Skills Library
Security · Review & audit

cloud-security-workflow

/cloud-security-workflow

Reviews authorized cloud accounts, container images, and Kubernetes clusters with read-only Trivy, Prowler, and kubectl workflows. Use for AWS, Azure, GCP, Kubernetes, K8s, container image, cloud posture, 云安全, 云账户, 容器镜像, or 集群安全.

Author
HG-ha ↗
Repository
Argusai ↗
Licence
GPL-3.0
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Reviews authorized cloud accounts, container images, and Kubernetes clusters with read-only Trivy, Prowler, and kubectl workflows. Use for AWS, Azure, GCP, Kubernetes, K8s, container image, cloud posture, 云安全, 云账户, 容器镜像, or 集群安全.

Original author description

Reviews authorized cloud accounts, container images, and Kubernetes clusters with read-only Trivy, Prowler, and kubectl workflows. Use for AWS, Azure, GCP, Kubernetes, K8s, container image, cloud posture, 云安全, 云账户, 容器镜像, or 集群安全.

How it works

  1. Cloud Security Workflow
Original SKILL.md headings · 43 lines, 226 words
SKILL.md preview
---
name: cloud-security-workflow
description: Reviews authorized cloud accounts, container images, and Kubernetes clusters with read-only Trivy, Prowler, and kubectl workflows. Use for AWS, Azure, GCP, Kubernetes, K8s, container image, cloud posture, 云安全, 云账户, 容器镜像, or 集群安全.
trigger-keywords:
  - "\\b(cloud security|cloud posture|AWS|Azure|GCP|Prowler|Kubernetes|K8s|kubectl|container image)\\b"
  - "云安全|云账户|云配置|容器镜像|集群安全|Kubernetes安全"
trigger-tools:
  - cloud_tool_inventory
  - prowler_cloud_plan
  - kubectl_readonly_plan
---

## Cloud Security Workflow

Start from an explicit account, subscription, project, cluster context, region,
and permitted credential profile. Never infer authorization from credentials
already present on the host.

### Preflight

1. Create a Case with the matching `cloud_account`, `cluster`, or
   `container_image` target.
2. Call `cloud_tool_inventory`; use `external_tool_inventory` only when a CLI
   path/version needs diagnosis.
3. Missing tools are blockers. Do not substitute shell commands or install
   unpinned packages.
4. Record credential source by profile/context name only. Never place keys,
   tokens, kubeconfig content, or passwords in tool arguments or evidence.

### Assessment

- Container/repository/filesystem: review `trivy_cloud_plan`, then run
  `trivy_cloud_scan`. Offline mode may have stale or missing databases.
- Cloud posture: review provider, profile, regions, and check allow-list in
  `prowler_cloud_plan`; run `prowler_cloud_scan` only after confirmation.
- Kubernetes: use `kubectl_readonly_plan` before `kubectl_readonly_run`.
  Allowed operations are bounded inventory queries. Secrets, logs, exec,
  attach, port-forward, auth material, and mutation are excluded.
- IaC source must follow `iac-security-workflow`; do not confuse deployed
  posture with source configuration.

### Evidence

Preserve tool/version, account or cluster identity, region/namespace, exact
plan, report artifact, and parser limits. A scanner failure is a lead until the
affected resource and control are independently verified. Deduplicate the same
root cause across regions/resources while retaining affected instances.

### Stop conditions

Stop on ambiguous scope, unexpected account/context, expired credentials,
throttling, mutating command requirements, or output containing secrets.
Never remediate cloud resources automatically.

Versions

The database has no other skills named cloud-security-workflow.

Database snapshot: 13.11.2026 · package version e87788ddda97 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90performing-container-security-scanning-with-trivy
    Runs Trivy across every target type it supports - container images, filesystems, Git repositories, and Kubernetes clusters - for OS and dependency vulnerabilities, IaC misconfiguration, exposed secrets, and licences, generating CycloneDX or SPDX SBOMs. Use when integrating Trivy…
  • 100cloud-security-posture
    Audit and harden cloud and Kubernetes security posture - IAM, RBAC, KMS, Vault, cert-manager, OPA/Gatekeeper, Kyverno, Trivy, Falco, CIS benchmarks. Read-only audit first, then gated remediation. Use for posture reviews, compliance checks and hardening.
  • 100container-image-scanning-trivy-grype
    Use this skill when scan container images for OS and package vulnerabilities in CI/CD using Trivy and Grype.
  • 100implementing-cloud-security-posture-management
    Continuously monitor multi-cloud environments (AWS, Azure, GCP) for misconfigurations, compliance violations, and security risks using Prowler, ScoutSuite, AWS Security Hub, Microsoft Defender for Cloud, and GCP Security Command Center. Use for cross-cloud posture monitoring,…
  • 100trivy
    Expert Trivy security scanner assistance covering container image scanning, filesystem CVEs, git repositories, and IaC misconfigs. Use when scanning Docker images, auditing Kubernetes manifests, or running security checks in CI.
  • 100container-security
    Container and Kubernetes security: hardening images, runtime configuration and deployment manifests. USE WHEN: securing Docker containers, Kubernetes deployments, or reviewing container configurations DO NOT USE FOR: general Docker usage (use the `docker` skill), Kubernetes…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.