Event Description Generator
Orchestrate event description audits by delegating chunk work to the event-descriptions-worker subagent. Resolve a project name to projectId via get_context when needed, then spawn worker subagents over cursors for a bounded run window and write outputs into run-scoped directories. Use when auditing missing event descriptions at scale without doing per-event analysis directly in this skill.
Install
/plugin marketplace add amplitude/mcp-marketplaceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add amplitude/mcp-marketplace --skill event-description-generatorgit clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude-experimental/skills/event-description-generator ~/.claude/skills/event-description-generatorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Event Description Generator Run this skill as an **orchestrator only**. Do not perform per-event filtering, repo search, or description-writing logic in this skill body. Delegate chunk processing to the `event-descriptions-worker` subagent. ## Workflow 1. Resolve project input (`projectId` or project name) 2. Create a run ID with short git SHA (`<projectId>-<sha>`) 3. Create run directories under `runs/` 4. Determine cursor plan (`cursorStart`, `maxEvents`, chunk size) 5. Spawn `event-descriptions-worker` subagents for cursor chunks 6. Collect worker summaries + output paths 7. Compress the run into a single CSV 8. Report concise progress and next cursor ## Execution Rules - Keep this skill as a **dispatcher**; the worker does the heavy lifting. - Do not call `set_event_metadata` from this skill. - Do not manually re-implement worker filtering/search logic here. - Preserve user control over scope (project, cursor range, chunk size, parallelism). ## Prerequisites The user must provide either: - `projectId`, or - project name to resolve. If neither is provided, stop and ask. ## Phase 1: Resolve Project ### 1.1 If `projectId` is provided Use it directly. ### 1.2 If project name is provided Call `get_context` and resolve the name to a single `projectId`. - If exactly one clear match exists, continue with that ID. - If multiple matches exist, ask the user to choose. - Do not choose an ambiguous match on behalf of the user. ### 1.3 If project name is not provided
Details
- Skill name
event-description-generator- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude-experimental/skills/event-description-generator/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Event Description Generator skill do?
Orchestrate event description audits by delegating chunk work to the event-descriptions-worker subagent. Resolve a project name to projectId via get_context when needed, then spawn worker subagents over cursors for a bounded run window and write outputs into run-scoped directories. Use when auditing missing event descriptions at scale without doing per-event analysis directly in this skill.
How do I install the Event Description Generator skill?
Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Event Description Generator popular?
It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.
Related skills
Add Analytics Instrumentation
48amplitude/mcp-marketplace
End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature
Analyze Account Health
48amplitude/mcp-marketplace
Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.
Analyze AI Topics
48amplitude/mcp-marketplace
Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.
Getting Started with Amplitude
48amplitude/mcp-marketplace
First-run onboarding for the Amplitude Grok data-partner bot. Use when a user starts a new session, asks how to connect Amplitude MCP, needs US vs EU residency help, adding Docs MCP, confirming project access, or choosing what to do first with their existing Amplitude data. Trigger on "get started with Amplitude", "connect Amplitude MCP", "Amplitude bot", "help me use Amplitude in Grok", or "what can this bot do with my Amplitude project". Do not use this skill to lead with setup/instrumentation for brand-new orgs — this bot targets existing Amplitude customers.
Economy Mode
45Azure-Samples/agent-skills-dotnet-demo
Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.
Investigate AI Session
48amplitude/mcp-marketplace
Deep-dives into specific AI agent sessions or failure patterns to explain why something went wrong. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when investigating a specific session ID, debugging agent failures, understanding why quality is low, tracing tool errors, or when monitor-ai-quality surfaces an issue that needs root cause analysis.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.