onboarding

An agent skill by coreyhaines31, from coreyhaines31/marketingskills. Tags: analytics, onboarding, optimization, product-strategy, workflow.

What it does

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add coreyhaines31/marketingskills --skill onboarding

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/coreyhaines31/marketingskills
cp -r marketingskills/skills/onboarding ~/.claude/skills/onboarding

Safety box score

Grade A, minimal risk: 4 of 100 risk points, rated 2026-10-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This is a documentation-only onboarding/activation coaching skill: it reads optional local product-marketing context and gives advice about onboarding flows, checklists, empty states, and re-engagement. It ships no executable code, but it does broaden the agent’s reading scope to nearby context files and can steer the agent toward email/outreach recommendations.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	0 (none)	No shell commands, scripts, or code execution are shipped in these files; they are plain markdown references and eval cases.
Network access	0 (none)	The skill only cites external documentation URLs (for example Amplitude) and does not itself download or transmit data.
Filesystem reach	1 (low)	It explicitly tells the agent to read optional local files like `.agents/product-marketing.md`, `.claude/product-marketing.md`, or `product-marketing-context.md` before answering.
Secrets & credentials	0 (none)	There is no instruction to read, paste, or handle tokens, passwords, `.env` files, keychains, or browser sessions.
Privilege & persistence	0 (none)	No sudo, global installs, services, shell startup edits, or OS/git settings changes are requested.
Instruction hijack surface	0 (none)	I found no prompt-injection content that tells the agent to ignore rules, hide things, or follow remote instructions.
Irreversible actions	0 (none)	The skill recommends onboarding emails and human outreach as strategy, but it does not itself send messages, post, pay, book, merge, deploy, or delete anything.
Transparency	0 (none)	There are no binaries, encoded payloads, minified assets, or unpinned installers; everything provided is readable markdown/JSON.

Before installing

Read `skills/onboarding/SKILL.md` and the three reference docs; there is no code to audit, only guidance.
Check whether your environment contains any of `.agents/product-marketing.md`, `.claude/product-marketing.md`, or `product-marketing-context.md` before letting the agent use them.
If you do not want lifecycle-email advice, keep a boundary in place: ask for recommendations only, not drafted outbound messages.
Treat the external Amplitude links as references only; nothing in this skill fetches them automatically.

Rated 2026-10-20 by an automated review of 5 files from the skill's repository.

Source

Repository: coreyhaines31/marketingskills (all skills from this repository)
Path: skills/onboarding/SKILL.md
Branch: main
Collection: marketingskills
Updated: 2026-09-21

paywalls — When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
ab-testing — When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
ads — When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms.
aso — When the user wants to audit or optimize an App Store or Google Play listing.
churn-prevention — When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies.
cro — When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages.