adobe-ci-integration
Build deterministic CI gates for Adobe adapters without giving fork jobs credentials or spending against live creative/document APIs
Install / Use
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-ci-integrationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of adobe-ci-integration
adobe-ci-integration scores 83/100 on our quality scale, 598th of 746 Operations skills we index.
Its SKILL.md is 3.9 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.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so adobe-ci-integration 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 foundOur 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-ci-integration compared with similar skills
All 4 of these similar skills score higher than adobe-ci-integration; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| adobe-ci-integration (this skill)by jeremylongshore | 83 | 2.8k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install adobe-ci-integration?
- Run
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-ci-integration. The install tabs above show the steps for each supported agent. - Which AI agents does adobe-ci-integration work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is adobe-ci-integration 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-ci-integration still maintained?
- The repository was last updated about 2 months ago, so adobe-ci-integration is actively maintained.
Skill content
View source on GitHubname: adobe-ci-integration description: >- Build deterministic CI gates for Adobe adapters without giving fork jobs credentials or spending against live creative/document APIs. Use when testing integration changes. Trigger with "test Adobe in CI", "Adobe contract tests", or "gate Adobe deploy". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<repository> <services> <trusted-lane>" version: 1.8.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags: [saas, adobe, ci] model: inherit effort: high compatibility: "Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval"
Adobe Contract-Safe CI
Overview
Build deterministic CI gates for Adobe adapters without giving fork jobs credentials or spending against live creative/document APIs. 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
Pull requests can prove routes, headers, schemas, polling, redaction, EOL bans, errors, and retries offline. Live tests require a protected trusted branch, non-production project/workspace, synthetic fixtures, strict budget, and explicit mutation/cleanup boundaries. Recheck the dated evidence map before relying on mutable product behavior.
Authentication
Fork and untrusted PR jobs receive no secrets. Protected lanes use environment-scoped credentials and record aliases only; secret canaries gate artifacts and logs.
Instructions
- Map CI trust boundaries, service adapters, fixtures, secret sources, deploy workflows, and fork behavior.
- Add offline request/response contracts for auth, async URLs, PDF assets, webhooks, errors, throttling, and EOL endpoints.
- Separate untrusted PR jobs from protected credentialed smoke and deploy jobs.
- Use synthetic inputs, transaction/generation ceilings, serialized jobs, and deterministic cleanup in any live lane.
- Gate on secret scans, obsolete-route scans, negative cases, generated-file checks, and immutable artifact identity.
- Treat skipped trusted tests as unknown and retain redacted receipts plus cleanup evidence.
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
Repository and sandbox owners approve trusted live lanes; security approves secret access; product and budget owners approve any upload, generation, write, deploy, or deletion.
Error Handling
- A 429 is not an acceptable successful assertion.
- Never auto-update fixtures from live customer data.
- Fail if a fork can request a secret-bearing environment.
Output
Return the trust matrix, fixtures, gates, commands, live boundary, secret evidence, cleanup, and owners. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.
Examples
- Prove a fork job has no Adobe secrets.
- Reject JWT, /sensei/cutout, and Lightroom Firefly Services routes statically.
Validation
Exercise and record expected and observed results for:
- fork isolation
- secret canary
- contract drift
- 429
- obsolete route
- 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
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
