Contracts, skills and playbooks worth forking

What you can fork

Each catalog is a different kind of reusable work. A template is a document. A skill is a competence for the assistant. A playbook is the mandate it follows.

• Document templates — Structured, variable-driven agreements — not PDFs. Fork a master services agreement, an NDA or a statement of work, adapt it in the editor and keep the clause library that comes with it.
• AI skills — Packaged prompts and tools that give the assistant a specific job: risk review, clause extraction, redline etiquette. Drop-in, and reviewable line by line before you let it run.
• Playbooks — Target terms, fallbacks, concession ladders and walk-away lines. This is the mandate the assistant follows on every turn of a negotiation, not a prompt you retype.

Fork, improve, propose

The same loop as an open-source repository, inside the workspace, with a readable diff of the agreement rather than a patch file.

• Fork anything free — Open-source listings are MIT licensed. Clone one into your workspace and it is yours to use and to edit.
• Improve and propose — Edit the clone, then propose the change upstream with a readable diff of exactly what you altered — a clause, a variable, a walk-away line.
• Reviewed and merged — Maintainers review proposals. Merged work updates the canonical listing for everyone downstream of it.

A catalog, not an app store

The marketplace is how reusable work moves between workspaces. It is not a third-party integration directory, and it is not a place we invent a partner program.

• You take the listing: A fork is a copy in your workspace, not a live link that can change under you
• You take the listing: MIT listings stay free after you clone them
• The assistant uses what you installed: A skill runs only after you add it and, where the mandate requires, after you review it
• The assistant uses what you installed: A playbook is the mandate — installing it is how you tell the assistant how you negotiate
• Selling is optional: Premium listings exist for authors who want to sell a template, a skill or a playbook
• Selling is optional: Open-source listings do not become paid because you used them

Questions about the marketplace

• Do I have to use a marketplace template? No. You can draft from a blank document, from your own library, or from a marketplace listing. The assistant drafts from whichever library you have approved.
• Is a skill the same as an integration? No. A skill is packaged behaviour for the assistant inside Paqt — a review pass, an extraction, a redline style. It is not a connection to someone else's system.
• What does MIT licensed mean here? The listing's source is yours to use, to modify and to redistribute under the MIT terms attached to it. Forking it into your workspace is the ordinary way to start.
• Can I publish my own playbook? Yes. Improve a fork and propose it upstream, or publish a listing of your own. Maintainers review what becomes canonical; a private playbook can also stay in your workspace and never leave it.