api-patterns
3CX's native PBX MCP server: the per-PBX endpoint shape (every PBX is its own FQDN and its own OAuth authorization server — there is no shared mcp.3cx.com),…
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
$ npx -y skills add wyre-technology/msp-claude-plugins --skill templates --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/templatesContext 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
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.
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.
status, or signatures; use `pandadoc-documents`.
| 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) |
Call `pandadoc-list-templates` with optional parameters:
**Example: Find MSA templates:**
**Example: Find all proposal templates:**
**Example: List all templates:**
Call `pandadoc-get-template` with the `id` parameter to get full template details including fields, tokens, roles, and pricing table structure.
**Example:**
| 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 |
| 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 |
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.
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 | 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 |
| Field | Type | Description | |-------|------|-------------| | `name` | string | Token name (e.g., "Client.Company") | | `value` | string | Default value (if any) |
One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai
Repo: wyre-technology/msp-claude-plugins
3CX's native PBX MCP server: the per-PBX endpoint shape (every PBX is its own FQDN and its own OAuth authorization server — there is no shared mcp.3cx.com),…
3CX's live-operations surface: read-only visibility into active calls, recordings, voicemail, department and queue membership, and forwarding/presence…
3CX's read-only directory surface: resolving a caller by email or by exact extension, searching the PBX's own phonebooks, searching contacts synced from an…
3CX's system-and-configuration surface: server time, PBX event log and application log search, service status, database schema and the read-only SELECT-only…
Abnormal Security abuse mailbox cases: user-reported email submissions, case statuses and judgments, the case lifecycle, bulk and remediation actions, and…
Abnormal Security message analysis: message retrieval, email header inspection, attachments, sender reputation, delivery context, and SPF/DKIM/DMARC…