Easy to Install

CoQuill runs entirely inside Claude. There is no server to spin up, no database to configure, and nothing to host. You get document automation the moment you install it.

Two ways to install

The canonical setup is Claude Cowork with the folder download — no terminal, no configuration, and no plugin marketplace needed. Claude Code and compatible clients are also supported for users who prefer a terminal-based workflow.

Claude Cowork — Download the latest coquill-v*.zip from GitHub Releases, unzip it, and open the folder as a new Cowork project. Done.

Claude Code — Run a single command:

/plugin marketplace add houfu/coquill

That is the entire installation process.

No terminal required

If you are not a developer, Claude Cowork is the right choice. Installation is just two steps: download a zip file and open the folder. That is it — no terminal, no command line, no coding environment, nothing to configure.

Everything else happens inside the Claude conversation you already know how to use.

Dependencies handle themselves

CoQuill relies on a handful of Python packages — docxtpl, pyyaml, jinja2, and weasyprint. You never need to install them manually. When a skill runs, it installs any missing packages automatically. After the initial install, everything is cached locally.

No separate app

There is no standalone application, no Electron window, no browser tab to keep open. CoQuill lives where Claude already lives. You interact with it through the same conversation interface you use for everything else in Claude Cowork or Claude Code.

That means zero context-switching. Ask Claude to prepare a document with CoQuill, answer a few questions, and the finished file appears in your output/ folder — all without leaving the chat.

Because CoQuill is just a folder, it is completely portable. If you have built a set of templates for your own work, sharing them is as simple as zipping up the folder and sending it over. Your colleague opens it as a Cowork project on their own machine and can use the same templates to produce the same documents.

No deployment, no shared server, no access management. The whole setup travels in a zip file.

Your files stay local

Templates are local files, rendering happens on your machine, and output stays on your disk. No cloud uploads, no waiting for a remote server to respond.

CoQuill requires an active Claude session — but your documents never leave your machine.