Index of every page on this site: llms.txt
All skills
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adobe-load-scale

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈77 tokens for metadata: the name and description. ≈854 when used: this file. ≈764 more on demand in 1 file.

Description uses 3.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈307 characters, or 3.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.

Approval Boundaries

Sandbox, vendor-account, data, budget, and operations owners approve tests. Bulk generation/transactions, cancellation, and artifact deletion require explicit execution approval.

Error Handling

  • Never load-test production customer workflows.
  • Abort on unexpected spend, content leakage, growing unknown jobs, or error threshold.
  • Do not use identities or projects as rate-limit shards.

Output

Return assumptions, current constraints, load model, raw/result metrics, correctness evidence, safe envelope, aborts, cleanup, and retest owner. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Show queue backpressure before the service is saturated.
  • Recover a worker restart without duplicate submission.

Validation

Exercise and record expected and observed results for:

  • ramp
  • 429
  • vendor 5xx
  • unknown completion
  • worker restart
  • kill switch

Resources

  • Current first-party evidence map — recheck dated Adobe sources before execution.
  • Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides legitimate scripts and configurations for load testing and auto-scaling Adobe API integrations using k6 and Kubernetes. It follows security best practices by using environment variables for credentials and interacting with official Adobe domains.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<workload> <target-volume> <sandbox>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "capacity"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/adobe-load-scale