Agent skill

MCP Documentation Standard

Create or update Patsnap MCP catalog documentation in this repository.

Apache-2.0Auto-check passedAgent Workflows

Install MCP Documentation Standard

skills CLI

$ npx skills add patsnap/mcp --skill mcp-documentation-standard -a claude-code

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

GitHub CLI

$ gh skill install patsnap/mcp mcp-documentation-standard --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/patsnap/mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/mcp-documentation-standard .claude/skills/mcp-documentation-standard && 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 "mcp-documentation-standard" agent skill from https://github.com/patsnap/mcp/tree/main/.agents/skills/mcp-documentation-standard into .claude/skills/mcp-documentation-standard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-documentation-standard", 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/patsnap/mcp/tree/main/.agents/skills/mcp-documentation-standard

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 patsnap/mcp --skill mcp-documentation-standard -a codex

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

GitHub CLI

$ gh skill install patsnap/mcp mcp-documentation-standard --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/patsnap/mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/mcp-documentation-standard .agents/skills/mcp-documentation-standard && 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 "mcp-documentation-standard" agent skill from https://github.com/patsnap/mcp/tree/main/.agents/skills/mcp-documentation-standard into .agents/skills/mcp-documentation-standard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-documentation-standard", 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 patsnap/mcp --skill mcp-documentation-standard -a cursor

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

GitHub CLI

$ gh skill install patsnap/mcp mcp-documentation-standard --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/patsnap/mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/mcp-documentation-standard .cursor/skills/mcp-documentation-standard && 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 "mcp-documentation-standard" agent skill from https://github.com/patsnap/mcp/tree/main/.agents/skills/mcp-documentation-standard into .cursor/skills/mcp-documentation-standard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-documentation-standard", 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/patsnap/mcp.git --path .agents/skills/mcp-documentation-standard

--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 patsnap/mcp --skill mcp-documentation-standard -a gemini-cli

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

GitHub CLI

$ gh skill install patsnap/mcp mcp-documentation-standard --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/patsnap/mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/mcp-documentation-standard .gemini/skills/mcp-documentation-standard && 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 "mcp-documentation-standard" agent skill from https://github.com/patsnap/mcp/tree/main/.agents/skills/mcp-documentation-standard into .gemini/skills/mcp-documentation-standard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-documentation-standard", 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 patsnap/mcp mcp-documentation-standard

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 patsnap/mcp --skill mcp-documentation-standard -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/patsnap/mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/mcp-documentation-standard .github/skills/mcp-documentation-standard && 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 "mcp-documentation-standard" agent skill from https://github.com/patsnap/mcp/tree/main/.agents/skills/mcp-documentation-standard into .github/skills/mcp-documentation-standard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-documentation-standard", 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 patsnap/mcp --skill mcp-documentation-standard -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 patsnap/mcp mcp-documentation-standard --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/patsnap/mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/mcp-documentation-standard .opencode/skills/mcp-documentation-standard && 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 "mcp-documentation-standard" agent skill from https://github.com/patsnap/mcp/tree/main/.agents/skills/mcp-documentation-standard into .opencode/skills/mcp-documentation-standard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-documentation-standard", 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: mcp-documentation-standard
GitHub stars: 113
Token cost: ~1.2k tokens
SKILL.md length: 599 words
Files: 3 (incl. references)
Skills in repo: 32
Repo updated: Aug 20, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Create or update Patsnap MCP catalog documentation in this repository.

Works in 6 steps: Collect authoritative Marketplace facts → Choose the destination → Write the server README → …
Adding a Marketplace MCP server
SKILL.md covers Required outcome, 1. Collect authoritative…, 2. Choose the destination and 3. Write the server README, plus 3 more sections
Calls git

What it does

MCP Documentation Standard is an agent skill from patsnap/mcp. Create or update Patsnap MCP catalog documentation in this repository. Use when adding a Marketplace MCP server, refreshing its README or service SKILL, classifying it under ip-intelligence, life-sciences, or rd-innovation, or updating the repository README and Glama indexes.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/templates.md`).

It sits in Agent Workflows, covering MCP servers, Technical documentation and Intellectual property. It works with Model Context Protocol. The repository describes itself as: MCP server for 200M+ patents, scientific literature, chemistry and pharma records. Search prior art and R&D intelligence powered by PatSnap's proprietary databases via Claude… The licence is Apache-2.0.

When your agent uses it

Adding a Marketplace MCP server
Refreshing its README
Classifying it under ip-intelligence
Updating the repository README and Glama indexes

Example prompts

“/mcp-documentation-standard”

Requirements

A credential in YOUR_API_KEY

Workflow steps

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

Collect authoritative Marketplace facts
Choose the destination
Write the server README
Write the service SKILL
Update discovery indexes
Verify before handoff

What it can do on your machine

Read from SKILL.md and the folder at commit 7a4b429. 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:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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

MCP Documentation Standard loads about 1.2k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 599 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.1k

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 patsnap/mcp at commit 7a4b429, republished under its Apache-2.0 licence (© patsnap). 599 words, ~1,240 tokens.

Download SKILL.mdSave it as .claude/skills/mcp-documentation-standard/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: mcp-documentation-standard
description: Create or update Patsnap MCP catalog documentation in this repository. Use when adding a Marketplace MCP server, refreshing its README or service SKILL, classifying it under ip-intelligence, life-sciences, or rd-innovation, or updating the repository README and Glama indexes.

MCP Documentation Standard

Use this workflow to turn a Patsnap Marketplace MCP detail page into consistent, reviewable repository documentation.

Required outcome

For every MCP server, create or update these files in its business-domain directory:

<category>/<server-directory>/README.md
<category>/<server-directory>/SKILL.md

Then update all applicable indexes:

/README.md
/<category>/README.md
/glama.json

Do not create a business-server skill under .agents/skills. This skill is the reusable documentation standard; each MCP's own SKILL.md belongs beside that MCP's README.md.

Read references/templates.md before writing or reviewing MCP documentation.

1. Collect authoritative Marketplace facts

Open the exact MCP detail page and record:

Marketplace slug, displayed product name, provider, lifecycle state, and version
product purpose and stated data coverage
endpoint URL, MCP configuration key, and transport type
complete tool names, purposes, required and optional parameters
enums, limits, defaults, incompatibilities, asynchronous behavior, and prerequisites

For dynamic pages, use a browser capable of reading the rendered detail and tool panels. Treat the Marketplace tool definitions as the source of truth for tool behavior. Do not infer unsupported parameters from general marketing copy or from similarly named MCPs.

2. Choose the destination

Map the product to one business domain:

Patent search, patent analytics, portfolios, legal status, valuation, or workspace collections: ip-intelligence
Drugs, biology, chemistry, clinical, regulatory, or life-science intelligence: life-sciences
TRIZ, engineering innovation, scientific literature, concept generation, or R&D workflows: rd-innovation

Use a patsnap--prefixed directory name. Preserve a Marketplace slug that already starts with patsnap-; otherwise prefix it, for example patent-analysis becomes patsnap-patent-analysis. Before creating a directory, search the repository for an existing canonical location.

3. Write the server README

Use the README template in the reference. Keep it useful to both humans and catalog consumers:

define what the MCP does and what it does not do
identify its data source or dependency on upstream tool output
list every supported tool with a concise, accurate description
provide a copyable configuration using the exact endpoint and key
give realistic usage examples grounded in supported capabilities
link to the exact Marketplace detail page and repository

Never include a real API key. Use YOUR_API_KEY in examples.

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

4. Write the service SKILL

The service SKILL.md is an agent operating guide, not a duplicate product brochure. Follow the repository's service frontmatter convention and template in the reference. Document:

when the MCP should and should not be used
prerequisites and exact connection configuration
correct tool ordering and upstream dependencies
required inputs, important defaults, enums, maximums, and unsupported combinations
how to interpret empty, partial, asynchronous, or estimated results
short example workflows and official resources

Do not invent tool schemas. Prefer explicit constraints that prevent invalid calls and misleading conclusions.

5. Update discovery indexes

Update the root README's relevant domain description and service table. Update the matching category README in the same way.

Add the server to root glama.json as:

patsnap/mcp/<category>/<server-directory>

Keep relatedServers grouped by category and sorted by directory name. Add narrowly relevant keywords or quality-description coverage when the new capability materially expands the catalog.

Category-level glama.json files currently contain only schema and maintainer metadata. Do not add a service list to them unless their schema or existing repository convention changes.

6. Verify before handoff

Check all of the following:

server title, slug, endpoint, configuration key, transport, and version agree across files
every documented tool exists on the Marketplace page
required parameters and limits are not weakened or omitted
every README link and every relatedServers path resolves to the intended local directory
edited JSON parses successfully
the generic documentation skill passes the official skill validator
no unfinished placeholder, scaffold text, secret, or accidental unrelated edit remains
git diff --check succeeds

Review the final diff and report exactly which MCP directories and indexes changed.

Files

SKILL.md and 2 other files (references) in .agents/skills/mcp-documentation-standard of patsnap/mcp.

SKILL.md
agents/openai.yaml
references/templates.md

Open the folder on GitHubat commit 7a4b429

Compare with similar skills

MCP Documentation Standard 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.

MCP Documentation Standard compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
MCP Documentation Standard this skillpatsnap/mcp	113	—	~1.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Development AssistantRobThePCGuy/Claude-Patent-Creator	196	—	~1.3k	Automated safety check: Notes	MIT	3 days ago
Olore Claude Code Latestolorehq/olore	104	—	~901	Automated safety check: Pass	MIT	today
Researching With Deepwikiaiskillstore/marketplace	430	—	~1.2k	Automated safety check: Pass	None	today
Claude Docs Consultantcentminmod/my-claude-code-setup	2.7k	—	~959	Automated safety check: Pass	MIT	2 days ago
Typescript Styletjx666/vscode-mcp	105	—	~961	Automated safety check: Pass	Custom licence	2 mo ago

Similar skills

Development Assistant
RobThePCGuy/Claude-Patent-Creator
Guides through adding new features, MCP tools, analyzers, and extending the patent creator system.
196 GitHub stars~1.3k tokensUpdated 3 days ago
Agent WorkflowsAuto-check: notes
Olore Claude Code Latest
olorehq/olore
Local claude-code documentation reference (latest). An agent skill from olorehq/olore.
104 GitHub stars~901 tokensUpdated today
Agent WorkflowsAuto-check passed
Researching With Deepwiki
aiskillstore/marketplace
Research GitHub, GitLab, and Bitbucket repositories using DeepWiki MCP server.
430 GitHub stars~1.2k tokensUpdated today
Agent WorkflowsAuto-check passed
Claude Docs Consultant
centminmod/my-claude-code-setup
Consult official Claude Code documentation from code.claude.com using selective fetching.
2.7k GitHub stars~959 tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed
Typescript Style
tjx666/vscode-mcp
TypeScript code style and repo conventions for VSCode MCP — inference vs explicit types, ESM import suffixes, zod schema contracts, async VSCode/Node APIs, JSON-safe IPC results, JSDoc for public…
105 GitHub stars~961 tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Score Harness
ruvnet/metaharness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness.
694 GitHub stars~613 tokensUpdated today
DevelopmentAuto-check passed

Questions about MCP Documentation Standard

What does MCP Documentation Standard do?

Create or update Patsnap MCP catalog documentation in this repository. MCP Documentation Standard is an agent skill from patsnap/mcp. Create or update Patsnap MCP catalog documentation in this repository.

When should I use MCP Documentation Standard?

MCP Documentation Standard fits situations like: adding a Marketplace MCP server; refreshing its README; classifying it under ip-intelligence; updating the repository README and Glama indexes.

How do I install MCP Documentation Standard in Claude Code?

Run `npx skills add patsnap/mcp --skill mcp-documentation-standard -a claude-code`. Or copy the skill folder (.agents/skills/mcp-documentation-standard in patsnap/mcp) into .claude/skills/mcp-documentation-standard in your project. Claude Code loads it when a task matches its description.

How do I install MCP Documentation Standard in Codex?

Run `npx skills add patsnap/mcp --skill mcp-documentation-standard -a codex`. Or copy the skill folder (.agents/skills/mcp-documentation-standard in patsnap/mcp) into .agents/skills/mcp-documentation-standard in your project. Codex loads it when a task matches its description.

Can I use MCP Documentation Standard 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 patsnap/mcp --skill mcp-documentation-standard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcp-documentation-standard, .gemini/skills/mcp-documentation-standard, .github/skills/mcp-documentation-standard and .opencode/skills/mcp-documentation-standard in your project.

What does MCP Documentation Standard need to run?

Going by SKILL.md and its folder, MCP Documentation Standard needs the command-line tools its instructions call (git). Our summary lists: A credential in YOUR_API_KEY.

Does MCP Documentation Standard access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is MCP Documentation Standard 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 MCP Documentation Standard use?

MCP Documentation Standard 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 MCP Documentation Standard use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 851 tokens, read only when the agent opens those files.

What are the alternatives to MCP Documentation Standard?

Skills that share tags, products or a category with MCP Documentation Standard: Development Assistant (RobThePCGuy/Claude-Patent-Creator, 196 stars), Olore Claude Code Latest (olorehq/olore, 104 stars), Researching With Deepwiki (aiskillstore/marketplace, 430 stars) and Claude Docs Consultant (centminmod/my-claude-code-setup, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains MCP Documentation Standard?

patsnap (a GitHub organization) maintains it in patsnap/mcp, which has 113 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on August 20, 2026.

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

Install MCP Documentation Standard

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

MCP Documentation Standard

Required outcome

1. Collect authoritative Marketplace facts

2. Choose the destination

3. Write the server README

4. Write the service SKILL

5. Update discovery indexes

6. Verify before handoff

Files

Compare with similar skills

Similar skills

More from patsnap/mcp

Related

Questions about MCP Documentation Standard