Agent skill · data analytics · jeremylongshore
adobe-data-handling
Analyze and enforce classification, minimization, signed-URL custody, retention, deletion, content provenance, and privacy-request boundaries for Adobe workflows. Use when the task requires adobe data custody and privacy review. Trigger with "Adobe data handling", "PDF privacy", or "Firefly content policy".
Why this skill is useful
Provides specific patterns and scripts for PII detection and GDPR compliance that are not commonly known.
What it needs
Requires adobe-sdk 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
Adobe Data Custody and Privacy Review Overview Analyze and enforce classification, minimization, signed-URL custody, retention, deletion, content provenance, and privacy-request boundaries for Adobe workflows. 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 Adobe services have distinct custody contracts. PDF Services can use supported customer-storage signed URLs and can delete Adobe-hosted assets through the Assets endpoint. Firefly inputs/outputs and Content Credentials require product-specific review. Privacy Service is a separate Experience Platform API with its own authorization contract. Recheck the dated evidence map before relying on mutable product behavior. Authentication Treat tokens and signed URLs as secrets and prompts, images, PDFs, extracted text, event bodies, and identifiers as classified content. Do not send data to a service merely because auth succeeds. Instructions 1. Map every input, derived field, prompt, artifact, event, log, storage hop, recipient, jurisdiction, purpose, and owner. 2. Minimize fields/content and select customer-managed storage or Adobe assets from current service/security evidence. 3. Set signed-URL scope/expiry, encryption, access, provenance, retention, deletion, and legal-hold controls. 4. Validate content-policy and Content Credentials behavior from live product outcomes without inventing regex screening guarantees. 5. Separate ordinary application deletion from regulated Privacy Service requests and identify responsible controllers/processors. 6. Test redaction, access, expiry, deletion, legal hold, provenance preservation, and incident escalation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-data-handling