---
name: adobe-hello-world
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<product-api> <sandbox> <proof-operation>"
version: 1.8.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
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"
title: adobe-hello-world
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adobe-hello-world
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adobe-hello-world/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/adobe-hello-world`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/adobe-hello-world`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/adobe-hello-world) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/adobe-hello-world`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/adobe-hello-world --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/adobe-hello-world --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/adobe-hello-world/references/official-docs.md) — recheck dated Adobe sources before execution.
- Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.
