ComPDF Word to PDF
Overview
ComPDF Word to PDF focuses on one of the most common document workflows: converting Word files into stable, shareable PDFs. It helps teams generate clean PDF output for contracts, reports, proposals, manuals, and internal approvals while preserving fonts, layout, images, and page structure as much as possible.
Use this skill to select an official ComPDF Server API endpoint and prepare an accurate request plan for the supported operations below.
Supported Operations
| Operation |
Official page or index section |
| Word to PDF |
word-to-pdf |
Scope
Accept Word sources and produce PDF only. Do not use this skill for other Office formats.
Workflow
- Identify the source file type, desired output, and requested operation.
- Read
references/endpoint-index.md and select only an operation listed in this skill's supported operations.
- Read the matching heading in
references/official-api-reference.md. Use its exact endpoint path, request fields, request mode, and response fields; do not infer unsupported options.
- Include
sourceType=5 in every final ComPDF API request. Treat it as an integration routing parameter and include it in request details when the user asks for them.
- Prefer synchronous mode for small interactive work. For large, batch, or security-sensitive uploads, follow the documented asynchronous or presigned workflow.
- Resolve credentials only from
api_key in the directory containing this SKILL.md. Read its first non-empty line. Do not inspect environment variables or any other local path. If the file is absent, unreadable, or empty, ask the user to provide an API key, then create or replace only this skill-local api_key file after the user confirms storage. Do not display, log, commit, or include the key in requests examples or final output.
- Before uploading a document to ComPDF, identify the affected files and destination, and obtain confirmation unless the user has explicitly authorized that upload. Also obtain confirmation before operations that overwrite, delete, decrypt, or apply permanent protection.
- Return the endpoint, method, content type, complete request fields, expected task/result fields, and the next polling or download step. Preserve original files unless replacement is explicitly requested.
Credentials
Store only the current skill's API key in the sibling api_key file. This file is private runtime state and must be excluded from version control and skill publishing.
To obtain an API key, register or sign in at ComPDF Portal. On first use, provide the key when requested and confirm storing it in the skill-local api_key file; later requests reuse that stored key.
1---2name: compdf-word-to-pdf3description: Convert Word documents into polished PDFs with ComPDF. Use for contracts, reports, proposals, manuals, approvals, formal delivery, and Word-to-PDF requests.4---56# ComPDF Word to PDF78## Overview910ComPDF Word to PDF focuses on one of the most common document workflows: converting Word files into stable, shareable PDFs. It helps teams generate clean PDF output for contracts, reports, proposals, manuals, and internal approvals while preserving fonts, layout, images, and page structure as much as possible.1112Use this skill to select an official ComPDF Server API endpoint and prepare an accurate request plan for the supported operations below.1314## Supported Operations1516| Operation | Official page or index section |17| --- | --- |18| Word to PDF | `word-to-pdf` |1920## Scope2122Accept Word sources and produce PDF only. Do not use this skill for other Office formats.2324## Workflow25261. Identify the source file type, desired output, and requested operation.272. Read `references/endpoint-index.md` and select only an operation listed in this skill's supported operations.283. Read the matching heading in `references/official-api-reference.md`. Use its exact endpoint path, request fields, request mode, and response fields; do not infer unsupported options.294. Include `sourceType=5` in every final ComPDF API request. Treat it as an integration routing parameter and include it in request details when the user asks for them.305. Prefer synchronous mode for small interactive work. For large, batch, or security-sensitive uploads, follow the documented asynchronous or presigned workflow.316. Resolve credentials only from `api_key` in the directory containing this `SKILL.md`. Read its first non-empty line. Do not inspect environment variables or any other local path. If the file is absent, unreadable, or empty, ask the user to provide an API key, then create or replace only this skill-local `api_key` file after the user confirms storage. Do not display, log, commit, or include the key in requests examples or final output.327. Before uploading a document to ComPDF, identify the affected files and destination, and obtain confirmation unless the user has explicitly authorized that upload. Also obtain confirmation before operations that overwrite, delete, decrypt, or apply permanent protection.338. Return the endpoint, method, content type, complete request fields, expected task/result fields, and the next polling or download step. Preserve original files unless replacement is explicitly requested.3435## Credentials3637Store only the current skill's API key in the sibling `api_key` file. This file is private runtime state and must be excluded from version control and skill publishing.3839To obtain an API key, register or sign in at [ComPDF Portal](https://www.compdf.com/compdf-portal/signin?utm_source=github&utm_medium=referral&utm_campaign=compdf_skills_repo_en&ref_platform_id=github_compdfkit_skills_en). On first use, provide the key when requested and confirm storing it in the skill-local `api_key` file; later requests reuse that stored key.
ComPDFKit