← ClaudeAtlas

rudder-setuplisted

Takes an app from no analytics to one real event delivered to a destination the user picks, with the pipeline as rudder-cli specs in git. Use when the user says "set up RudderStack", "onboard" or "send my first event", or when the RudderStack Get started card or plugin sent them here.
rudderlabs/rudder-agent-skills · ★ 19 · AI & Automation · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# Set up RudderStack in this project Done means one real event reached the destination the user chose. The app sends it, or curl does when there is no app here. The destination's delivery count proves it, and so does the payload at the destination when the user can read it there. The pipeline exists as specs in `rudder/` and every change is committed, so `git revert` followed by `rudder-cli apply` undoes it. The user makes three decisions: the plan (what to learn and which events), where events go, and whether to apply the specs. ## When to use - The user asks to set up RudderStack, add analytics, or send a first event, in a repository you can edit. - The user pasted the prompt from RudderStack's Get started card, or ran the onboarding command of the RudderStack plugin. - Best started in the app that will send events. Started in an empty folder, the home folder or a folder of several repositories, step 1 recommends starting again in the app, and can instead continue with a first event sent by curl. - Not for a workspace that already has CLI-managed resources from another project. Step 2 stops in that case. ## Before you start - **rudder-cli**: check with `rudder-cli --version`. If missing, install with `d=$(mktemp -d) && curl -fsSL https://github.com/rudderlabs/rudder-iac/releases/latest/download/install.sh -o "$d/install.sh" && sh "$d/install.sh"`. The command downloads the installer into a new temporary folder, then runs that file; do not pipe it into a shell. It is th