# Quill Agent Skill

You are talking to **Quill**. This document is a short orientation and an index for an external agent. Detailed task teaching lives in the procedure library. This file has no organization data.

## Find a useful starting point

Quill organizes structured information, collects it through forms, generates
documents from templates, and supports document review and signing. Product
capability, connection authority, and visible content are different.

For MCP connections, `quill_orient` with `{}` reports current authority,
including `connection.permissions` for browser sign-in. `quill_catalogue`
lists product capabilities; its entries do not grant permission to run them.
The live guide lists visible published models and forms. An empty list does not
establish that there are no drafts or other resources.
Browser sign-in tokens work through MCP, not direct HTTP API routes.

When someone asks what is possible, summarize Quill, their permission, and
visible work. Use available tools and the relevant library procedure to verify
a proposed action. Offer two or three grounded examples. Do not require the
person to learn internal field names or read the full reference first.

Start from what the person has already explained and inspect relevant existing
work before suggesting replacements. For a blank start, ask one useful
question, such as "What would you like to collect or turn into a document?"
If their goal is clear, ask only about the next consequential decision. Avoid
a long questionnaire or a complete schema designed in isolation.

Offer to create or edit only when the current grant, role and supported tools
allow it. Read access can still support discussing the design; explain the
specific extra access needed before promising changes. Asking what is possible
does not authorize creating sample data, rehearsing changes or publishing.
For a concrete requested change, make the smallest useful agreed change within
its mandate, read it back, and explain the result.
Use visual review only when browser tools and access exist. Distinguish saved
drafts from published content. Do not add another confirmation loop for an
already authorized action.


## Index

Public links are readable without a credential. Named catalogue, authority, and library commands need a credential.

- **Task procedures:** [/llms.txt](/llms.txt) lists every procedure. [/llms-full.txt](/llms-full.txt) contains the procedure text. The same pages are on the public website at [the procedure library](https://quilltasks.com/developers/library.md).
- **Catalogue:** [capability manifest](/.well-known/quill-agent-manifest). With a credential, `quill_catalogue` or `quill catalogue` lists capability ids. Entries do not grant permission to run them.
- **Authority:** [Read this connection's authority](https://quilltasks.com/developers/library/agent/orient.md). With a credential, `quill_orient` or `quill orient` reports the calling connection.
- **Library search:** [Dispatch capabilities](https://quilltasks.com/developers/library/agent/dispatch.md) is the procedure for `agent.library.list` and `agent.library.read`. With a credential, `quill library --q <text>` searches and `quill library <id>` reads one procedure.
- **Library resource:** with a credential, an MCP host reads `quill://library/{id}`. The same text is public at `https://quilltasks.com/developers/library/{id}.md`.
- **CLI:** from the repository, `pnpm --filter @quill/cli quill catalogue` and `pnpm --filter @quill/cli quill library`. `quill library` takes one document id, or `--q`, `--cursor`, and `--limit`.
- **Connect and changes:** [Connect an agent host by signing in](https://quilltasks.com/developers/library/agent/connect.md), [Dispatch capabilities](https://quilltasks.com/developers/library/agent/dispatch.md), [Rehearse an administrative change](https://quilltasks.com/developers/library/agent/plans.md), [Ask a person to review work first](https://quilltasks.com/developers/library/agent/proposals.md).
- **Salesforce setup:** [Salesforce setup and receipts](https://quilltasks.com/developers/library/integrations/salesforce.md). The generated package setup reference is in that procedure.

Per-organization orientation is `GET /api/agent/agents-md` and needs a credential. It is not part of this document.
