prowler-docs

Enforce Prowler documentation style guide and writing standards.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill prowler-docs-brivaro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prowler-docs
Source: https://github.com/brivaro/brivaro-ai-wizard/tree/main/skills/prowler-docs
Command: npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill prowler-docs-brivaro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive style guide and set of standards for writing documentation related to Prowler features, ensuring consistency, clarity, and adherence to best practices.

Core Features & Use Cases

  • Style Guide: Defines brand voice, technical terminology, and formatting standards.
  • SEO Optimization: Offers guidance on structuring content for better searchability.
  • Component Usage: Demonstrates how to use MDX components for version badges, warnings, and danger calls.
  • Use Case: When tasked with writing a new tutorial for a Prowler feature, this skill ensures the documentation follows established guidelines for clarity and discoverability.

Quick Start

Use the prowler-docs skill to review the brand voice guidelines for Prowler documentation.

Frequently Asked Questions about prowler-docs

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

FAQPage Schema
What are the documentation style guide standards for writing Prowler technical tutorials?

Documentation standards for Prowler technical writing enforce unbiased communication, specific technical terminology, title case formatting, and proper hyphenation to ensure clarity and consistency across features and tutorials.

How do I use MDX components for warnings and version badges in technical documentation?

MDX components for warnings and version badges are used in technical documentation by following specific formatting standards that structure content for discoverability and clear user guidance within the documentation framework.

How do I optimize technical writing content for SEO in developer guides?

SEO optimization for technical writing content involves structuring guides with standardized formatting, unbiased communication, and proper technical terminology to improve searchability and content discoverability for users.

Does the Prowler documentation style guide cover brand voice and technical terminology formatting?

Yes, the Prowler documentation style guide defines brand voice standards, technical terminology usage, and formatting rules including title case and hyphenation to maintain consistency across all feature documentation.

What is the best way to ensure consistent writing standards across feature documentation?

The best way to ensure consistent writing standards across feature documentation is to apply a comprehensive style guide covering brand voice, formatting standards, and MDX component usage to maintain clarity and adherence to best practices.

When do I need to follow unbiased communication guidelines in technical writing?

Unbiased communication guidelines in technical writing must be followed whenever creating Prowler features, tutorials, or guides to ensure content adheres to established documentation standards and maintains neutral, clear language.