Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 18% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 7% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 61% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -7% | 0% |
Use this skill when writing Prowler documentation for:
Use Title Case for all headers:
Use when information can be logically divided:
markdownProwler CLI includes: * **Industry standards:** CIS, NIST 800, NIST CSF * **Regulatory compliance:** RBI, FedRAMP, PCI-DSS * **Privacy frameworks:** GDPR, HIPAA, FFIEC
Place keywords at the beginning:
mdximport { VersionBadge } from "/snippets/version-badge.mdx" ## New Feature Name <VersionBadge version="4.5.0" /> Description of the feature...
mdx<Warning> Disabling encryption may expose sensitive data to unauthorized access. </Warning> <Danger> Running this command will **permanently delete all data**. </Danger>
Reference without articles:
docs/
├── getting-started/
├── tutorials/
├── providers/
│ ├── aws/
│ ├── azure/
│ ├── gcp/
│ └── ...
├── api/
├── sdk/
├── compliance/
└── developer-guide/Other measured skills in the registry, with their headline benchmark lift.