adobe-deploy-integration
Deploy Adobe-powered applications to Vercel, Cloud Run, and Adobe App Builder with proper credential injection and health monitoring. Use when deploying Adobe API integrations to production platforms. Trigger with phrases like "deploy adobe", "adobe Vercel", "adobe Cloud Run", "adobe App Builder deploy", "adobe production deploy".
Best use case
adobe-deploy-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deploy Adobe-powered applications to Vercel, Cloud Run, and Adobe App Builder with proper credential injection and health monitoring. Use when deploying Adobe API integrations to production platforms. Trigger with phrases like "deploy adobe", "adobe Vercel", "adobe Cloud Run", "adobe App Builder deploy", "adobe production deploy".
Teams using adobe-deploy-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/adobe-deploy-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How adobe-deploy-integration Compares
| Feature / Agent | adobe-deploy-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deploy Adobe-powered applications to Vercel, Cloud Run, and Adobe App Builder with proper credential injection and health monitoring. Use when deploying Adobe API integrations to production platforms. Trigger with phrases like "deploy adobe", "adobe Vercel", "adobe Cloud Run", "adobe App Builder deploy", "adobe production deploy".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Adobe Deploy Integration
## Overview
Deploy Adobe-powered applications to three platforms: Vercel (serverless), Google Cloud Run (containers), and Adobe App Builder (native Adobe Runtime). Each with proper OAuth credential management.
## Prerequisites
- Adobe OAuth Server-to-Server credentials for production
- Platform CLI installed (`vercel`, `gcloud`, or `aio`)
- Application tested in staging environment
## Instructions
### Option A: Adobe App Builder (Native Adobe Hosting)
App Builder deploys serverless Runtime actions directly to Adobe infrastructure:
```bash
# Login to Adobe I/O CLI (requires IMS auth since AIO CLI v11)
aio login
# Select your project and workspace
aio console project select
aio console workspace select Production
# Deploy all actions, static assets, and event registrations
aio app deploy
# Check deployed actions
aio runtime action list
# View action logs
aio runtime activation list --limit 10
aio runtime activation logs <activationId>
```
```javascript
// app.config.yaml — App Builder configuration
application:
actions: actions
web: web-src
runtimeManifest:
packages:
my-adobe-app:
actions:
process-image:
function: actions/process-image/index.js
runtime: nodejs:20
inputs:
ADOBE_CLIENT_ID: $ADOBE_CLIENT_ID
ADOBE_CLIENT_SECRET: $ADOBE_CLIENT_SECRET
annotations:
require-adobe-auth: true
final: true
```
### Option B: Vercel Deployment
```bash
# Set Adobe credentials as Vercel environment variables
vercel env add ADOBE_CLIENT_ID production
vercel env add ADOBE_CLIENT_SECRET production
vercel env add ADOBE_SCOPES production
# Deploy
vercel --prod
```
```json
// vercel.json
{
"functions": {
"api/**/*.ts": {
"maxDuration": 60
}
},
"env": {
"ADOBE_CLIENT_ID": "@adobe_client_id",
"ADOBE_CLIENT_SECRET": "@adobe_client_secret",
"ADOBE_SCOPES": "@adobe_scopes"
}
}
```
```typescript
// api/firefly/generate.ts — Vercel serverless function
import type { VercelRequest, VercelResponse } from '@vercel/node';
import { getAccessToken } from '../../src/adobe/client';
export default async function handler(req: VercelRequest, res: VercelResponse) {
if (req.method !== 'POST') return res.status(405).end();
try {
const token = await getAccessToken();
const fireflyResponse = await fetch(
'https://firefly-api.adobe.io/v3/images/generate',
{
method: 'POST',
headers: {
'Authorization': `Bearer ${token}`,
'x-api-key': process.env.ADOBE_CLIENT_ID!,
'Content-Type': 'application/json',
},
body: JSON.stringify(req.body),
}
);
const result = await fireflyResponse.json();
return res.status(fireflyResponse.status).json(result);
} catch (error: any) {
return res.status(500).json({ error: error.message });
}
}
```
### Option C: Google Cloud Run
```bash
# Store credentials in Secret Manager
echo -n "${ADOBE_CLIENT_ID}" | gcloud secrets create adobe-client-id --data-file=-
echo -n "${ADOBE_CLIENT_SECRET}" | gcloud secrets create adobe-client-secret --data-file=-
# Build and deploy
gcloud builds submit --tag gcr.io/${PROJECT_ID}/adobe-service
gcloud run deploy adobe-service \
--image gcr.io/${PROJECT_ID}/adobe-service \
--region us-central1 \
--platform managed \
--set-secrets="ADOBE_CLIENT_ID=adobe-client-id:latest,ADOBE_CLIENT_SECRET=adobe-client-secret:latest" \
--set-env-vars="ADOBE_SCOPES=openid,AdobeID,firefly_api" \
--min-instances=1 \
--timeout=60s
```
### Health Check Endpoint (All Platforms)
```typescript
// api/health.ts
export async function GET() {
const checks: Record<string, any> = {};
// Test Adobe IMS token generation
try {
const start = Date.now();
const token = await getAccessToken();
checks.adobe = {
status: 'healthy',
latencyMs: Date.now() - start,
tokenLength: token.length,
};
} catch (error: any) {
checks.adobe = {
status: 'unhealthy',
error: error.message,
};
}
const overall = Object.values(checks).every(
(c: any) => c.status === 'healthy'
) ? 'healthy' : 'degraded';
return Response.json({
status: overall,
services: checks,
timestamp: new Date().toISOString(),
});
}
```
## Output
- Application deployed to chosen platform
- Adobe credentials injected via platform secret management
- Health check endpoint validates IMS connectivity
- Serverless function timeout configured for Adobe API latency
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| `aio app deploy` auth error | Not logged in to AIO CLI | Run `aio login` |
| Vercel function timeout | Adobe API takes > 10s | Increase `maxDuration` in vercel.json |
| Cloud Run cold start timeout | Token generation on cold start | Set `min-instances=1` |
| Secret not found | Wrong secret name | Verify with `gcloud secrets list` or `vercel env ls` |
## Resources
- [Adobe App Builder Deployment](https://developer.adobe.com/app-builder/docs/guides/app_builder_guides/deployment/deployment)
- [Vercel Environment Variables](https://vercel.com/docs/environment-variables)
- [Cloud Run Secrets](https://cloud.google.com/run/docs/configuring/services/secrets)
## Next Steps
For webhook handling, see `adobe-webhooks-events`.Related Skills
running-integration-tests
Execute integration tests validating component interactions and system integration. Use when performing specialized testing. Trigger with phrases like "run integration tests", "test integration", or "validate component interactions".
research-to-deploy
Researches infrastructure best practices and generates deployment-ready configurations, Terraform modules, Dockerfiles, and CI/CD pipelines. Use when the user needs to deploy services, set up infrastructure, or create cloud configurations based on current best practices. Trigger with phrases like "research and deploy", "set up Cloud Run", "create Terraform for", "deploy this to AWS", or "generate infrastructure configs".
workhuman-deploy-integration
Workhuman deploy integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman deploy integration".
workhuman-ci-integration
Workhuman ci integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman ci integration".
wispr-deploy-integration
Wispr Flow deploy integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr deploy integration".
wispr-ci-integration
Wispr Flow ci integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr ci integration".
windsurf-ci-integration
Integrate Windsurf Cascade workflows into CI/CD pipelines and team automation. Use when automating Cascade tasks in GitHub Actions, enforcing AI code quality gates, or setting up Windsurf config validation in CI. Trigger with phrases like "windsurf CI", "windsurf GitHub Actions", "windsurf automation", "cascade CI", "windsurf pipeline".
webflow-deploy-integration
Deploy Webflow-powered applications to Vercel, Fly.io, and Google Cloud Run with proper secrets management and Webflow-specific health checks. Trigger with phrases like "deploy webflow", "webflow Vercel", "webflow production deploy", "webflow Cloud Run", "webflow Fly.io".
webflow-ci-integration
Configure Webflow CI/CD with GitHub Actions — automated CMS validation, integration tests with test tokens, and publish-on-merge workflows. Use when setting up automated testing or CI pipelines for Webflow integrations. Trigger with phrases like "webflow CI", "webflow GitHub Actions", "webflow automated tests", "CI webflow", "webflow pipeline".
vercel-deploy-preview
Create and manage Vercel preview deployments for branches and pull requests. Use when deploying a preview for a pull request, testing changes before production, or sharing preview URLs with stakeholders. Trigger with phrases like "vercel deploy preview", "vercel preview URL", "create preview deployment", "vercel PR preview".
vercel-deploy-integration
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies. Use when deploying to production, configuring deployment regions, or setting up blue-green deployment patterns on Vercel. Trigger with phrases like "deploy vercel", "vercel production deploy", "vercel promote", "vercel rollback", "vercel regions".
veeva-deploy-integration
Veeva Vault deploy integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva deploy integration".