Agent skill · design visual · jeremylongshore
adobe-policy-guardrails
Analyze and enforce repository, runtime, data, spend, endpoint, and approval guardrails without guessing secret formats or content-policy rules. Use when the task requires adobe policy and execution guardrails. Trigger with "Adobe guardrails", "block unsafe Adobe calls", or "Adobe policy checks".
Why this skill is useful
Adds specific Adobe lint rules and CI checks for credential scanning and content policy enforcement that the AI wouldn't reliably generate on its own.
What it needs
Requires eslint installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Policy and Execution Guardrails Overview Analyze and enforce repository, runtime, data, spend, endpoint, and approval guardrails without guessing secret formats or content-policy rules. 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 Guardrails derive from current service docs and local policy: approved auth flows, hosts/versions, scopes/profiles, schemas, storage domains, budgets, data classes, and approval boundaries. Secret prefixes and prompt regexes are not authoritative security or content-policy controls. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use mature secret scanners plus entropy/context rules and provider revocation procedures. Runtime authorization evaluates credential binding, entitlement, resource, operation, and approval. Instructions 1. Inventory all Adobe calls, credentials, endpoints, versions, payload classes, storage URLs, retries, jobs, events, and destructive operations. 2. Create allowlists for current hosts/versions/services and denylists for JWT, /sensei/cutout, and retired Lightroom Firefly Services. 3. Validate configuration/request/response schemas and redact tokens, signed URLs, prompts, and customer content. 4. Enforce data-purpose, owner, budget, concurrency, idempotency, and approval tokens before side effects. 5. Route Adobe policy outcomes to a human-readable denial path; never silently rewrite prompts or broaden scopes. 6. Test bypasses, stale docs, false positives, emergency disablement, exception expiry, and audit receipts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-policy-guardrails