adobe-reliability-patterns
Analyze and design idempotency, bounded polling, per-service circuits, durable queues, DLQ/replay, degradation, and reconciliation for Adobe workloads
Install / Use
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-reliability-patternsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of adobe-reliability-patterns
adobe-reliability-patterns scores 83/100 on our quality scale, 518th of 642 Marketing skills we index.
Its SKILL.md is 4.1 KB long, well organised into 13 sections and no code examples: a solid amount of guidance for an agent.
With 2,785 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so adobe-reliability-patterns is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
adobe-reliability-patterns compared with similar skills
All 4 of these similar skills score higher than adobe-reliability-patterns; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| adobe-reliability-patterns (this skill)by jeremylongshore | 83 | 2.8k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install adobe-reliability-patterns?
- Run
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-reliability-patterns. The install tabs above show the steps for each supported agent. - Which AI agents does adobe-reliability-patterns work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is adobe-reliability-patterns safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is adobe-reliability-patterns still maintained?
- The repository was last updated about 2 months ago, so adobe-reliability-patterns is actively maintained.
Skill content
View source on GitHubname: adobe-reliability-patterns description: >- Analyze and design idempotency, bounded polling, per-service circuits, durable queues, DLQ/replay, degradation, and reconciliation for Adobe workloads. Use when the task requires adobe async reliability controls. Trigger with "Adobe reliability", "Firefly retry design", or "PDF job recovery". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<services> <failure-model> <recovery-objectives>" version: 1.8.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags: [saas, adobe, reliability] model: inherit effort: high compatibility: "Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval"
Adobe Async Reliability Controls
Overview
Analyze and design idempotency, bounded polling, per-service circuits, durable queues, DLQ/replay, degradation, and reconciliation for Adobe workloads. 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
Adobe services fail independently and async submission may succeed before the caller sees a response. Reliability is a state machine: planned, approved, submitted, acknowledged, running, terminal, artifact verified, downstream acknowledged, and cleaned. Unknown is not failed or safe to replay. Recheck the dated evidence map before relying on mutable product behavior.
Authentication
Idempotency records and job evidence use aliases and hashes, never tokens, signed URLs, or content. Credential failure and content/policy failure have different containment owners.
Instructions
- Map operations, side effects, states, identifiers, retryability, time budgets, dependencies, and reconciliation sources.
- Create per-service circuits and queues so one Adobe product does not exhaust all workers.
- Persist submission intent before network call and bind returned job/status/cancel evidence atomically.
- Poll returned status URLs with jitter, terminal-state validation, cancellation, and strict elapsed-time budget.
- Route exhausted/unknown work to quarantine or DLQ; replay only after reconciliation and approval.
- Exercise crashes, timeouts, 429/5xx, revocation, vendor outage, duplicate events, and recovery objectives.
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
Workload owner approves replay/degradation; budget owner approves resubmission; data owner approves artifact custody; security owns credential failures; cancellation/deletion require explicit approval.
Error Handling
- No fixed timeout table substitutes for measured objectives.
- Never retry unknown submissions blindly.
- Fallback output must be labeled and must not bypass policy or approval.
Output
Return state model, retry/idempotency matrix, circuit/queue design, reconciliation and replay runbooks, drills, SLOs, and owners. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.
Examples
- Recover after a crash between submission and response persistence.
- Reconcile an unknown job before approved replay.
Validation
Exercise and record expected and observed results for:
- 429
- 5xx
- ambiguous timeout
- credential revocation
- duplicate event
- vendor outage
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.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
