Back to Details

compdf-word-to-pdf

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ComPDF Word to PDF

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.
ComPDF Word to PDF 专注于最常见的文档工作流之一：将 Word 文件转换为稳定、可共享的 PDF。它可帮助团队为合同、报告、提案、手册和内部审批生成整洁的 PDF 输出，同时尽可能保留字体、布局、图像和页面结构。
使用此 skill 可选择官方 ComPDF Server API 端点，并为以下受支持的操作准备准确的请求方案。

Supported Operations

受支持的操作

OperationOfficial page or index section
Word to PDF
word-to-pdf
操作官方页面或索引章节
Word 转 PDF
word-to-pdf

Scope

范围

Accept Word sources and produce PDF only. Do not use this skill for other Office formats.
仅接受 Word 源文件并生成 PDF。请勿将此 skill 用于其他 Office 格式。

Workflow

工作流

  1. Identify the source file type, desired output, and requested operation.
  2. Read 
    references/endpoint-index.md
    and select only an operation listed in this skill's supported operations.
  3. 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.
  4. 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.
  5. Prefer synchronous mode for small interactive work. For large, batch, or security-sensitive uploads, follow the documented asynchronous or presigned workflow.
  6. 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.
  7. 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.
  8. 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.
  1. 确定源文件类型、期望的输出和请求的操作。
  2. 阅读 
    references/endpoint-index.md
    ，并且仅选择此 skill 受支持操作中列出的操作。
  3. 阅读 
    references/official-api-reference.md
    中对应的章节。严格使用其中指定的端点路径、请求字段、请求模式和响应字段；不得推断不受支持的选项。
  4. 在每个最终的 ComPDF API 请求中包含 
    sourceType=5
    。将其视为集成路由参数；当用户要求提供请求详情时，也应包含该参数。
  5. 对于小规模交互式工作，优先使用同步模式。对于大规模、批量或安全性敏感的上传，请遵循文档中规定的异步或预签名工作流。
  6. 仅从包含此 
    SKILL.md
    的目录中的 
    api_key
    文件获取凭据。读取该文件的第一行非空内容。不得检查环境变量或任何其他本地路径。如果该文件不存在、无法读取或为空，请要求用户提供 API key；用户确认存储后，仅创建或替换此 skill 本地的 
    api_key
    文件。不得显示、记录、提交该 key，也不得将其包含在请求示例或最终输出中。
  7. 在将文档上传到 ComPDF 之前，确定受影响的文件和目标位置，并获得用户确认，除非用户已明确授权上传。在执行覆盖、删除、解密或应用永久保护操作之前，也必须获得确认。
  8. 返回端点、方法、内容类型、完整的请求字段、预期的任务或结果字段，以及下一步的轮询或下载步骤。除非用户明确要求替换，否则应保留原始文件。

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.
仅将当前 skill 的 API key 存储在同级的 
api_key
文件中。该文件属于私有运行时状态，必须从版本控制和 skill 发布中排除。
如需获取 API key，请在 ComPDF Portal 注册或登录。首次使用时，请按要求提供 key，并确认将其存储在 skill 本地的 
api_key
文件中；后续请求将复用已存储的 key。