SkillAgentSearch skills...

adobe-hello-world

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

Install / Use

npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-hello-world

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Automation

Supported Platforms

Universal

Our assessment of adobe-hello-world

adobe-hello-world scores 83/100 on our quality scale, 2161st of 2,780 Automation skills we index.

Its SKILL.md is 4.0 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.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so adobe-hello-world 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 found

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.

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-hello-world compared with similar skills

All 4 of these similar skills score higher than adobe-hello-world; compare them before choosing.

SkillScoreStarsUpdatedFormat
adobe-hello-world (this skill)by jeremylongshore832.8k53d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install adobe-hello-world?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-hello-world. The install tabs above show the steps for each supported agent.
Which AI agents does adobe-hello-world 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-hello-world 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-hello-world still maintained?
The repository was last updated about 2 months ago, so adobe-hello-world is actively maintained.

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"

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.

Related Skills

View on GitHub
GitHub Stars2.8k
CategoryAutomation
Updated1mo ago
Forks404

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
adobe-hello-world — Universal Skill: Install & Safety Check | SkillAgent