What is the primary purpose of the docs-review skill?

It reviews markdown documentation for adherence to specific style guides, focusing on tone, clarity, and formatting to improve technical writing quality.

What specific style elements does it check?

It audits for corporate jargon, proper UI element formatting (bold vs backticks), link descriptions, tone qualifiers like 'easy' or 'simple', and proper use of pronouns.

Can I use this skill on GitHub Pull Requests?

Yes, it features a specialized PR mode that uses the GitHub MCP tool to post structured, numbered comments as a single cohesive review on a pull request.

How does it handle local documentation files?

If GitHub tools are not available, the skill defaults to Local Review Mode, providing a numbered markdown list of issues directly in your conversation.

Why are issues numbered sequentially?

Sequential numbering is a mandatory requirement of this skill to allow users to efficiently reference and track specific feedback during the revision process.

Metabase Documentation Reviewer

Name: Metabase Documentation Reviewer
Author: Activer007

byActiver007

Learning & Documentation

Reviews documentation changes for compliance with the Metabase writing style guide and general readability standards.

About

The Metabase Documentation Reviewer skill automates the process of auditing markdown documentation against professional writing standards. It intelligently detects its environment to provide either localized feedback or a structured GitHub Pull Request review using a pending review workflow. By checking for specific patterns in tone, voice, structural clarity, and technical formatting, it ensures that documentation remains professional, accessible, and consistent across all files and contributions.

Key Features

Automated compliance checking against the Metabase style guide
Integrated GitHub pending review workflow for cohesive PR feedback
Sequential issue numbering for easy reference and tracking
Comprehensive checks for tone, voice, formatting, and technical accuracy
Intelligent environment detection for local vs. GitHub PR modes
0 GitHub stars

Use Cases

Checking local markdown files for formatting and voice consistency before committing
Performing automated style audits on documentation pull requests
Ensuring technical instructions follow established 'why-before-how' patterns

About

Key Features

Automated compliance checking against the Metabase style guide
Integrated GitHub pending review workflow for cohesive PR feedback
Sequential issue numbering for easy reference and tracking
Comprehensive checks for tone, voice, formatting, and technical accuracy
Intelligent environment detection for local vs. GitHub PR modes
0 GitHub stars

Use Cases

Checking local markdown files for formatting and voice consistency before committing
Performing automated style audits on documentation pull requests
Ensuring technical instructions follow established 'why-before-how' patterns