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

Prove one Adobe API connection with a current, read-only or synthetic operation and a content-safe receipt. Use during onboarding before any production workflow. Use when the task requires adobe minimal access proof. Trigger with "Adobe hello world", "test Adobe connection", or "verify Adobe entitlement".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

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

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 Minimal Access Proof

Overview

Prove one Adobe API connection with a current, read-only or synthetic operation and a content-safe receipt. 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

The smallest useful proof is product-specific: token acquisition alone does not demonstrate API entitlement. Prefer a documented read or a synthetic asynchronous job whose artifact can be safely deleted; do not use retired Photoshop v1, /sensei/cutout, or Lightroom Firefly Services endpoints. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Use a dedicated non-production credential or consenting test user and record only aliases, scope names, product profiles, response status, and request identifiers.

Instructions

  1. Resolve the exact Adobe organization, project, workspace, credential type, and service.
  2. Read the current product quickstart and identify the least consequential documented proof.
  3. Validate endpoint host, method, request schema, scopes, entitlement, and storage requirements offline.
  4. Run exactly one bounded proof and capture redacted response and correlation evidence.
  5. Verify the expected allow case and one safe denied or invalid fixture without broadening access.
  6. Delete approved temporary assets and issue a pass, fail, or entitlement-blocked result.

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

Require the sandbox and data owners before a live call. Image/document generation, upload, spend, or asset deletion needs explicit approval even in a test environment.

Error Handling

  • Stop if the service is absent from Developer Console.
  • Do not treat a 401, 403, or policy rejection as a reason to guess new scopes.
  • Never use production customer files as a hello-world fixture.

Output

Return the selected proof, current documentation, auth/entitlement aliases, request receipt, negative result, cleanup evidence, and decision. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Verify one authorized synthetic request without exposing the bearer token.
  • Demonstrate that a retired endpoint is rejected by the preflight.

Validation

Exercise and record expected and observed results for:

  • valid proof
  • missing entitlement
  • wrong host
  • invalid fixture
  • timeout
  • cleanup

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 standard boilerplate code for developers to integrate with Adobe's Firefly, PDF Services, and Photoshop APIs. It follows security best practices by using environment variables for credential management and relies on official SDKs from a well-known service provider.

  • 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
<product-api> <sandbox> <proof-operation>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "onboarding"
]
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-hello-world