Update to ShipPDF

{
  "description": "Create a reusable ShipPDF template for an invoice, report, proposal, certificate, or other PDF, including its layout, data schema, and sample data. Use when the user wants to design a new ShipPDF template or turn a reference document into one.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 427
    }
  ],
  "name": "shippdf-create-template",
  "skill_md_contents": "---\nname: shippdf-create-template\ndescription: Create a reusable ShipPDF template for an invoice, report, proposal, certificate, or other PDF, including its layout, data schema, and sample data. Use when the user wants to design a new ShipPDF template or turn a reference document into one.\n---\n\n# Create a ShipPDF template\n\nUse the connected ShipPDF MCP tools. Discover the tools provided by the ShipPDF\nserver; client prefixes vary, so match the tool names below to the available\ntools. If the connection requires authentication, direct the user to the client's\nShipPDF connection controls to sign in and select a workspace. Never ask for\npasswords or API tokens in conversation. If a required tool is unavailable,\nexplain the missing connection or permission instead of inventing a result.\n\n1. Establish the document's purpose, content, repeated data, branding, and paper\n   size from the request and any reference. Ask only for missing details that\n   prevent useful progress. Use clearly labeled sample values for a design;\n   never invent real customer facts, amounts, or legal terms.\n2. Call `list_projects` to resolve the destination project. Follow `next_cursor`\n   when needed. Use an explicitly selected project, or the sole available one;\n   ask the user to choose when several are plausible. Never invent `proj_` IDs.\n3. Call `get_authoring_guide` before authoring. Use `describe_schema` for the exact\n   shape of unfamiliar nodes, page settings, fields, expressions, and formats.\n   The live guide and tool schemas are authoritative; do not substitute HTML,\n   CSS, or an imagined JSON format for a ShipPDF template document.\n4. Build the document using short input and editor defaults. Use paper presets\n   and orientation, leaving margins at their defaults unless specified. Give\n   every explicit length its unit. Use full data paths, typed numeric amounts,\n   and display formatting. Use calculated fields for supported totals and table\n   expressions for line amounts. Draw shared cell borders once.\n5. If an image is needed, use `import_asset` with a public URL provided or\n   authorized by the user, then reference its returned asset ID. Do not send\n   local paths or private URLs to this tool. For generated or user-provided image\n   bytes you can access, first create the template, then call `upload_image` with\n   its `template_id`, `filename`, and base64 `content` (up to 5 MB decoded).\n   Set the image node's `imageSource` to `{type: asset, assetId: <returned ID>}`\n   with `edit_template`. Never put image bytes or data URIs in the document.\n   Proceed without optional branding if no supported source is available.\n6. Call `create_template` with `project_id`, `name`, and `document`. Read the\n   returned `pages`, `lock_version`, `publishable`, and `problems`. A saved draft\n   may still have problems; `publishable: null` does not mean validation passed.\n   Fix reported paths and node problems with `edit_template`, threading the\n   latest lock version. On a stale version, reapply the intended changes to the\n   current draft returned by the server, preserving other edits.\n7. Offer the returned `mcp_preview_url` for visual review. If browser tools are\n   available and authorized through the client's permission flow, inspect it.\n   Add `&grid=true&guides=true&bounds=true&inspect=true` for node bounds and page\n   guides if helpful. Otherwise use the returned document and page diagnostics.\n   Preview links expire; `get_draft_template` refreshes them. Browser preview\n   costs no generation credits and does not verify final PDF pagination.\n8. Leave the result as a draft unless the user has requested publishing or PDF\n   generation. If publishing is authorized, publish only when `publishable` is\n   true and problems are empty using `publish_template` with the reviewed\n   `lock_version`. If publishing reports a stale version, review the current\n   draft before retrying; never publish an unseen version. Publishing changes\n   future generations of this template. For an authorized PDF, continue with\n   the `shippdf-generate-document` skill; each generation spends one credit.\n\nReport the template name and `template_id`, whether it is a draft or published,\nany unresolved problems, and the preview link when available. Report a PDF only\nafter generation has completed successfully.\n"
}