Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Change a PDF’s permission flags (edit, print, copy, forms, annotations, etc.) by uploading it to the Solutions API, polling until completion, then returning a download URL for the updated PDF.
Change a PDF’s permission flags (edit, print, copy, forms, annotations, etc.) by uploading it to the Solutions API, polling until completion, then returning a download URL for the updated PDF.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill changes the permission flags of a PDF (e.g., whether it can be printed, edited, or copied) by: accepting a PDF file from the user, accepting desired permission settings (true/false), uploading them to the Solutions API, polling the job status until it is finished, returning the download URL for the updated PDF.
The API requires an API key used as a Bearer token: Authorization: Bearer <API_KEY> How the user gets an API key: https://login.cross-service-solutions.com/register Or the user can provide an API key directly. Rule: never echo or log the API key.
Base URL: https://api.xss-cross-service-solutions.com/solutions/solutions Create permission-change job: POST /api/75 multipart/form-data parameters: file — required — PDF file canModify — required — "true" or "false" canModifyAnnotations — required — "true" or "false" canPrint — required — "true" or "false" canPrintHighQuality — required — "true" or "false" canAssembleDocument — required — "true" or "false" canFillInForm — required — "true" or "false" canExtractContent — required — "true" or "false" canExtractForAccessibility — required — "true" or "false" Get result by ID: GET /api/<ID> When done, the response contains: output.files[] with { name, path } where path is a downloadable URL.
PDF file (binary) Permission flags (boolean-like), all required by API: canModify canModifyAnnotations canPrint canPrintHighQuality canAssembleDocument canFillInForm canExtractContent canExtractForAccessibility API key (string)
None
If the user does not specify permissions, use a conservative default that disallows modification and extraction, but allows printing: canModify: false canModifyAnnotations: false canPrint: true canPrintHighQuality: true canAssembleDocument: false canFillInForm: true (reasonable default if forms exist) canExtractContent: false canExtractForAccessibility: true (often desirable for accessibility) These defaults can be adjusted per product policy.
Return a structured result: job_id (number) status (string) download_url (string, when done) file_name (string, when available) permissions (object) reflecting the final values sent Example output: { "job_id": 7501, "status": "done", "download_url": "https://.../permissions.pdf", "file_name": "permissions.pdf", "permissions": { "canModify": false, "canModifyAnnotations": false, "canPrint": true, "canPrintHighQuality": true, "canAssembleDocument": false, "canFillInForm": true, "canExtractContent": false, "canExtractForAccessibility": true } }
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.