prowler-sdk-check

Scaffold Prowler SDK checks with standard file layout and metadata frontmatter.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/adbertram/Devolutions-CIEM --skill prowler-sdk-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prowler-sdk-check
Source: https://github.com/adbertram/Devolutions-CIEM/tree/main/prowler/skills/prowler-sdk-check
Command: npx skills add https://github.com/adbertram/Devolutions-CIEM --skill prowler-sdk-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill automates the scaffolding of Prowler SDK checks and their metadata, enabling teams to bootstrap checks quickly with consistent structure and documentation.

Core Features & Use Cases

  • SDK-aligned scaffolding: Creates the standard provider/service/resource folder, check script, and metadata JSON.
  • Metadata consistency: Ensures the frontmatter includes a valid name, description, license, and version metadata for discoverability.
  • Use Case: When adding a new security check (AWS, Azure, GCP, Kubernetes, etc.), this Skill provides the boilerplate and references to connect with prowler-cli workflows.

Quick Start

Create a new Prowler SDK check by following the Step-by-Step Creation Process documented in SKILL.md, including file paths and metadata fields.

Frequently Asked Questions about prowler-sdk-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Prowler SDK security check across different cloud providers?

To create a Prowler SDK security check, this Skill automates scaffolding the standard provider/service/check folder structure, check script, and metadata JSON for rapid, consistent security check creation across AWS, Azure, GCP, and Kubernetes.

What metadata is required when adding a custom check to the Prowler SDK?

The required frontmatter metadata for a custom Prowler SDK check includes a valid name, description, license, and version to ensure proper discoverability and seamless integration with prowler-cli workflows.

Can I use this scaffolding tool for Kubernetes and GitHub security checks, or is it limited to AWS?

You can use this scaffolding tool for Kubernetes and GitHub security checks, as it targets developers implementing new checks across multiple providers including AWS, Azure, GCP, Kubernetes, and GitHub.

What is the standard file layout for a Prowler SDK check?

The standard file layout for a Prowler SDK check follows a provider/service/check directory structure alongside its corresponding metadata JSON file to enforce consistency and enable seamless discovery.

Why do I need to scaffold metadata for Prowler cloud security checks?

Scaffolding metadata for Prowler cloud security checks enforces consistent frontmatter like name, description, license, and version, which ensures seamless discovery and integration of new checks across providers.