ComPDF Encrypt & Decrypt PDF
Overview
ComPDF Encrypt & Decrypt PDF is a focused security skill for controlling access to PDF documents. It lets teams encrypt PDFs with AES-128, AES-256, or RC4 options, apply passwords and permissions, and remove passwords from authorized files when internal processing or redistribution requires it.
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 |
| Encrypt PDF |
pdf-encrypt |
| Decrypt PDF |
pdf-decrypt |
Scope
Never assist with decryption unless the user explicitly confirms authorization. Treat passwords and document content as sensitive, and do not repeat them in output.
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.
- Prefer synchronous mode for small interactive work. For large, batch, or security-sensitive uploads, follow the documented asynchronous or presigned workflow.
- Resolve the API key before preparing the request. Read the first non-empty line from
COMPDF_API_KEY_FILE when set. Otherwise read %USERPROFILE%\.compdf\api_key on Windows, or ~/.config/compdf/api_key on macOS and Linux. Pass the value only as the x-api-key header; never put it in code, logs, examples, or output.
- Before an operation that overwrites, deletes, decrypts, applies permanent protection, or sends a document externally, identify affected files and obtain confirmation unless the user has already authorized it.
- 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.
API Key
Use one local, private key file so later ComPDF tasks do not require pasting an API key into chat. The file must contain only the API key on its first non-empty line. Do not create, commit, upload, or display this file.
When the selected file is absent, unreadable, or empty, direct the user to obtain a key at 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, save it in the selected file, and retry.
Maintainer
Refresh the local official snapshot before release, then inspect the diff for renamed endpoints, changed fields, and changed enum values:
python scripts/sync_official_api_reference.py
1---2name: compdf-encryt-pdf-decrypt-pdf3description: Encrypt PDFs with AES-128, AES-256, or RC4 options and decrypt authorized PDFs with ComPDF. Use for PDF passwords, permission controls, encryption, decryption, and document-access protection.4---5
6# ComPDF Encrypt & Decrypt PDF
7
8## Overview
9
10ComPDF Encrypt & Decrypt PDF is a focused security skill for controlling access to PDF documents. It lets teams encrypt PDFs with AES-128, AES-256, or RC4 options, apply passwords and permissions, and remove passwords from authorized files when internal processing or redistribution requires it.
11
12Use this skill to select an official ComPDF Server API endpoint and prepare an accurate request plan for the supported operations below.
13
14## Supported Operations
15
16| Operation | Official page or index section |
17| --- | --- |
18| Encrypt PDF | `pdf-encrypt` |
19| Decrypt PDF | `pdf-decrypt` |
20
21## Scope
22
23Never assist with decryption unless the user explicitly confirms authorization. Treat passwords and document content as sensitive, and do not repeat them in output.
24
25## Workflow
26
271. Identify the source file type, desired output, and requested operation.
282. Read `references/endpoint-index.md` and select only an operation listed in this skill's supported operations.
293. 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.
304. Prefer synchronous mode for small interactive work. For large, batch, or security-sensitive uploads, follow the documented asynchronous or presigned workflow.
315. Resolve the API key before preparing the request. Read the first non-empty line from `COMPDF_API_KEY_FILE` when set. Otherwise read `%USERPROFILE%\.compdf\api_key` on Windows, or `~/.config/compdf/api_key` on macOS and Linux. Pass the value only as the `x-api-key` header; never put it in code, logs, examples, or output.
326. Before an operation that overwrites, deletes, decrypts, applies permanent protection, or sends a document externally, identify affected files and obtain confirmation unless the user has already authorized it.
337. 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.
34
35## API Key
36
37Use one local, private key file so later ComPDF tasks do not require pasting an API key into chat. The file must contain only the API key on its first non-empty line. Do not create, commit, upload, or display this file.
38
39When the selected file is absent, unreadable, or empty, direct the user to obtain a key at `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`, save it in the selected file, and retry.
40
41## Maintainer
42
43Refresh the local official snapshot before release, then inspect the diff for renamed endpoints, changed fields, and changed enum values:
44
45```powershell
46python scripts/sync_official_api_reference.py
47```
majiayu000