Agent skill · software engineering · jeremylongshore
adobe-performance-tuning
Improve Adobe integration latency and throughput from measurements while preserving correctness, policy, and spend boundaries. Use when the task requires adobe measured performance tuning. Trigger with "tune Adobe performance", "reduce Firefly latency", or "optimize PDF jobs".
Why this skill is useful
Adds specific optimization scripts for Adobe API performance that are not commonly found in public documentation.
What it needs
Requires adobe-sdk, redis 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 Measured Performance Tuning Overview Improve Adobe integration latency and throughput from measurements while preserving correctness, policy, and spend boundaries. 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 No universal Adobe latency table is a production contract. Measure token reuse, queue wait, upload/download, submission, status polling, vendor processing, validation, and downstream work separately by service and operation. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use content-free metrics and aliases. Token reuse must honor actual expiry response and revocation; cached signed URLs and customer outputs are not performance caches by default. Instructions 1. Define objective, workload, input class, concurrency, cost ceiling, completeness, and measurement window. 2. Instrument queue, transport, vendor job, polling, storage transfer, validation, retry, and downstream spans. 3. Measure percentiles, 429s, failures, bytes, transactions/generations, and artifact correctness from a synthetic canary. 4. Test token reuse, connection reuse, right-sized inputs, bounded concurrency, adaptive polling, and safe deduplication independently. 5. Canary one change within current documented constraints and compare correctness plus spend, not latency alone. 6. Retain verified gains with rollback thresholds and remove instrumentation that captures sensitive content. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-performance-tuning--a49e02