Agent skill · data analytics · jeremylongshore
adobe-cost-tuning
Reduce Adobe integration spend using contract, invoice, usage, queue, storage, and retry evidence instead of invented per-call prices. Use when the task requires adobe workload cost and waste review. Trigger with "reduce Adobe cost", "Adobe spend review", or "PDF transaction budget".
Why this skill is useful
Provides domain-specific knowledge on Adobe API pricing models and cost optimization strategies that the AI wouldn't reliably generate on its own.
What it needs
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 Workload Cost and Waste Review Overview Reduce Adobe integration spend using contract, invoice, usage, queue, storage, and retry evidence instead of invented per-call prices. 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 Firefly entitlements and generative usage, PDF Services document transactions, and application compute/storage/egress are distinct cost classes. Pricing and plan limits are mutable; use the account contract, live usage surface, and dated first-party pages. Recheck the dated evidence map before relying on mutable product behavior. Authentication Collect aggregated aliases, operation classes, outcomes, retries, bytes, and durations. Prompts, assets, documents, users, tokens, and signed URLs are not cost telemetry. Instructions 1. Define billing window, account/contract owner, services, operations, workload units, and non-negotiable quality objectives. 2. Reconcile invoice/contract and service usage with submitted jobs, terminal outcomes, retries, duplicates, and storage/compute costs. 3. Find duplicate submissions, failed transactions, oversized inputs, stale outputs, excessive polling, and unused environments. 4. Model idempotency, caching-by-approved-hash, batching where documented, input sizing, queue admission, and retention changes. 5. Canary one control and measure quality, latency, 429s, usage units, and downstream impact. 6. Adopt only verified savings with budget alerts, anomaly ownership, rollback, and a dated pricing assumption register. 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-cost-tuning