Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/adobe-prod-checklist

@820dfc8
Run it yourself

Issue an evidence-backed production decision across Adobe auth, entitlements, API versions, data custody, async reliability, spend, observability, and rollback. Use before launch or a material integration change. Use when the task requires adobe production readiness decision. Trigger with "Adobe production checklist", "approve Adobe launch", or "Adobe go-live review".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈98 tokens for metadata: the name and description. ≈883 when used: this file. ≈848 more on demand in 1 file.

Description uses 4.9% 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 ≈393 characters, or 4.9%.

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 Production Readiness Decision

Overview

Issue an evidence-backed production decision across Adobe auth, entitlements, API versions, data custody, async reliability, spend, observability, and rollback. 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

A launch is ready only when the deployed artifact and actual organization/project/workspace, credentials, product profiles, service versions, storage, queues, events, monitoring, support, and rollback are evidenced together. Passing a token call or happy path is insufficient. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Verify secret lifecycle, user consent if applicable, least privilege, entitlement, rotation, revocation, and environment isolation. JWT, Photoshop v1, and retired Lightroom Firefly Services references are launch blockers.

Instructions

  1. Verify immutable artifact, dependencies, configuration, generated assets, tests, migrations, and rollback target.
  2. Confirm organization/project/workspace, auth flow, scopes, profiles, entitlement, storage, and owner matrices.
  3. Review every service version, async job, retry/idempotency, rate/spend, event authenticity, and EOL guard.
  4. Review data classification, signed URLs, logs, retention, deletion, incident response, and vendor support custody.
  5. Exercise canary, denial, 429, unknown status, rollback, reconciliation, and cleanup paths.
  6. Issue GO, CONDITIONAL GO, or NO-GO with evidence, owners, expirations, and rollback authority.

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

Named release, security, data, budget, and operations owners approve their controls. Deploy, generation, upload, webhook replacement, secret deletion, and asset deletion remain separate actions.

Error Handling

  • NO-GO on obsolete endpoints, missing entitlement, unbounded polling/retries, or unverified rollback.
  • A skipped negative test remains an open condition.
  • Do not waive content or signed-URL leakage as observability detail.

Output

Return the signed control matrix, evidence links, failed gates, decision, conditions, owners, expiry, and rollback triggers. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Reject a release containing /sensei/cutout.
  • Approve a canary only after unknown-job and credential-revocation paths pass.

Validation

Exercise and record expected and observed results for:

  • obsolete API
  • entitlement
  • 429
  • unknown job
  • secret revocation
  • rollback

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 is a legitimate production deployment checklist for Adobe API integrations. It follows security best practices for credential management and uses standard deployment tools like kubectl and curl for their intended purposes.

  • 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
<release> <environment> <change-scope>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "readiness"
]
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-prod-checklist