Day Zero · Aug 25–26, then TBD
16 skills,
free to take.
Every mechanical piece of the 4-session program, as skill files. Plain markdown with frontmatter — run them in Claude Code, the Codex extension, or anything that reads a skills directory. No account, no signup, no expiry.
Install
The archive is a .claude/skills/ directory and nothing else, so it drops into an existing project without touching anything already there.
curl -fsSLO https://www.shipai.club/skills/day-zero.zip
unzip -o day-zero.zip -d .
rm day-zero.zipWant just one session? Each below has its own bundle, and every skill links to its raw SKILL.md.
By session
/skill-writerSKILL.mdTurn something you keep re-explaining into a skill file you run with one word. Use the second time you type the same instructions.
/content-calendarSKILL.mdBuild a four-week calendar from what the ICP actually asks, kept as a live artifact you update rather than regenerate. Use once voice and ICP exist.
/weekly-reportSKILL.mdPut a short weekly numbers report on a schedule so it arrives without being asked. Use once there are numbers you can actually obtain.
/icp-builderSKILL.mdDefine a B2B ICP tight enough to write one email to, and build the named account list. Use before any outbound.
/outbound-sequenceSKILL.mdWrite cold outbound email that gets replies, plus the follow-up cadence and the graceful no. Use once the account list exists.
/social-postSKILL.mdTurn one thing you actually shipped into platform-native post drafts for X and LinkedIn, in your own voice. Use when there's a real artifact and no post yet.
/site-structureSKILL.mdPlan a marketing site: sections, order, and the job each one does. Use before writing any page copy.
/landing-copySKILL.mdWrite marketing site copy from the positioning brief and apply it to the actual page. Use once the section order exists.
/site-scaffoldSKILL.mdScaffold or extend a Next.js marketing site — routes, metadata, sections. Use when the copy needs somewhere to live.
/content-mapSKILL.mdWork backwards from what the ICP searches to the first twenty pages worth writing. Use before drafting any article.
/programmatic-pagesSKILL.mdDesign a templated page set that is genuinely useful rather than a doorway. Use when one page shape times real data covers many queries.
/og-imageSKILL.mdGenerate Open Graph images so shared links preview properly. Use once routes exist, before anyone shares one.
/perf-passSKILL.mdMeasure Core Web Vitals and fix only what moves a number. Use when the site is deployed and feels slow.
/support-agentSKILL.mdPut a chat agent on the site that answers from your own content and knows when to hand off to a human. Use on the prepared template branch.
/scheduled-workflowSKILL.mdShip one workflow that runs on a schedule and lands its output in a review queue. Use once a routine is worth taking out of the week.
/content-repurposeSKILL.mdCut one published article into an X thread, a LinkedIn post and a newsletter blurb that each read as native. Use once something is actually published.
Questions people ask
Do I have to attend to use these?
No. They're published so anyone can run the process, now or years from now.
Do they only work in Claude Code?
No. They're markdown with frontmatter — anything that reads a skills directory runs them.
Can I change them?
Yes, and you should. They're opinionated on purpose — edit them to fit your product and workflow.
What's the catch?
None. Ship AI is a free community meetup in Phoenix.
Ran one and it did something odd?
Say so in Discord. These files improve on what people hit running them for real.