Skip to content
Development
Skill

/templates

PandaDoc template library and structure: layout, content blocks, tokens, interactive fields, signature fields, pricing tables, and recipient roles, plus the MSP template set (MSAs, SOWs, proposals, quotes, NDAs, change orders, QBRs), template versioning, tags, and the template

From plugin
msp-claude-plugins
46200 skills146 agents200 commands4 MCP
Install
$ npx -y skills add wyre-technology/msp-claude-plugins --skill templates --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/templates

Context preview

The summary Claude sees to decide when to auto-load this skill.

PandaDoc template library and structure: layout, content blocks, tokens, interactive fields, signature fields, pricing tables, and recipient roles, plus the MSP template set (MSAs, SOWs, proposals, quotes, NDAs, change orders, QBRs), template versioning, tags, and the template

SKILL.md

templates.SKILL.md
name: "PandaDoc Templates"
description: >
  PandaDoc template library and structure: layout, content blocks, tokens,
  interactive fields, signature fields, pricing tables, and recipient roles,
  plus the MSP template set (MSAs, SOWs, proposals, quotes, NDAs, change
  orders, QBRs), template versioning, tags, and the template field reference.
when_to_use: >-
  When browsing the template library, choosing a template for a document type, inspecting
  a template's fields and tokens, or using a template to create a new document. Use when:
  pandadoc template, pandadoc blueprint, pandadoc library, document template, template search,
  template list, msa template, sow template, proposal template, or quote template.

PandaDoc Template Management

Overview

Templates in PandaDoc are reusable document blueprints that define the structure, layout, content, and fields of a document. MSPs use templates to standardize their business documents -- managed service agreements (MSAs), statements of work (SOWs), proposals, hardware quotes, and NDAs. Templates contain placeholders (tokens) for client-specific content, signature fields, and pricing tables that get populated when a document is created. A well-organized template library is the foundation of an efficient MSP sales process.

Anti-triggers

  • **A real document created from a template** — templates have no recipients,

status, or signatures; use `pandadoc-documents`.

  • **Which template suits a given MSP deal type** — use `pandadoc-proposals`.

MCP Tools

Available Tools

| Tool | Description | Key Parameters | |------|-------------|----------------| | `pandadoc-list-templates` | List and search templates | `q` (search query), `count`, `page`, `tag`, `folder_uuid` | | `pandadoc-get-template` | Get template details | `id` (required) |

List Templates

Call `pandadoc-list-templates` with optional parameters:

  • **Search by name:** Set `q` to a template name or keyword (e.g., "MSA", "proposal", "quote")
  • **Filter by tag:** Set `tag` to a template tag (e.g., "msp", "managed-services")
  • **Filter by folder:** Set `folder_uuid` to filter by a specific folder
  • **Paginate:** Set `page` (1-based) and `count` (up to 100)

**Example: Find MSA templates:**

  • `pandadoc-list-templates` with `q=Managed Services Agreement`, `count=100`

**Example: Find all proposal templates:**

  • `pandadoc-list-templates` with `q=proposal`, `count=100`

**Example: List all templates:**

  • `pandadoc-list-templates` with `count=100`, `page=1`

Get Template Details

Call `pandadoc-get-template` with the `id` parameter to get full template details including fields, tokens, roles, and pricing table structure.

**Example:**

  • `pandadoc-get-template` with `id=tpl_abc123def456`

Key Concepts

Template Structure

| Component | Description | Example | |-----------|-------------|---------| | Layout | Page structure and design | Header, body sections, footer | | Content blocks | Static text and formatting | Terms and conditions, scope descriptions | | Tokens | Dynamic text placeholders | `{{Client.Company}}`, `{{Contract.StartDate}}` | | Fields | Interactive form fields | Text inputs, checkboxes, dropdowns | | Signature fields | E-signature placeholders | Signature, initials, date signed | | Pricing tables | Line-item pricing | Services, hardware, recurring fees | | Roles | Recipient roles | Client, MSP, Approver |

Common MSP Templates

| Template | Purpose | Key Tokens | |----------|---------|-----------| | Managed Services Agreement (MSA) | Long-term IT management contract | Client.Company, Contract.Term, Contract.Value, MSP.Company | | Statement of Work (SOW) | Project-specific scope and deliverables | Project.Name, Project.Timeline, Project.Budget | | Service Proposal | Proposed managed services with pricing | Client.Company, Services.Description, Pricing | | Hardware Quote | Equipment and licensing quote | Client.Company, Quote.ValidUntil, Items | | NDA | Non-disclosure agreement | Client.Company, Client.Name, Effective.Date | | Change Order | Modifications to existing agreements | ChangeOrder.Number, Original.Agreement, Changes | | Quarterly Business Review (QBR) | Review document for client meetings | Client.Company, Review.Period, Metrics |

Template Versioning

Templates in PandaDoc support versioning:

| Field | Description | |-------|-------------| | `version` | Current version number | | `date_created` | When the template was first created | | `date_modified` | When the template was last updated |

> **Important:** When a template is updated, existing documents created from earlier versions are not affected. New documents will use the latest version.

Template Tags

Use tags to organize templates by category:

| Tag | Purpose | |-----|---------| | `msp` | General MSP templates | | `managed-services` | Managed service agreements | | `project` | Project-based templates (SOWs) | | `security` | Security service templates | | `compliance` | Compliance-related documents | | `onboarding` | New client onboarding documents |

Field Reference

Template Fields

| Field | Type | Description | |-------|------|-------------| | `id` | string | Template unique identifier | | `name` | string | Template display name | | `date_created` | datetime | When the template was created | | `date_modified` | datetime | When the template was last modified | | `version` | string | Template version number | | `tags` | array | Template tags for organization | | `folder_uuid` | string | Folder the template belongs to | | `roles` | array | Recipient roles defined in the template | | `tokens` | array | Content tokens (dynamic variables) | | `fields` | array | Interactive form fields | | `pricing_tables` | array | Pricing table structures |

Token Fields

| Field | Type | Description | |-------|------|-------------| | `name` | string | Token name (e.g., "Client.Company") | | `value` | string | Default value (if any) |

Common Workflows

Find the

Read more
Ships withmsp-claude-plugins

One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai

Get the whole plugin

Other skills on msp-claude-plugins.