brand-guidelines, has one of each kind of file a skill can carry. Select a file to read what it's for and see a minimal example.expense-reports, has one of each file that chat, Cowork, and Claude Code all load, plus the README and license the directory requires. Select a file to read what it’s for and see a minimal example.The manifest identifies the plugin to every app and to Anthropic's directory, which doesn't accept a plugin without one. To publish the plugin in Anthropic's directory you also need [a README and a license](/docs/plugins/pre-submission-checklist#readme-and-license); select those files in the tree to see what each needs.
Its `name` is the plugin's permanent identity: people install and refer to the plugin by this value, so make it specific to your product and never change it after release. Change `displayName` when you want a different label.
This manifest has the fields that every app and the directory read:
```json theme={null} { "name": "expense-reports", "displayName": "Expense Reports", "version": "1.0.0", "description": "File, track, and approve expense reports from a conversation, using your finance system's connector and your company's approval rules.", "author": { "name": "Example Corp", "url": "https://example.com" }, "license": "MIT" } ```A skill is a `SKILL.md` file in its own folder under `skills/`, and the folder name matches the skill's `name` field. Claude decides when to load the skill from its `description`, so write the description as the situations a user would be in. Skills load in chat, Cowork, and Claude Code.
This skill files an expense from a receipt:
```markdown theme={null} --- name: file-expense description: File an expense report. Use when the user mentions a receipt, reimbursement, or expense, or asks to submit spending for approval. --- To file an expense: 1. Read the amount, date, merchant, and currency from the receipt. 2. Call the expenses connector's `create_report` tool with those fields. 3. Reply with the report number and its approval status. ```A skill folder can hold [supporting files](/docs/skills/how-to#add-resources) that are too detailed for `SKILL.md`:
Mention each file in `SKILL.md` so Claude knows when to load it, for example "Pick the category from `references/categories.md`".
This reference file lists the expense categories:
```markdown theme={null} # Expense categories - Travel: flights, hotels, taxis, and mileage - Meals: client meals and team events - Software: subscriptions and licenses ```A skill can include scripts in a `scripts/` folder next to `SKILL.md`.
In `SKILL.md`, refer to a script by its path under `${CLAUDE_SKILL_DIR}`, for example `python3 ${CLAUDE_SKILL_DIR}/scripts/total.py receipts.csv`. [Add scripts](/docs/skills/how-to#add-scripts) explains how each app resolves that path.
This script totals the amounts in a CSV file of receipts:
```python theme={null} import csv import sys with open(sys.argv[1], newline="") as f: total = sum(float(row["amount"]) for row in csv.DictReader(f)) print(f"{total:.2f}") ```A command is a single Markdown file under `commands/` with a `description` in its frontmatter. In Cowork and Claude Code, you run it by typing its name, here `/expense-reports:summarize`. In chat, a command loads as a skill, and Claude applies it when the task fits.
This command summarizes a month's expenses:
```markdown theme={null} --- description: Summarize this month's expense reports --- List this month's expense reports with their totals and approval status, then summarize them in three sentences. ````.mcp.json` at the plugin root references your remote MCP server by URL. On claude.ai and in Cowork, the entry is listed on the plugin's **Connectors** tab, where each user adds or connects it and signs in through your server's OAuth flow. Claude Code loads it with the plugin.
Don't put API keys or other secrets in this file, because every person who installs the plugin receives its files.
This one points at the expenses server:
```json theme={null} { "mcpServers": { "expenses": { "type": "http", "url": "https://mcp.example.com/mcp" } } } ```A plugin loads without a README, but you need one to publish it: Anthropic's directory shows the README as the listing's description, and [validation](/docs/plugins/pre-submission-checklist#readme-and-license) blocks a submission that has none.
Write at least 40 words, not counting words inside code blocks, and say what the plugin does, how to use it, and what data it sends.
This README covers those three points:
```markdown theme={null} # Expense Reports File, track, and approve expense reports from a conversation with Claude. ## Use it Attach a receipt and ask Claude to file it. Claude reads the amount, date, and merchant, files the report through the Expense Reports connector, and replies with the report number. Ask what's waiting on you to list the reports that need your approval. ## Data The plugin sends receipt details and report fields to your Example Corp account through mcp.example.com. It stores nothing itself. ```A plugin loads without a license, but you need one to publish it: Anthropic's directory doesn't list a plugin until it has a license, and [validation](/docs/plugins/pre-submission-checklist#readme-and-license) blocks a submission that has neither a `LICENSE` file nor a `license` field.
Add a `LICENSE` file to the plugin folder, or set `license` in `plugin.json`.