Agent skill

Style Review

Review MetaMask documentation for editorial compliance (voice, terminology, formatting, content type, frontmatter, workflow).

Apache-2.0Auto-check passed

Install Style Review

skills CLI

$ npx skills add MetaMask/metamask-docs --skill style-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install MetaMask/metamask-docs style-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/MetaMask/metamask-docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/style-review .claude/skills/style-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "style-review" agent skill from https://github.com/MetaMask/metamask-docs/tree/main/.cursor/skills/style-review into .claude/skills/style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-review", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/MetaMask/metamask-docs/tree/main/.cursor/skills/style-review

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add MetaMask/metamask-docs --skill style-review -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install MetaMask/metamask-docs style-review --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MetaMask/metamask-docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/style-review .agents/skills/style-review && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "style-review" agent skill from https://github.com/MetaMask/metamask-docs/tree/main/.cursor/skills/style-review into .agents/skills/style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-review", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add MetaMask/metamask-docs --skill style-review -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install MetaMask/metamask-docs style-review --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MetaMask/metamask-docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/style-review .cursor/skills/style-review && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "style-review" agent skill from https://github.com/MetaMask/metamask-docs/tree/main/.cursor/skills/style-review into .cursor/skills/style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-review", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/MetaMask/metamask-docs.git --path .cursor/skills/style-review

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add MetaMask/metamask-docs --skill style-review -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install MetaMask/metamask-docs style-review --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MetaMask/metamask-docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/style-review .gemini/skills/style-review && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "style-review" agent skill from https://github.com/MetaMask/metamask-docs/tree/main/.cursor/skills/style-review into .gemini/skills/style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-review", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install MetaMask/metamask-docs style-review

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add MetaMask/metamask-docs --skill style-review -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/MetaMask/metamask-docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/style-review .github/skills/style-review && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "style-review" agent skill from https://github.com/MetaMask/metamask-docs/tree/main/.cursor/skills/style-review into .github/skills/style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-review", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add MetaMask/metamask-docs --skill style-review -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install MetaMask/metamask-docs style-review --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MetaMask/metamask-docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/style-review .opencode/skills/style-review && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "style-review" agent skill from https://github.com/MetaMask/metamask-docs/tree/main/.cursor/skills/style-review into .opencode/skills/style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-review", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: style-review
GitHub stars: 864
Token cost: ~1.2k tokens
SKILL.md length: 551 words
Files: 1
Skills in repo: 2
Repo updated: Sep 24, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Review MetaMask documentation for editorial compliance (voice, terminology, formatting, content type, frontmatter, workflow).

Works in 4 steps: Identify the product and content type → Run Vale (if available) → Review against editorial rules → …
SKILL.md covers When to use, Inputs, Step 1: Identify the product… and Step 2: Run Vale (if available), plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Style Review is an agent skill from MetaMask/metamask-docs. Review MetaMask documentation for editorial compliance (voice, terminology, formatting, content type, frontmatter, workflow). Use before submitting a PR or when asked to audit existing pages.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Ethereum. The repository describes itself as: Developer documentation for MetaMask. The licence is Apache-2.0.

Example prompts

“/style-review”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Identify the product and content type
Run Vale (if available)
Review against editorial rules
Generate the report

What it can do on your machine

Read from SKILL.md and the folder at commit 8be8eb9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Style Review loads about 1.2k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 551 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~51
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MetaMask/metamask-docs at commit 8be8eb9, republished under its Apache-2.0 licence (© MetaMask). 551 words, ~1,236 tokens.

Download SKILL.mdSave it as .claude/skills/style-review/SKILL.md (or your agent's skills folder).

name: style-review
description: Review MetaMask documentation for editorial compliance (voice, terminology, formatting, content type, frontmatter, workflow). Use before submitting a PR or when asked to audit existing pages.

Style review

When to use

You want to check existing content for style, terminology, formatting, or content-type issues.
You are preparing to submit a PR and want a structured editorial pass.

Inputs

The user provides a file path or directory to review. If not provided, ask what to review.

Step 1: Identify the product and content type

Read the file path to determine:

Product area - which product folder the file lives in (for example, metamask-connect/, snaps/, agent-wallet/). Load the corresponding product rule from .cursor/rules/product-*.mdc. For Infura content, use .cursor/rules/product-infura.mdc and link to Infura documentation.
Content type - which folder determines the expected structure (for example, concepts/, how-to/, reference/). Use .cursor/rules/content-types.mdc for the mapping.

Step 2: Run Vale (if available)

Try running Vale on the target file:

bash

vale <file-or-directory>

If Vale is not installed, skip this step and note it in the report. Continue with the manual review.

Step 3: Review against editorial rules

Read the file fully. The following points are quick reminders; use the linked .mdc files as the source of truth for full criteria, examples, and edge cases.

Voice and tone (editorial-voice.mdc)

Active voice and present tense used throughout.
Second person ("you"), not "the developer" or "users."
Contractions used where appropriate.
No marketing language, superlatives, or promotional tone.
No em dashes or en dashes; use commas, parentheses, or semicolons.
First sentence of each section gets to the point.
No slang, figures of speech, or culturally specific idioms.

Terminology (terminology.mdc)

Product names match the required forms (dapp, MetaMask, smart account, web3, etc.).
Standards spelled out on first use with identifier in parentheses (for example, "Chain Agnostic Improvement Proposal 25 (CAIP-25)"), short form on subsequent references.
Product-specific terminology matches the corresponding product-*.mdc rule file.

Markdown formatting (`markdown-formatting.mdc`)

Lines wrapped at about 100 columns.
Each sentence on its own line.
Code blocks have a language tag.
Links use relative paths within the product, absolute paths across products.
Descriptive link text; no "click here" or bare URLs.
Admonitions use Docusaurus syntax and are not nested.
Tables are aligned in source Markdown.
No duplicate H1 if page metadata contains a title field.

Show full SKILL.md (203 more words)Show less

Content type compliance (content-types.mdc)

Page structure matches the expected content type for its folder.
Concept pages: no step-by-step instructions, ends with "Next steps."
How-to pages: goal stated first, prerequisites listed, numbered steps.
Reference pages: parameter format matches surrounding pages in the same product section.
Quickstart pages: complete, copy-paste-and-run code.
Troubleshooting pages: symptom/error first, then fix.

Page metadata

description field present (one sentence for SEO).
sidebar_label only when needed (default nav label would be too long or wordy); otherwise omit.
No duplicate H1 if title is set in page metadata.

Contributor workflow (contributor-workflow.mdc)

If the file is new, verify it has been added to the correct sidebar file.
If the file was moved or renamed, verify a redirect exists in vercel.json.
Cross-product links use absolute URL paths.

Step 4: Generate the report

Present findings as a structured report grouped by category. For each issue:

Line number - approximate location in the file.
Category - Voice/Tone, Terminology, Formatting, Content Type, Page metadata, or Workflow.
Issue - what is wrong.
Suggestion - how to fix it.

Report format

## Style review: <file>

### Product: <product name> | Content type: <type>

### Summary
- X issues found (Y from Vale, Z from manual review)
- Severity: A critical, B suggestions

### Voice and tone
- Line 12: Passive voice - "The block number can be specified..." → "Specify the block number..."

### Terminology
- Line 8: "smart contract account" → Use "smart account" per terminology.mdc.

### Formatting
- Line 45: Code block missing language tag.
- Line 22: Em dash found - replace with comma or period.

### Content type
- Page is in `concepts/` but contains numbered step-by-step instructions. Move steps to a
  how-to page and link to it.

### Page metadata
- Missing `description` field.

If reviewing a directory, produce one report per file, then a summary at the end showing totals across all files.

If no issues are found, say so explicitly.

Files

Just SKILL.md in .cursor/skills/style-review of MetaMask/metamask-docs.

Open the folder on GitHubat commit 8be8eb9

Compare with similar skills

Style Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Style Review compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Style Review this skillMetaMask/metamask-docs	864	—	~1.2k	Automated safety check: Pass	Apache-2.0	16 days ago
Wagmi Feature Developmentwevm/wagmi	6.8k	—	~3.8k	Automated safety check: Pass	MIT	9 days ago
Release Roundethereumjs/ethereumjs-monorepo	2.8k	—	~2k	Automated safety check: Pass	None	22 days ago
Update Est Fixturesethereumjs/ethereumjs-monorepo	2.8k	—	~3.3k	Automated safety check: Pass	None	22 days ago
Swapper Depositswapperfinance/swapper-toolkit	852	—	~1.8k	Automated safety check: Pass	MIT	6 mo ago
BNB Chain MCP Serverinternet-court/internet-court-skill	6.6k	1 repos	~1.7k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Wagmi Feature Development
wevm/wagmi
Walks through adding a Wagmi feature across its layers: a Viem-based core action, TanStack Query options, and React and Vue bindings.
6.8k GitHub stars~3.8k tokensUpdated 9 days ago
DevelopmentAuto-check passed
Release Round
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
2.8k GitHub stars~2k tokensUpdated 22 days ago
DevelopmentAuto-check passed
Update Est Fixtures
ethereumjs/ethereumjs-monorepo
Updates EthereumJS execution-spec test fixtures from an ethereum/execution-specs release, then (after a human merge) points the monorepo submodule, updates VM npm scripts, reports a first test run…
2.8k GitHub stars~3.3k tokensUpdated 22 days ago
DevelopmentAuto-check passed
Swapper Deposit
swapperfinance/swapper-toolkit
Deposit and bridge funds into a wallet or protocol using Swapper Finance.
852 GitHub stars~1.8k tokensUpdated 6 mo ago
Business, Finance & HRAuto-check passed
BNB Chain MCP Server
internet-court/internet-court-skill
Connects an agent to the BNB Chain MCP server to read blocks and contracts, move tokens and NFTs, register ERC-8004 agents and use Greenfield storage.
6.6k GitHub starsUsed in 1 repo~1.7k tokens
Agent WorkflowsAuto-check passed
Minara Crypto Trading and Wallet
Minara-AI/minara-skills
Drives the Minara CLI for crypto swaps, perps, limit orders, wallet transfers, deposits and withdrawals, plus AI market analysis.
362 GitHub stars~5.7k tokensUpdated 23 days ago
Business, Finance & HRAuto-check passed

Questions about Style Review

What does Style Review do?

Review MetaMask documentation for editorial compliance (voice, terminology, formatting, content type, frontmatter, workflow). Style Review is an agent skill from MetaMask/metamask-docs. Review MetaMask documentation for editorial compliance (voice, terminology, formatting, content type, frontmatter, workflow).

How do I install Style Review in Claude Code?

Run `npx skills add MetaMask/metamask-docs --skill style-review -a claude-code`. Or copy the skill folder (.cursor/skills/style-review in MetaMask/metamask-docs) into .claude/skills/style-review in your project. Claude Code loads it when a task matches its description.

How do I install Style Review in Codex?

Run `npx skills add MetaMask/metamask-docs --skill style-review -a codex`. Or copy the skill folder (.cursor/skills/style-review in MetaMask/metamask-docs) into .agents/skills/style-review in your project. Codex loads it when a task matches its description.

Can I use Style Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MetaMask/metamask-docs --skill style-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/style-review, .gemini/skills/style-review, .github/skills/style-review and .opencode/skills/style-review in your project.

What does Style Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Style Review is instructions for the agent only.

Does Style Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Style Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Style Review use?

Style Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Style Review use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Style Review?

Skills that share tags, products or a category with Style Review: Wagmi Feature Development (wevm/wagmi, 6.8k stars), Release Round (ethereumjs/ethereumjs-monorepo, 2.8k stars), Update Est Fixtures (ethereumjs/ethereumjs-monorepo, 2.8k stars) and Swapper Deposit (swapperfinance/swapper-toolkit, 852 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Style Review?

MetaMask (a GitHub organization) maintains it in MetaMask/metamask-docs, which has 864 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 24, 2026.

Source: MetaMask/metamask-docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Style Review

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Style review

When to use

Inputs

Step 1: Identify the product and content type

Step 2: Run Vale (if available)

Step 3: Review against editorial rules

Voice and tone (editorial-voice.mdc)

Terminology (terminology.mdc)

Markdown formatting (markdown-formatting.mdc)

Content type compliance (content-types.mdc)

Page metadata

Contributor workflow (contributor-workflow.mdc)

Step 4: Generate the report

Report format

Files

Compare with similar skills

Similar skills

Wagmi Feature Development

Release Round

Update Est Fixtures

Swapper Deposit

BNB Chain MCP Server

Minara Crypto Trading and Wallet

More from MetaMask/metamask-docs

Author Page

Related

Questions about Style Review

Markdown formatting (`markdown-formatting.mdc`)