Agent skill

Author Page

by MetaMask in MetaMask/metamask-docs

Scaffold or draft new MetaMask documentation to editorial standards.

Apache-2.0Auto-check passed

Install Author Page

skills CLI
$ npx skills add MetaMask/metamask-docs --skill author-page -a claude-code

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

GitHub CLI
$ gh skill install MetaMask/metamask-docs author-page --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/author-page .claude/skills/author-page && 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/

Facts

Skill name
author-page
GitHub stars
865
Token cost
~1.7k tokens
SKILL.md length
561 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Scaffold or draft new MetaMask documentation to editorial standards.

  • Works in 5 steps: Determine conventions → Scaffold the page → Write the content → …
  • Creating a new page
  • SKILL.md covers When to use, Inputs, Step 1: Determine conventions and Step 2: Scaffold the page, plus 3 more sections
  • Calls bash and npm

What it does

Author Page is an agent skill from MetaMask/metamask-docs. Scaffold or draft new MetaMask documentation to editorial standards. Use when creating a new page, writing a first draft, or helping a non-writer meet the documentation team's expectations.

Its SKILL.md is about 1.7k 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.

When your agent uses it

  • Creating a new page
  • Writing a first draft
  • Helping a non-writer meet the documentation teams expectations

Example prompts

  • “/author-page”

Workflow steps

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

  1. Determine conventions
  2. Scaffold the page
  3. Write the content
  4. Verify the file is complete
  5. Remind the contributor

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

    Shell commands in SKILL.md call:

    • bash
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.infura.io

    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

Author Page loads about 1.7k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 561 words of instructions outside code blocks.

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

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). 561 words, ~1,671 tokens.

Download SKILL.mdSave it as .claude/skills/author-page/SKILL.md (or your agent's skills folder).
name
author-page
description
Scaffold or draft new MetaMask documentation to editorial standards. Use when creating a new page, writing a first draft, or helping a non-writer meet the documentation team's expectations.

Author a new documentation page

Help create a new documentation page that follows MetaMask editorial standards from the start.

When to use

  • You need to scaffold a new page or write a first draft.
  • You are helping someone who is not a writer produce content that meets team expectations.

Inputs

Ask the user for any information they have not already provided:

  1. Product area - which product is this for? (MetaMask Connect, Embedded Wallets, Smart Accounts Kit, Agent Wallet, Snaps). Infura API and dashboard docs live at Infura documentation and are not authored in this repository.
  2. Content type - what kind of page? (concept/explanation, how-to guide, quickstart, reference, tutorial, troubleshooting)
  3. Topic - what is the page about?
  4. File path - where should the file live? (Suggest one based on product and content type if the user doesn't specify.)

Step 1: Determine conventions

Based on the product and content type, load the relevant rules:

  • .cursor/rules/content-types.mdc - structural expectations for the content type.
  • .cursor/rules/product-*.mdc - product-specific terminology and conventions.
  • .cursor/rules/editorial-voice.mdc - tone and voice.
  • .cursor/rules/markdown-formatting.mdc - formatting conventions.
  • .cursor/rules/terminology.mdc - required terms and casing.

Check how existing pages in the same folder are structured. Match their conventions for headings, front-matter fields, intro style, and parameter formats.

Step 2: Scaffold the page

Create the file with the correct structure for its content type.

Page metadata

Follow page metadata rules in .cursor/rules/markdown-formatting.mdc (required description, recommended keywords, optional sidebar_label only when the nav label would otherwise be too long or wordy, and the title vs duplicate H1 rule). Do not repeat or contradict that rule here.

Structure by content type

Concept / Explanation (for concepts/ or learn/ folders):

markdown
---
description: <one sentence>
---

# <Topic name>

<Opening paragraph: what this is and why it matters. 2-3 sentences. Get to the point.>

## <First concept section>

<Explain the concept. No step-by-step instructions.>

## <Second concept section>

...

## Next steps

- [<Related how-to guide>](<relative link>)
- [<Related reference>](<relative link>)

How-to guide (for guides/ or how-to/ folders):

markdown
---
description: <one sentence>
---

# <Action-oriented title: "Send a transaction" not "Sending transactions">

<Opening paragraph: what the reader will accomplish. 1-2 sentences.>

## Prerequisites

- <Requirement 1>
- <Requirement 2>

## Steps

### 1. <First action>

<Instruction. One action per step.>

### 2. <Second action>

...

## Next steps

- [<Related content>](link)

Quickstart (for quickstart/ or get-started/ folders):

markdown
---
description: <one sentence>
---

# <What the reader will build or achieve>

<Opening paragraph: what the reader will have at the end. 1-2 sentences.>

## Prerequisites

- <Requirement>

## Steps

### 1. <First step>

<Complete, copy-paste-ready code.>

### 2. <Second step>

...

## Next steps

- [<Extend this with a how-to guide>](link)

Reference (for reference/ folders):

markdown
---
description: <one sentence>
---

# <API or method name>

<One sentence describing what the method or API does.>

## Parameters

<Match the parameter format used in surrounding reference pages in the same product. Use tables
or nested bulleted lists depending on the established convention.>

## Returns

<Describe the return value.>

## Example

<Working code example.>

Tutorial (for tutorials/ folders):

markdown
---
description: <one sentence>
---

# <What the reader will learn>

<Opening paragraph: what the reader will build, what they will learn, and why it matters.
2-3 sentences.>

## Prerequisites

- <Requirement - assume no prior knowledge>

## Steps

### 1. <First step>

<Explain every step. Include expected output.>

...

## Complete code

<Full working code sample the reader can download or copy.>

## Next steps

- [<More advanced guide>](link)

Troubleshooting (for troubleshooting/ folders):

markdown
---
description: <one sentence>
---

# <Symptom or error message>

## Problem

<Describe the symptom. Include the exact error text if available.>

## Solution

<Steps to fix the issue.>
Show full SKILL.md (270 more words)Show less

Step 3: Write the content

Fill in the scaffold with content based on what the user provides. Follow these rules:

  • Voice: active, present tense, second person ("you"). Use contractions where appropriate.
  • First sentence: get to the point. Answer "what" or "why" immediately.
  • No em/en dashes: use commas, parentheses, or semicolons.
  • Sentence case for all headings.
  • One sentence per line, wrapped at about 100 columns.
  • Code blocks: always include a language tag. Use bash npm2yarn for install commands.
  • Terminology: use the required forms from terminology.mdc.
  • No marketing language: no "powerful," "seamless," "best-in-class."
  • No invented API behavior: if you are not certain about a parameter, return value, or behavior, add a :::note admonition flagging it for review rather than stating it as fact.

Step 4: Verify the file is complete

Before finishing, check:

  • Page metadata includes description; add sidebar_label only when the default nav label would be too long or wordy (see markdown-formatting.mdc).
  • Opening paragraph answers "what" and "why" in the first 1-2 sentences.
  • Structure matches the content type.
  • Terminology matches terminology.mdc and the product rule file.
  • Code blocks have language tags.
  • No em dashes, en dashes, or marketing language.
  • File name uses lowercase and dashes (send-transactions.md, not sendTransactions.md).
  • File is placed in the correct product and content-type folder.

Step 5: Remind the contributor

After creating the page, remind the user to:

  1. Add the page to the correct sidebar file (see contributor-workflow.mdc for the mapping).
  2. If any page was moved, renamed, or removed in the same change set, add redirects in vercel.json (see contributor-workflow.mdc).
  3. Preview locally with npm start.
  4. Check that the CI linter passes before requesting review.

© MetaMask, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/author-page of MetaMask/metamask-docs.

Open the folder on GitHubat commit 8be8eb9

Compare with similar skills

Author Page 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.

Author Page compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Author Page this skillMetaMask/metamask-docs865—~1.7kAutomated safety check: PassApache-2.0
Wagmi Feature Developmentwevm/wagmi6.8k—~3.8kAutomated safety check: PassMIT
Release Roundethereumjs/ethereumjs-monorepo2.8k—~2kAutomated safety check: PassNone
Update Est Fixturesethereumjs/ethereumjs-monorepo2.8k—~3.3kAutomated safety check: PassNone
Swapper Depositswapperfinance/swapper-toolkit852—~1.8kAutomated safety check: PassMIT
BNB Chain MCP Serverinternet-court/internet-court-skill6.5k1 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • 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 8 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 21 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 21 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.5k 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 22 days ago
    Business, Finance & HRAuto-check passed

More from MetaMask/metamask-docs

  • Style Review

    MetaMask/metamask-docs

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

    865 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed

Works with

Questions about Author Page

What does Author Page do?

Scaffold or draft new MetaMask documentation to editorial standards. Author Page is an agent skill from MetaMask/metamask-docs. Scaffold or draft new MetaMask documentation to editorial standards.

When should I use Author Page?

Author Page fits situations like: creating a new page; writing a first draft; helping a non-writer meet the documentation teams expectations.

How do I install Author Page in Claude Code?

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

How do I install Author Page in Codex?

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

Can I use Author Page 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 author-page -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/author-page, .gemini/skills/author-page, .github/skills/author-page and .opencode/skills/author-page in your project.

What does Author Page need to run?

Going by SKILL.md and its folder, Author Page needs the command-line tools its instructions call (bash and npm).

Does Author Page access the network?

SKILL.md names 1 domain. As links in the text: docs.infura.io. This is read from the text; nothing was executed.

Is Author Page 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 Author Page use?

Author Page 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 Author Page use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 Author Page?

Skills that share tags, products or a category with Author Page: 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 Author Page?

MetaMask (a GitHub organization) maintains it in MetaMask/metamask-docs, which has 865 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.