Adobe Skills is a collection of skills, plugins, agents, and MCP servers that extend AI coding agents with workflows for Adobe products and other tasks. Developers use it to help coding agents work with Adobe analytics and application-building tools. The catalogue entries are the repository’s own skills, plugins, agents, and MCP integrations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/adobe/skills/sling-distributionnpx skills add adobe/skills --skill sling-distributiongit clone --depth 1 https://github.com/adobe/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/adobe/skills/sling-distribution)<a href="https://agentmods.dev/skills/adobe/skills/sling-distribution"><img src="https://agentmods.dev/badge/skills/adobe/skills/sling-distribution.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00038 | $0.05022 |
| Opus 5 | $0.00019 | $0.02511 |
| Sonnet 5 | $0.00008 | $0.01004 |
| Haiku 4.5 | $0.00004 | $0.00502 |
Grade A, and why
sling-distribution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 740 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEM Cloud Service Sling Distribution Event Handling
Monitor and react to content distribution lifecycle events using the Sling Distribution API.
When to Use This Skill
Use Sling Distribution event handling for:
- Monitoring distribution lifecycle: Track package creation, queueing, and delivery
- Custom post-distribution actions: Cache warming, notifications, analytics
- Distribution auditing: Log and track all distribution events
- Failure handling: React to dropped packages and distribution failures
- Integration workflows: Trigger external systems after successful distribution
For programmatic publishing, use the Replication API instead.
Official API Documentation
Key Packages:
org.apache.sling.distribution- Core distribution interfacesorg.apache.sling.distribution.event- Event topics and propertiesorg.apache.sling.distribution.queue- Queue monitoring
Understanding Sling Distribution in Cloud Service
What is Sling Distribution?
Sling Distribution is the underlying transport mechanism for content replication in AEM Cloud Service. When you use the Replication API (Replicator.replicate()), Sling Distribution handles:
- Package Creation: Content is assembled into distribution packages
- Queueing: Packages are queued for delivery
- Transport: Packages are sent to Adobe Developer pipeline service
- Import: Target tier imports and applies the content
Architecture Flow
Replication API Call
↓
[AGENT_PACKAGE_CREATED] - Package assembled
↓
[AGENT_PACKAGE_QUEUED] - Package added to queue
↓
[AGENT_PACKAGE_DISTRIBUTED] - Package sent to pipeline
↓
[IMPORTER_PACKAGE_IMPORTED] - Package imported on target tier
OR
[AGENT_PACKAGE_DROPPED] - Package failed and was removed
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 740 lines · 38 tokens per session scan A 7c965e9d82f9
sling-distribution is a skill published in the GitHub repository adobe/skills (177 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 5,022 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
google-cloud-solution-n-tier-serverless-web-app
Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).