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

/adobe-known-pitfalls

@820dfc8
Run it yourself

Detect current high-risk Adobe integration traps before they become production incidents. Use when the task requires adobe integration pitfall review. Trigger with "Adobe pitfalls", "review Adobe integration", or "find obsolete Adobe code".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈66 tokens for metadata: the name and description. ≈843 when used: this file. ≈851 more on demand in 1 file.

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

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 Integration Pitfall Review

Overview

Detect current high-risk Adobe integration traps before they become production incidents. 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

High-risk traps include Service Account JWT, confusing S2S with user auth, missing entitlements/profiles, secrets in clients, retired Photoshop v1 and Lightroom Firefly Services, reconstructed async URLs, leaked signed URLs, fixed limits, unverified events, and wrong App Builder workspace. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Review effective authority and secret flow before code style. A valid token, installed SDK, or successful deploy does not prove product entitlement or correct data ownership.

Instructions

  1. Read manifests, locks, config, adapters, routes, workflows, logs, dashboards, tests, and runbooks.
  2. Glob and Grep for JWT, /sensei/cutout, Lightroom Firefly Services, client-side secrets, fixed quotas, and hardcoded job routes.
  3. Trace auth ownership, product profiles, versions, signed URLs, async states, retries, events, workspaces, and cleanup.
  4. Classify each finding as obsolete, unsafe, brittle, undocumented, environment-specific, or stale evidence.
  5. Propose the smallest compatible correction with tests, canary, rollback, and named owner.
  6. Edit only approved repository artifacts, rerun gates, and record unresolved external dependencies.

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

Read-only review needs no mutation authority. Credential/profile changes, production calls, deploys, replays, registration changes, and deletion require separate explicit approval.

Error Handling

  • Do not replace one remembered constant with another.
  • Do not infer a product from a similarly named Adobe API.
  • Do not auto-fix secrets without coordinated rotation and revocation.

Output

Return findings with file/line evidence, current sources, severity, correction, test, owner, and unresolved risks. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Find a retired endpoint in code and documentation.
  • Find a status URL reconstructed from jobId instead of response evidence.

Validation

Exercise and record expected and observed results for:

  • JWT
  • Photoshop v1
  • Lightroom EOL
  • client secret
  • fixed limit
  • forged event

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 an auditing framework designed to identify security vulnerabilities and deprecated features in Adobe integrations. It establishes strong safety boundaries, including explicit approval requirements for mutations and clear instructions for data redaction during analysis.

  • 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
<repository> <services> <environment>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "review"
]
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-known-pitfalls