prowler-cloud/prowler

prowler-docs

Prowler documentation style guide and writing standards.

First seen Jan 21, 2026

Installation

$ npx skills add prowler-cloud/prowler --skill prowler-docs

Also in this package

Other skills from prowler-cloud/prowler · top by installs.

npx skills add prowler-cloud/prowler

Browse all from prowler-cloud/prowler

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 14.8K
License LICENSE
Default branch master
Open issues 142
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0
LicenseApache-2.0
Allowed toolsRead, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
More metadata
author
prowler-cloud
version
1.0
scope
["root"]
auto_invoke
Writing documentation

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,157 B
  • docs SUMMARY.md 156 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 67 installs

SKILL.md

When to Use

Use this skill when writing Prowler documentation for:

  • Feature documentation
  • API/SDK references
  • Tutorials and guides
  • Release notes

Brand Voice

Unbiased Communication

  • Avoid gendered pronouns (use "you/your" or "they/them")
  • Use inclusive alternatives: businessman → businessperson, mankind → humanity
  • No generalizations about gender, race, nationality, culture
  • Avoid militaristic language: fight → address, kill chain → cyberattack chain

Technical Terminology

  • Define key terms and acronyms on first use: "Identity and Access Management (IAM)"
  • Prefer verbal over nominal constructions: "The report was created" not "The creation of the report"
  • Use clear, accessible language; minimize jargon

Formatting Standards

Title Case Capitalization

Use Title Case for all headers:

  • Good: "How to Configure Security Scanning"
  • Bad: "How to configure security scanning"

Hyphenation

  • Prenominal position: "world-leading company"
  • Postnominal position: "features built in"

Bullet Points

Use when information can be logically divided:

Prowler CLI includes:
* **Industry standards:** CIS, NIST 800, NIST CSF
* **Regulatory compliance:** RBI, FedRAMP, PCI-DSS
* **Privacy frameworks:** GDPR, HIPAA, FFIEC

Interaction Verbs

  • Desktop: Click, Double-click, Right-click, Drag, Scroll
  • Touch: Tap, Double-tap, Press and hold, Swipe, Pinch

SEO Optimization

Sentence Structure

Place keywords at the beginning:

  • Good: "To create a custom role, open a terminal..."
  • Bad: "Open a terminal to create a custom role..."

Headers

  • H1: Primary (unique, descriptive)
  • H2-H6: Subheadings (logical hierarchy)
  • Include keywords naturally

MDX Components

Version Badge

import { VersionBadge } from "/snippets/version-badge.mdx"

## New Feature Name

<VersionBadge version="4.5.0" />

Description of the feature...

Warnings and Danger Calls

<Warning>
Disabling encryption may expose sensitive data to unauthorized access.
</Warning>

<Danger>
Running this command will **permanently delete all data**.
</Danger>

Prowler Features (Proper Nouns)

Reference without articles:

  • Prowler App, Prowler CLI, Prowler SDK
  • Prowler Cloud, Prowler Studio, Prowler Registry
  • Built-in Compliance Checks
  • Multi-cloud Security Scanning
  • Autonomous Cloud Security Analyst (AI)

Documentation Structure

docs/
├── getting-started/
├── tutorials/
├── providers/
│   ├── aws/
│   ├── azure/
│   ├── gcp/
│   └── ...
├── api/
├── sdk/
├── compliance/
└── developer-guide/

Resources

  • Documentation: See [references/](references/) for links to local developer guide