Agent skill · creative production · jeremylongshore
adobe-core-workflow-b
Execute an Adobe PDF Services operation through explicit asset custody, asynchronous status, output verification, and cleanup. Use for approved document conversion, extraction, or generation. Use when the task requires pdf services controlled document job. Trigger with "process PDF with Adobe", "PDF Services job", or "Adobe document automation".
Why this skill is useful
Adds executable scripts for PDF creation, extraction, and conversion that extend the AI's capabilities in document automation.
What it needs
Requires npm installed locally. Requires adobe account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
PDF Services Controlled Document Job Overview Execute an Adobe PDF Services operation through explicit asset custody, asynchronous status, output verification, and cleanup. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract The REST lifecycle is authenticate, supply a supported signed URL or create an asset and upload to its pre-signed URI, create an async job, follow the Location/status contract, retrieve output, and delete Adobe-hosted assets when no longer needed. Limits vary by operation. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use server-side service credentials and bind assets to the same credential or approved signed URL. Signed URLs are bearer capabilities and must be redacted, narrowly scoped, and short-lived. Instructions 1. Classify the input, operation, page/file constraints, output, retention, transaction budget, and owners. 2. Choose customer-managed signed URLs or Adobe-hosted assets and document the custody boundary. 3. Validate media type, size, protection state, operation contract, and current limits before upload. 4. Create the job once, retain the returned status location, and poll within an attempt and elapsed-time budget. 5. Download or receive output into approved storage, verify type/hash/expected structure, and acknowledge downstream custody. 6. Delete approved Adobe-hosted assets promptly and reconcile transaction, failure, retention, and deletion evidence. Tool Discipline Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-core-workflow-b