Download for MacApple silicon, macOS 14+
Skill

event-description-generator

@amplitude Updated 2026-10-22

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

With your agent

Install OMGSkills skill "amplitude/mcp-marketplace:plugins/amplitude-experimental/skills/event-description-generator" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/amplitude/mcp-marketplace /tmp/mcp-marketplace && ln -s /tmp/mcp-marketplace/plugins/amplitude-experimental/skills/event-description-generator ~/.claude/skills/event-description-generator

From README

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 Resolve project input (projectId or project name) Create a run ID with short git SHA ( - ) Create run directories under runs/ Determine cursor plan (cursorStart, maxEvents, chunk size) Spawn event-descriptions-worker subagents for cursor chunks Collect worker summaries + output paths Compress the run into a single CSV Report concise progress and next cursor Execution Rules Keep this skill as a dispatcher; the worker does the heavy lifting. Do not call seteventmetadata 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.