| name | compdf-toolkit |
| description | All-in-one ComPDF workflow for document conversion, OCR, data extraction, PDF editing, protection, compression, and watermarking. Use for any ComPDF Server API request that processes PDF, Office, HTML, CSV, RTF, TXT, or image files. |
ComPDF Toolkit
Overview
ComPDF Toolkit Skill gives AI agents a full PDF workflow layer in one package. It combines file conversion, OCR, structured extraction, page editing, encryption, decryption, and watermark processing so teams can handle document-heavy tasks without switching tools. The skill is designed for agent workflows that need reliable PDF preprocessing before analysis, routing, generation, or compliance review.
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 |
|---|
| All conversion endpoints | Conversion endpoints |
| PDF editing, security, watermark, compression, and comparison | PDF endpoints |
| Document parsing and schema-based extraction | AI endpoints |
Scope
Use this broad skill only when the request spans multiple ComPDF capabilities or no focused ComPDF skill is a clearer match.
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.
