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.
/plugin marketplace add adobe/skillsnpx agentmods add plugins/adobe/skills/project-managementgit 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/plugins/adobe/skills/project-management)<a href="https://agentmods.dev/plugins/adobe/skills/project-management"><img src="https://agentmods.dev/badge/plugins/adobe/skills/project-management.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
aem-project-management 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 2d 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.
What it actually says
{
"name": "aem-project-management",
"version": "1.0.0",
"description": "Project lifecycle management for AEM Edge Delivery Services - handover documentation, PDF generation, and project assistance",
"author": {
"name": "Adobe"
},
"license": "Apache-2.0",
"skills": [
"./skills/handover",
"./skills/handover-author",
"./skills/handover-developer",
"./skills/handover-admin",
"./skills/whitepaper",
"./skills/auth",
"./skills/ops"
],
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/pdf-lifecycle.js\""
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/pdf-lifecycle.js\""
}
]
}
],
"SessionEnd": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/pdf-lifecycle.js\""
}
]
}
]
},
"keywords": [
"adobe",
"aem",
"eds",
"edge-delivery-services",
"project",
"handover",
"documentation",
"whitepaper",
"pdf"
]
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 399 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago First seen · 63 lines scan A dc6927996f1c
aem-project-management is a plugin published in the GitHub repository adobe/skills (177 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
migrate-tool
Generate database migrations and code migration scripts for framework upgrades.
discover
Discover which AI agent to build — map automation outcomes to solvable opportunities, validate assumptions, and decide build vs buy. Use when exploring agent ideas, analyzing automation opportunities, running build-or-buy analysis, or estimating agent development costs.
auth
Auth skills for Claude Code — scaffold hand-rolled auth endpoints and audit auth code against security best practices.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.