Getting Started

Quickstart

From buying a kit to your first finished artifact in about five minutes — using SEOKit and the /seo-audit command as the worked example.

This is the fastest path from a fresh purchase to a real deliverable. We use SEOKit and /seo-audit as the example, but the shape is identical for every kit.

The five-minute path

  1. Buy a kit. Pick a plan on pricing and check out. Dodo handles payment and tax as merchant of record.
  2. Your key arrives by email. Within moments you get a license key plus install instructions. (You also get a dashboard login, and you can link your GitHub account from the dashboard for repo access.)
  3. Authenticate the CLI.
  4. Install the kit.
  5. Run a command in Claude Code and collect the artifacts.

1. Install and authenticate

If you have not already installed the CLI, see Installation. Then authenticate with the key from your email:

npm i -g claudekits
ck auth ck_xxxxxxxxxxxxxxxxxxxx
bash

You should see a confirmation listing the kits your license unlocks.

2. Install SEOKit

ck install seokit
bash

The CLI downloads the kit, installs it globally into ~/.claude/, and prints its token ledger as it lands the files. Output looks like this:

✓ Installed seokit v1.0.0 → ~/.claude/
  26 files written.
 
Token ledger
  FILE                              KIND     TOKENS  % OF 200K
  skills/seo-writing/SKILL.md       skill     1,936       1.0%
  skills/seo-data/SKILL.md          skill     1,118       0.6%
  …
  commands/seo-audit.md             command     844       0.4%
 
Total: 16,004 tokens  (8.0% of the 200k context window)
Skill files (SKILL.md) are always-loaded; agents/commands load on demand.

Only the always-loaded portion sits in your context on every turn; commands and agents load on demand when you invoke them. Run ck tokens seokit any time to re-inspect.

3. Run your first audit

Open Claude Code and run the kit's flagship audit command:

/seo-audit https://yourstore.com

On first run the command bootstraps the kit's shared context (it offers to create seo/SITE.md, seo/KEYWORD_MAP.md, and seo/REVENUE.md — the files every other SEO command reads), then walks the site across technical, content, and AI-search surfaces. Everything converges into one readable report — what's broken, why it matters, how to fix it — with the top 3 issues first, and evidence attached to every finding.

4. Collect the artifacts

When the run finishes you have a set of Markdown deliverables written into your project, for example:

  • seo/SITE.md — your site profile: stack, render mode, money-page map.
  • The audit report — findings ranked by impact, each with the concrete fix.
  • seo/KEYWORD_MAP.md — the keyword-to-page map later commands build on.

That is the whole loop: buy → authenticate → install → run → artifacts. Every kit follows it.

Where to go next