Practitioner-focused agent skills for Adobe Customer Journey Analytics via the CJA MCP server — KPI pulse, top movers, funnel health check, dimension analysis, segment performance comparator, and executive briefing.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Use the CJA MCP server as an analytics copilot: KPI monitoring, funnel and segment analysis, dimension profiling, and executive readouts — all driven from natural-language requests in Claude Code, Cursor, and other MCP clients.
Claude Code:
/plugin marketplace add adobe/skills
/plugin install adobe-cja@adobe-skillsCursor / other MCP clients: Configure the MCP server entry per your environment (see below).
{
"mcpServers": {
"adobe-cja": {
"type": "http",
"url": "https://cja-mcp.adobe.io/mcp"
}
}
}Requests require IMS auth headers (Authorization, x-gw-ims-org-id, x-gw-ims-user-id, etc.); an OAuth proxy may inject these. Include x-data-view-id when required.
This repo's .mcp.json is a template only.
| Skill | Description | Try it |
|---|---|---|
| Monitor & investigate — Skills that track day-to-day KPI movement and dig into unexpected shifts. | ||
| cja-kpi-pulse | KPI digest with period-over-period change, trend direction, and dimension breakdown |
|
| cja-top-movers-watchlist | Ranks dimension items by biggest gain or loss for a metric |
|
| Analyze — Skills that go deeper into a specific question — funnels, dimensions, segment differences. | ||
| cja-funnel-health-check | Step-by-step fallout analysis across a multi-step conversion funnel |
|
| cja-dimension-analysis | Cardinality, distribution, trends, anomalies, and data quality for a dimension |
|
| cja-segment-performance-comparator | Side-by-side KPI comparison across two or more audience segments |
|
| Deliver — Skills that produce stakeholder-ready output, like narrative briefings for leadership and business reviews. | ||
| cja-executive-briefing | Narrative performance summary ready for leadership or QBR |
|
Each skill's SKILL.md contains the trigger description, phased workflow, MCP tool calls, and HTML output templates. Your MCP client routes natural-language requests to the matching skill automatically via the YAML description field.
To add a new skill, create a skills/<skill-id>/SKILL.md following the existing pattern (YAML frontmatter with name/description, phased workflow, MCP tool calls, HTML template). Keep name: stable — it is used for routing.
See the repository CONTRIBUTING.md for the broader contribution process.