---
name: adobe-core-workflow-b
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<operation> <input-classification> <output-destination>"
version: 1.8.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [ saas, adobe, pdf ]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval"
title: adobe-core-workflow-b
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adobe-core-workflow-b
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adobe-core-workflow-b/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/adobe-core-workflow-b`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/adobe-core-workflow-b`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/adobe-core-workflow-b) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/adobe-core-workflow-b`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/adobe-core-workflow-b --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/adobe-core-workflow-b --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.

## Approval Boundaries

Require data-owner and budget approval before upload or job creation. Decryption, external transfer, output retention, and asset deletion require explicit authorized owners.

## Error Handling

- Do not retry a disqualified or malformed document unchanged.
- Do not log input/output content, credentials, or signed URLs.
- Treat an ambiguous job result as reconciliation work, not permission to duplicate a transaction.

## Output

Return classification, storage decision, asset/job ledger, status evidence, verified output, transaction class, deletion receipt, and residual retention. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

## Examples

- Process a synthetic PDF and delete its Adobe-hosted assets.
- Reject an unsupported or protected fixture before upload.

## Validation

Exercise and record expected and observed results for:

- valid output
- unsupported input
- expired URL
- 429
- ambiguous job
- deletion verification

## Resources

- [Current first-party evidence map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adobe-core-workflow-b/references/official-docs.md) — recheck dated Adobe sources before execution.
- Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.
