About compdf-ocr
This ComPDF OCR skill helps agents and teams plan OCR requests for scanned PDFs and images. It covers text extraction, searchable-PDF output, and supported language values using the official API documentation.
Key features
- 01Convert PDFs to editable or searchable PDFs
- 02Extract text from PDFs
- 03OCR images into text
- 04Look up supported OCR languages
- 05Plan API requests from official documentation
Use cases
- 01Extract readable text from scanned PDFs
- 02Recognize text in image files
- 03Create searchable PDFs for archiving
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ compdfkit/ compdf-skills --skill compdf-ocrAfter installing, type/compdf-ocrin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlreferences/endpoint-index.mdofficial-api-reference.mdDetails
From the project READMEComPDF OCR
Overview
ComPDF OCR helps agents and teams unlock text from scanned PDFs, screenshots, photographed files, and other image-based documents. It supports OCR on both PDFs and image files, making it easier to extract readable text, recover structured content, and create searchable outputs for analysis, archiving, and workflow automation.
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 |
|---|---|
| PDF to editable/searchable PDF | pdf-to-editable-pdf-tool-guide |
| PDF text extraction | pdf-to-txt |
| Image OCR to text | image-to-txt |
| OCR language values | ocr-languages |
Scope
Restrict this skill to OCR and OCR-derived text or searchable-PDF output. Use the matching conversion skill for other target formats.
Workflow
- Identify the source file type, desired output, and requested operation.
- Read
references/endpoint-index.mdand 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=5in 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_keyin the directory containing thisSKILL.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-localapi_keyfile 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.