> ## Documentation Index
> Fetch the complete documentation index at: https://predev.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Agents: start with https://docs.pre.dev/agents.md, which has complete recipes, plan access, polling rules, errors and limits.
> Authenticate with the workspace API key (pdk_…) from Integrations → Built-in, sent as Authorization: Bearer <key>.
> REST API: https://api.pre.dev (OpenAPI: https://docs.pre.dev/api-reference/openapi.json). AI Gateway: https://api.pre.dev/v1, OpenAI-compatible (OpenAPI: https://docs.pre.dev/api-reference/ai-gateway.openapi.json).
> pre.dev MCP server: npx -y @predotdev/mcp setup adds it to every local coding agent with every pre.dev tool plus the user's own Chrome; the hosted server is https://api.pre.dev/mcp. Search these docs over MCP at https://docs.pre.dev/mcp.

# Agent skills

> Add Agent Skills as a SKILL.md or a .zip, at personal, project, or organization scope.

Skills give the Coding Agent reusable instructions and files, such as a testing convention, a style guide, or a repository workflow. pre.dev reads skills in the [Agent Skills](https://agentskills.io/specification) format: a `SKILL.md` whose frontmatter names the skill and says when to use it.

```markdown theme={null}
---
name: pdf-forms
description: Fill in and read PDF forms. Use when the user mentions PDF forms, form fields, or fillable PDFs.
---

Use the repository's PDF library. Run the form tests after every change and report their result.
```

## Add a skill

Open **Agent Skills** in [workspace Integrations](https://pre.dev/projects/integrations?tab=skills), or the same tab in a project's **Project setup**. Then either:

* **Paste SKILL.md**: paste the file's contents.
* **Upload .md or .zip**: a `SKILL.md`, or a `.zip` of the skill folder with `SKILL.md` plus `scripts/`, `references/`, or `assets/`.

pre.dev shows what it read before you save. Every skill needs:

| Field | Rule |
| - | - |
| Name | Lowercase letters, numbers, and single hyphens; up to 64 characters |
| Description | What the skill does and when the agent should use it; up to 1,024 characters |

A skill package can hold up to 2 MB of files. Keep long material in `references/` rather than the `SKILL.md` body.

In the CLI, `/skills add <name> <instructions>` adds a personal skill from one line of instructions.

## Scope

| Where you configure it | Scope |
| - | - |
| Personal workspace | Reusable personal default |
| Personal project | Project-specific entry; a matching name overrides the personal default |
| Organization or team project | Organization-wide entry |

Choose a distinct name when the instruction should supplement an inherited entry. Reuse its name when you intend a personal project to override it.

## Edit or disable

Use the entry controls to edit, toggle, or remove a skill. Apply changes before starting the work that should use them.

In the CLI, `/skills` lists personal entries. Enter or Space toggles an entry, `d` removes it, and `o` opens workspace Integrations in the browser.

Skills guide behavior. Review the actual output and checks for the task, especially when a requirement must be enforced by a test or repository policy.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.