Agent skill · data analytics · jeremylongshore
adobe-load-scale
Derive a safe Adobe workload envelope from synthetic load, queue/backpressure behavior, current service constraints, spend, and output correctness. Use when the task requires adobe capacity and load envelope. Trigger with "load test Adobe", "scale Firefly jobs", or "Adobe capacity plan".
Why this skill is useful
Adds executable k6 load testing scripts and Kubernetes HPA configurations specifically for Adobe APIs, which are not commonly found in public documentation.
What it needs
Requires k6 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 Capacity and Load Envelope Overview Derive a safe Adobe workload envelope from synthetic load, queue/backpressure behavior, current service constraints, spend, and output correctness. 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 Capacity is service-, operation-, entitlement-, and contract-specific. Measure arrival rate, queue age, concurrency, vendor time, 429/5xx, retries, terminal completion, storage transfer, cost units, and correctness. Do not publish guessed universal throughput. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use dedicated sandbox credentials, synthetic non-sensitive inputs, environment assertions, and a hard kill switch. Credential sharding to evade limits is forbidden. Instructions 1. Define workload shape, target volume, objectives, data/output checks, budget, ramp, abort thresholds, and cleanup. 2. Read current product constraints and measure a single-job baseline across all lifecycle stages. 3. Build an open/closed load model that drives the queue, not direct uncontrolled vendor floods. 4. Ramp one dimension at a time while recording concurrency, latency, 429s, failures, completions, spend, and artifacts. 5. Exercise backpressure, cancellation, unknown completion, vendor degradation, worker restart, and DLQ recovery. 6. Publish the conservative envelope, autoscaling/queue controls, emergency stop, capacity owner, and retest date. 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-load-scale