Overview

Use Quill, the AirOps agent captain, to work across Insights, Brand Kits, Playbooks, and workspace context.

Quill is the AirOps agent captain. Use Quill to move from insight to action across AirOps: ask questions about the page you are viewing, reference workspace context, and build or revise Playbooks.

Quill works best when you give it a clear goal, the relevant context, and permission to make the change you want. When Quill changes a Playbook or Brand Kit, review the result before publishing or running it at scale.

What Quill can help with

Quill can help you:

• Answer questions about your current AirOps page.

• Review Insights data and identify where to act next.

• Use Brand Kit context when planning content or updating instructions.

• Create, edit, and improve Playbooks from natural-language prompts.

• Manage Playbook Inputs, Artifacts, Tools, references, and Triggers.

• Search AirOps docs when you ask platform questions.

• Use file, image, PDF, and text attachments as part of a request.

Quill does not replace review for high-impact changes. Publish a Playbook only after you have reviewed the draft and confirmed the setup.

How to use Quill

1. Open a page in AirOps where Quill is available.

2. Click the green Quill button in the lower-right corner.

3. Ask a question or describe the change you want.

4. Add references with / when you want Quill to use a specific Brand Kit, Playbook, Prompt, Page, or Citation.

5. Attach files with the paperclip button when Quill should use source material.

6. Review Quill's answer or the draft changes it made.

7. Publish, run, or continue editing only after the output matches your goal.

On an empty Playbook, Quill may open automatically so you can describe what you want to build.

Quill is available on most workspace pages. It does not appear in account settings, usage, trash, the Workflow editor, or agent chat.

Page context and references

Quill receives context about the page where you send each message. For example, if you message Quill from a Playbook editor, it can use that Playbook as the target. If you message Quill from a Brand Kit, Grid, Knowledge Base, Workflow, Folder, Inbox, or Insights page, it can use that page context to answer more precisely.

Use / in the chat box to add explicit references. References help Quill focus on the exact resource you mean, especially when a workspace has multiple Brand Kits, Playbooks, tracked Pages, Prompts, or Citations.

Quill uses the page context from the moment you send the message. If you navigate to a different page during the same chat, send a new message from that page so Quill receives the updated context.

Attachments

Use attachments when Quill needs source material that is not already in AirOps. Quill accepts up to five files per message. Each file can be up to 10 MB.

Supported attachment types include:

• JPG, JPEG, PNG, GIF, and WebP images

• PDF files

• TXT and Markdown files

• JSON files

• HTML files

• CSV files

Quill can also use a screenshot of your current page when screenshot capture is enabled for your workspace.

Chat controls

Use the Quill header controls to manage the conversation:

Control	Use for
History	Reopen a previous Quill conversation.
New chat	Start a new conversation without prior chat context.
Enter full screen	Expand Quill when you need more space.
Minimize	Close the panel while keeping Quill available from the launcher.
Stop generating	Stop Quill while it is responding.

Examples

Use direct instructions like:

• "Create a Playbook to refresh pages with declining citations."

• "Explain what this Playbook does and suggest improvements."

• "Use this Brand Kit and outline a content refresh strategy."

• "Compare these citations and tell me which pages need updates."

When asking Quill to change a Playbook, include the outcome, source context, and any constraints in one message. For example:

Revise this Playbook so it refreshes blog posts with declining AI citations. Keep the existing Brand Kit Input, add a research section that checks current SERP and citation data, and add a Human Review checkpoint before any CMS update.