@link.me/cli-linux-arm64 0.2.56 → 0.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@link.me/cli-linux-arm64",
-	"version": "0.2.56",
+	"version": "0.3.1",
 	"description": "Platform binary for @link.me/cli (linux-arm64)",
 	"license": "UNLICENSED",
 	"os": [
@@ -13,6 +13,7 @@
 		"linkme": "./linkme"
 	},
 	"files": [
-		"linkme"
+		"linkme",
+		"skills/**/*"
 	]
 }

package/skills/agents/claude-code/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: linkme_cli_claude_code
+description: Use the Linkme CLI from Claude Code for Linkme profile editing, AP publishing, analytics, links, forms, gallery, automations, email, and merch workflows.
+---
+
+# Linkme CLI for Claude Code
+
+See the canonical **`agents/cli`** skill (`linkme_cli`) for install, authentication, output contracts (`--json`/`--quiet`/human), and the full command-area reference. This file only covers what's specific to running the CLI from Claude Code.
+
+## Claude Code Specifics
+
+- This repo ships a Claude Code plugin (`.claude-plugin/plugin.json` + `.claude-plugin/marketplace.json`) that bundles this whole `skills/` tree and an MCP server (`@link.me/mcp`, binary `linkme-mcp`). If the plugin/MCP server is already installed and enabled, prefer its MCP tools over shelling out to `linkme` — they cover the same commands with structured input/output and no subprocess overhead.
+- If the MCP server is not available, fall back to installing and shelling out to the CLI as described in `agents/cli`.
+- Use the `Bash` tool for CLI invocations and prefer `--json` output when you intend to parse the result programmatically in the same turn.

package/skills/agents/cli/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: linkme_cli
+description: Canonical reference for using the Linkme CLI (`linkme`) to manage Linkme profile editing, AP (Post on All Platforms) publishing, analytics, links, forms, gallery, automations, email, and commerce workflows. Other agent-specific skills point back to this file.
+---
+
+# Linkme CLI
+
+This is the canonical skill for operating the Linkme platform through the `linkme` CLI. The per-agent skills under `agents/` (`claude-code`, `codex`, `cowork`, `openclaw`) are thin pointers to this file — read this one for install, auth, output contracts, and the full area reference, then check the per-agent file only for sandbox-specific notes.
+
+## Install
+
+If `linkme` is missing, install it into a writable local prefix (most agent sandboxes do not have root):
+
+```bash
+mkdir -p /tmp/npm-global
+npm config set prefix /tmp/npm-global
+npm install -g @link.me/cli
+export PATH="/tmp/npm-global/bin:$PATH"
+```
+
+If `PATH` changes do not persist, call the binary directly:
+
+```bash
+/tmp/npm-global/bin/linkme --help
+```
+
+Update later with:
+
+```bash
+npm install -g @link.me/cli@latest
+```
+
+## Authenticate
+
+Use the manual, non-blocking browser flow:
+
+```bash
+linkme auth login --manual
+```
+
+This prints an authorization URL and exits immediately — it does not wait. Share the URL with the user and ask them to open it and approve access. Once they confirm, finish the flow:
+
+```bash
+linkme auth resume
+```
+
+Verify identity:
+
+```bash
+linkme whoami --json
+```
+
+For fully non-interactive contexts (CI, headless), skip the browser flow entirely and set `LINKME_TOKEN` in the environment instead.
+
+## Output Contracts
+
+Every `linkme` command supports three output modes:
+
+- **Human** (default) — optimized for reading, includes tables and formatting
+- **`--quiet`** — emits only the single most useful machine-readable scalar
+- **`--json`** — emits a stable, structured DTO for piping and parsing
+
+Rules of thumb:
+
+- Use `--json` whenever the output will be parsed, filtered, or fed into another step (`| jq ...`).
+- Use `--quiet` when you only need one id, count, or status value.
+- Use human output for the final summary shown to the user.
+- Discover flags and subcommands with `--help` before acting on anything unfamiliar — do not guess a command shape.
+
+## Areas
+
+The authoritative command surface is always `linkme --help`. The table below is a map, not an exhaustive contract:
+
+| Area | Covers |
+|------|--------|
+| `auth` | Login (browser or manual), resume, logout, sessions, profile switching |
+| `ap` | Post on All Platforms: `accounts`, `connect`/`disconnect`, `upload`, `limits`, `analytics` |
+| `ap post` | `create`, `list`, `calendar`, `status`, `watch`, `insights`, `comments`, `publish`, `cancel`, `retry`, `reschedule` |
+| `profile` | View/edit profile, `theme`, `sections`, `contact`, `forms`, `events`, `bands-in-town`, `video`, `pixels`, `linkme-icon`, `deeplink`, `add-to-contacts` |
+| `links` | Custom + platform links: `list`, `add`, `edit`, `delete`, `reorder`, `set <platform> <url>` / `unset <platform>`, `schedule` |
+| `featured` | Featured links, `headers`, `multilinks` |
+| `gallery` | Upload, list, delete, reorder gallery media |
+| `automations` | Instagram automations: connection, authorize, config, posts, create/update/publish, metrics/analytics/monitor |
+| `courses` | Author courses and lesson video uploads |
+| `contacts` | Collected contacts and stats |
+| `search` | Search Linkme users by username or name |
+| `username` | Check username validity/availability |
+| `waitlist` | Check/join gated feature waitlists |
+| `email` | Templates, sending domains, send/test, history, detail, cancel, upload-image |
+| `analytics` | Overview, visits, links, geo, realtime |
+| `commerce` | Digital products/orders (`products`), print-on-demand merch (`merch`) |
+| `shop` | Physical/storefront products and categories |
+| `agency` | Create agencies, invite/manage members, switch managed-user context |
+| `feeds` | Subscribe to and poll provider feeds |
+| `reviews` | Subscribe to and inspect review sources |
+| `upgrade` | Generate Linkme Pro upgrade links |
+| `config` | Show/set/reset CLI configuration and profiles |
+| `whoami` | Current identity |
+| `skill` | List/inspect bundled agent skills (this file included) |
+
+Note: there is no top-level `social` area. Social network links live under `links` (`links set <platform> <url>`, `links unset <platform>`, and `links list` shows both custom and platform links).
+
+## Discovery Pattern
+
+```bash
+linkme --help
+linkme <area> --help
+linkme <area> <subcommand> --help
+```
+
+Start broad, then drill into the specific area for the task at hand rather than memorizing flags.
+
+## Good Defaults
+
+- **Read before you write.** For profile-improvement tasks, inspect current state first: `profile`, `links list`, `featured list`, `gallery list`, `profile sections`, `profile theme`, `profile forms`.
+- **Publishing flow.** Connect accounts (`ap connect <provider>`) → create the post (`ap post create`) → confirm with `ap post status <id>` or stream with `ap post watch <id>`.
+- **Reporting flow.** Request `--json`, extract fields with `jq`, and summarize the numbers for the user in human language.
+- **Re-read after high-impact writes** (deletes, publishes, schedule changes) to confirm the change landed.

package/skills/agents/codex/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: linkme_cli_codex
+description: Use the Linkme CLI from Codex to manage profile content, links, AP publishing, analytics, automations, email, forms, gallery, and commerce workflows.
+---
+
+# Linkme CLI for Codex
+
+See the canonical **`agents/cli`** skill (`linkme_cli`) for install, authentication, output contracts (`--json`/`--quiet`/human), and the full command-area reference. This file only covers what's specific to running the CLI from Codex.
+
+## Codex Specifics
+
+- Codex sandboxes commonly restrict network access by default. Installing `@link.me/cli` via `npm install -g` and any `linkme` command that talks to the Linkme API requires network approval — request it explicitly rather than assuming it is already granted.
+- Prefer non-interactive flags over prompts: use `linkme auth login --manual` + `linkme auth resume` instead of the default interactive browser flow, and use `--json`/`--quiet` instead of relying on TTY-formatted human output.
+- Codex does not have a bundled MCP integration for this CLI — always invoke `linkme` as a subprocess.

package/skills/agents/cowork/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: linkme_cli_cowork
+description: Use the Linkme CLI from Cowork to manage Linkme profiles, links, publishing, analytics, forms, gallery, email, automations, and shop workflows.
+---
+
+# Linkme CLI for Cowork
+
+See the canonical **`agents/cli`** skill (`linkme_cli`) for install, authentication, output contracts (`--json`/`--quiet`/human), and the full command-area reference. This file only covers what's specific to running the CLI from Cowork.
+
+## Cowork Specifics
+
+- Cowork sandboxes usually do not have root, so always install to a local prefix (`npm config set prefix /tmp/npm-global`) as described in `agents/cli`. The executable is `linkme`, not `link.me`.
+- Cowork sessions may not persist `PATH` changes across separate task invocations — call `/tmp/npm-global/bin/linkme` directly if a fresh task can't find `linkme` on `PATH`.
+- For publishing workflows, always verify the final state with `linkme ap post status <id>` or `linkme ap post watch <id>` before reporting success to the user.

package/skills/agents/openclaw/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: linkme_cli_openclaw
+description: Use the Linkme CLI from OpenClaw to manage profiles, publishing, analytics, links, forms, gallery, automations, email, and commerce workflows.
+---
+
+# Linkme CLI for OpenClaw
+
+See the canonical **`agents/cli`** skill (`linkme_cli`) for install, authentication, output contracts (`--json`/`--quiet`/human), and the full command-area reference. This file only covers what's specific to running the CLI from OpenClaw.
+
+## OpenClaw Specifics
+
+- Login is a strictly two-step manual flow in OpenClaw sandboxes: run `linkme auth login --manual`, hand the printed URL to the user, wait for their confirmation, then run `linkme auth resume`. Do not background the login step or attempt to poll for completion any other way.
+- If `PATH` changes from the local-prefix install do not persist, call `/tmp/npm-global/bin/linkme` directly.
+- If a command changes state (delete, publish, reorder), confirm success from the command's own output or by re-reading the affected resource — do not assume success from a zero exit code alone when reporting back to the user.

package/skills/ap/create-post/SKILL.md

@@ -0,0 +1,134 @@
+---
+name: linkme_ap_create_post
+description: Create and publish a Post on All (AP) post with the Linkme CLI. Use when the user wants to upload one short-form video, target connected social platforms, check processing or publish status, or wait until publishing completes.
+---
+
+# AP Create Post
+
+## When To Use
+
+Use this skill when the user wants to publish one video across AP-connected platforms such as YouTube, TikTok, Instagram, Facebook, X, Threads, LinkedIn, or Snapchat.
+
+## Preconditions
+
+- The user must already be authenticated with `linkme`.
+- At least one AP provider account must be connected.
+
+Check connected accounts first:
+
+```bash
+linkme ap accounts
+```
+
+If no account is connected, connect one provider at a time:
+
+```bash
+linkme ap connect youtube
+linkme ap connect instagram
+linkme ap connect tiktok
+```
+
+## Core Workflow
+
+### 1. Upload the video if needed
+
+If the user has a local file, upload it and capture the returned R2 key:
+
+```bash
+linkme ap upload ./clip.mp4
+```
+
+The upload command prints a reusable AP video key like `u/42/my-video`.
+
+Skip this step if the user already has an AP R2 key.
+
+### 2. Create the AP post
+
+Create the post with either a local file path or an existing AP R2 key:
+
+```bash
+linkme ap post create \
+  --video ./clip.mp4 \
+  --caption "New drop. Out now." \
+  --platforms youtube,tiktok,instagram
+```
+
+Or with an uploaded key:
+
+```bash
+linkme ap post create \
+  --video u/42/my-video \
+  --caption "New drop. Out now." \
+  --platforms youtube,tiktok,instagram
+```
+
+Optional scheduling:
+
+```bash
+linkme ap post create \
+  --video u/42/my-video \
+  --caption "Tonight at 8." \
+  --platforms youtube,tiktok \
+  --schedule 2026-04-23T20:00:00Z
+```
+
+Optional TikTok privacy:
+
+```bash
+linkme ap post create \
+  --video u/42/my-video \
+  --caption "Behind the scenes" \
+  --platforms tiktok \
+  --tiktok-privacy PUBLIC_TO_EVERYONE
+```
+
+### 3. Inspect the post snapshot
+
+After creation, check the current state:
+
+```bash
+linkme ap post status <post-id>
+```
+
+Use this for a one-shot summary of media processing, per-platform target state, published URLs, and errors.
+
+### 4. Watch live progress
+
+To stream live updates until the post is fully published:
+
+```bash
+linkme ap post watch <post-id>
+```
+
+`watch` is the live command. It exits automatically once the post reaches fully published state.
+
+### 5. Publish immediately if needed
+
+If the post exists but still needs to be pushed now:
+
+```bash
+linkme ap post publish <post-id>
+```
+
+Then re-check with:
+
+```bash
+linkme ap post status <post-id>
+linkme ap post watch <post-id>
+```
+
+## Operating Rules
+
+- Prefer `linkme ap accounts` before creating a post if provider connectivity is unclear.
+- Prefer `linkme ap upload <file>` first when the same video may be reused.
+- Prefer `linkme ap post status <id>` for a one-shot answer.
+- Prefer `linkme ap post watch <id>` when the user wants to wait through processing and publishing.
+- Use `--json` when another tool needs structured output.
+
+## Minimal Happy Path
+
+```bash
+linkme ap upload ./launch.mp4
+linkme ap post create --video u/42/launch --caption "Shipping today" --platforms youtube,tiktok,instagram
+linkme ap post watch <post-id>
+```

package/skills/automations/instagram/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: linkme_automations_instagram
+description: Use when you need to connect Instagram, inspect posts and automations, or create, update, publish, and monitor Linkme Instagram automations from the CLI.
+---
+
+# Instagram Automations
+
+Use `linkme automations` for Instagram comment and DM automations.
+
+## Quick checks
+
+- `linkme whoami`
+- `linkme automations --help`
+- `linkme automations connection`
+- `linkme automations config`
+
+## Connect Instagram
+
+- Start OAuth: `linkme automations authorize`
+- Finish the callback after approval: `linkme automations callback --code "<code>" --state "<state>"`
+- Disconnect the current Instagram account: `linkme automations disconnect`
+
+## Inspect posts and automations
+
+- List available Instagram posts: `linkme automations posts --limit 20`
+- List automations: `linkme automations list --status active --limit 25`
+- Filter further when needed: `--search`, `--trigger-mode`, `--automation-type`, `--start-date`, `--end-date`
+- Inspect one automation: `linkme automations get <automation-id>`
+- Add `--json` when another tool needs structured output
+
+## Create and publish
+
+- Prefer `--file` for repeatable drafts and `--json` for inspection
+- Create from flags:
+
+```bash
+linkme automations create \
+  --name "Spring DM" \
+  --type comment \
+  --post 1234567890 \
+  --trigger-mode keywords \
+  --keyword spring \
+  --auto-reply \
+  --reply "Check your DMs" \
+  --dm-text "Here is the link" \
+  --dm-link-label "Open" \
+  --dm-link-url "https://link.me/you"
+```
+
+- Create from a spec file: `linkme automations create --file ./automation.json`
+- Update a draft: `linkme automations update <automation-id> --file ./automation.json`
+- Publish a draft: `linkme automations publish <automation-id>`
+- Duplicate an automation: `linkme automations duplicate <automation-id>`
+- Deactivate a live automation: `linkme automations deactivate <automation-id>`
+- Delete an automation: `linkme automations delete <automation-id>`
+
+## Monitor performance
+
+- Current metrics: `linkme automations metrics <automation-id>`
+- Poll metrics: `linkme automations monitor <automation-id> --interval 10 --count 12`
+- Per-automation link analytics: `linkme automations analytics <automation-id> --start-date 2026-04-01 --end-date 2026-04-30`
+- Dashboard totals: `linkme automations dashboard-stats`
+- Dashboard link analytics: `linkme automations dashboard-link-analytics --timezone UTC`
+
+## Working rules
+
+- If the payload shape is unclear, start with `linkme automations <subcommand> --help`
+- Before mutating, inspect existing drafts with `linkme automations list --json` or `linkme automations get <id> --json`

package/skills/commerce/merch/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: linkme_commerce_merch
+description: Use when you need to inspect merch templates or manage merch categories from the Linkme CLI.
+---
+
+# Merch
+
+Use `linkme commerce merch` for merch templates and category housekeeping.
+
+## Quick checks
+
+- `linkme whoami`
+- `linkme commerce --help`
+- `linkme commerce merch --help`
+
+## Merch templates
+
+- List templates: `linkme commerce merch list`
+- Structured output: `linkme commerce merch list --json`
+- The current CLI surface is inspect-only for merch templates; create or edit flows are not exposed here
+
+## Merch categories
+
+- List categories: `linkme commerce merch categories`
+- Create a category: `linkme commerce merch categories --create "Apparel"`
+- Delete a category with confirmation bypass: `linkme commerce merch categories --delete 8 --force`
+- Without `--force`, deletion prompts for confirmation
+- Add `--json` when another tool needs the raw category payload
+
+## Discovery
+
+- If the user wants broader commerce features, inspect `linkme commerce products --help`
+- If the user wants actual storefront products or categories, inspect `linkme shop products --help` and `linkme shop categories --help`
+- If the exact flag shape is unclear, run `linkme commerce merch <subcommand> --help` first

package/skills/email/lists/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: linkme_email_lists
+description: Use when you need to manage contact-backed email lists, templates, assets, test sends, and campaigns from the Linkme CLI.
+---
+
+# Email Lists And Campaigns
+
+Use `linkme email` for templates, assets, test sends, and campaign delivery. Use `linkme contacts` to inspect the audience behind campaigns.
+
+## Quick checks
+
+- `linkme whoami`
+- `linkme email --help`
+- `linkme contacts --help`
+- `linkme email domains`
+
+## Inspect the audience
+
+- Contact summary: `linkme contacts stats`
+- Paginated contacts: `linkme contacts list --page 1 --limit 50`
+- Use `--json` if you need structured contact data for follow-up steps
+
+## Templates and assets
+
+- List templates: `linkme email templates list`
+- Filter by category: `linkme email templates list --category onboarding`
+- Create from HTML file:
+
+```bash
+linkme email templates create \
+  --name "April Newsletter" \
+  --subject "April updates" \
+  --file ./newsletter.html \
+  --category newsletter
+```
+
+- Create from inline HTML: `linkme email templates create --name "Welcome" --subject "Hello" --body "<h1>Hi</h1>" --category onboarding`
+- Delete a template: `linkme email templates delete <template-id> --force`
+- Upload an image for template HTML: `linkme email upload-image ./hero.png`
+
+## Test and send
+
+- Send a test email: `linkme email test --to fan@example.com --template tmpl_123 --from news.example.com`
+- Send to all active contacts: `linkme email send --template tmpl_123 --from news.example.com --audience all`
+- Send to specific recipient ids: `linkme email send --template tmpl_123 --from news.example.com --audience ids --recipient-ids "1,2,3"`
+- Schedule a campaign: `linkme email send --template tmpl_123 --from news.example.com --audience all --schedule 2026-05-01T15:00:00Z`
+- Override the subject line: add `--subject "Flash sale"`
+
+## Track and control campaigns
+
+- Campaign history: `linkme email history --page 1 --limit 25`
+- Campaign detail: `linkme email detail <campaign-id>`
+- Cancel a scheduled campaign: `linkme email cancel <campaign-id>`
+
+## Working rules
+
+- If multiple verified domains exist, pass `--from`
+- If a command shape is unclear, run `linkme email <subcommand> --help` first
+- Prefer `--json` for agent-to-agent handoff or downstream parsing

package/skills/profile/make-it-look-good/SKILL.md

@@ -0,0 +1,311 @@
+---
+name: linkme_profile_make_it_look_good
+description: Polish a Linkme profile with the Linkme CLI. Use when the user wants to improve profile presentation, especially featured links, links, social links, gallery, sections, theme, and high-conversion profile modules.
+---
+
+# Make Profile Look Good
+
+## When To Use
+
+Use this skill when the user wants their Linkme profile to look cleaner, more complete, and more conversion-focused from the CLI.
+
+This skill is grounded in the current Linkme CLI surface. The main profile polish surface is not just `linkme profile`. It also includes `linkme featured`, `linkme links`, and `linkme gallery`.
+
+## Start Here
+
+Inspect the current profile and public content first:
+
+```bash
+linkme profile view
+linkme featured list
+linkme links list
+linkme gallery list
+linkme profile sections list
+```
+
+## Core Polish
+
+### Featured links first
+
+Featured links are usually the most important conversion surface on a Linkme profile. Treat them as the main polish step unless the user asked for something narrower.
+
+What to do:
+
+- make sure the best call-to-action links exist
+- remove weak or outdated featured items
+- reorder featured links so the highest-value destination is first
+- use headers or multilinks when they improve structure
+
+Commands:
+
+```bash
+linkme featured list
+linkme featured add --help
+linkme featured edit --help
+linkme featured reorder --help
+linkme featured headers --help
+linkme featured multilinks --help
+```
+
+### Then polish normal links, socials, and gallery
+
+Use the rest of the public profile surface to support the featured links.
+
+Commands:
+
+```bash
+linkme links list
+linkme links add --help
+linkme links set --help
+linkme links edit --help
+linkme gallery list
+linkme gallery upload --help
+linkme gallery reorder --help
+```
+
+What each area does:
+
+- `featured`: primary calls to action, headers, smart links
+- `links`: broader profile destinations, platform presence, and supporting links
+- `gallery`: visual proof, brand texture, product shots, creator imagery
+
+### Profile edit without unnecessary renaming
+
+Use `profile edit` to improve the first impression, but do not recommend changing `--username` or `--name` by default. Only touch those if the user explicitly asked, is rebranding, or there is a clear correctness issue.
+
+What it controls:
+
+- `--name`: public display name
+- `--username`: public handle
+- `--bio`: short positioning statement
+- `--image`: avatar or brand image
+- `--public-search`: whether the profile can appear in search
+- `--display-name-option`: display style, `user_name` or `brand_logo`
+
+Example:
+
+```bash
+linkme profile edit \
+  --bio "Tour dates, music drops, merch, and fan links in one place." \
+  --image ./avatar.jpg \
+  --public-search \
+  --display-name-option user_name
+```
+
+Default guidance:
+
+- improve bio clarity before changing identity fields
+- improve image quality before renaming anything
+- preserve established username/display name unless the user wants a change
+
+### Theme
+
+Use `profile theme` to create a coherent visual system.
+
+What it controls:
+
+- `--primary`: main text color
+- `--background`: background color
+- `--font`: custom profile font
+
+Example:
+
+```bash
+linkme profile theme \
+  --primary "#F6F1E8" \
+  --background "#111111" \
+  --font "Space Grotesk"
+```
+
+## Presentation Toggles
+
+Use these to control profile chrome and conversion helpers:
+
+- `linkme profile linkme-icon --enable`
+  Shows the Linkme icon on profile.
+- `linkme profile deeplink --enable`
+  Shows the deeplink banner.
+- `linkme profile add-to-contacts --show`
+  Shows the Add to Contacts button.
+- `linkme profile pixels --meta <id> --tiktok <id> --google-analytics <id>`
+  Adds tracking pixels. This requires Linkme Pro.
+
+Example:
+
+```bash
+linkme profile linkme-icon --enable
+linkme profile deeplink --enable
+linkme profile add-to-contacts --show
+linkme profile pixels --meta 1234567890 --tiktok TT-ABC123 --google-analytics G-ABCD1234
+```
+
+## Contact And Section Structure
+
+### Contact info
+
+Use profile contact info for direct conversion paths.
+
+- `email`: business or booking inbox
+- `phone`: booking or support number
+- `website`: canonical site or store
+- `address`: physical location
+
+Commands:
+
+```bash
+linkme profile contact list
+linkme profile contact set email bookings@example.com
+linkme profile contact set website https://example.com
+linkme profile contact set phone "+1 555 123 4567"
+```
+
+### Section visibility and order
+
+Use sections to decide what visitors see first.
+
+Commands:
+
+```bash
+linkme profile sections list
+linkme profile sections enable featured_links
+linkme profile sections enable contact_info
+linkme profile sections enable forms
+linkme profile sections move featured_links 1
+linkme profile sections move forms 2
+linkme profile sections move custom_events 3
+```
+
+Useful section keys exposed by the CLI include:
+
+- `featured_links`
+- `forms`
+- `bandsintown`
+- `custom_events`
+- `gallery`
+- `contact_info`
+- `instagram_videos`
+- `tiktok_videos`
+- `shop`
+- `bio`
+
+## High-Impact Modules
+
+### Custom events
+
+Use custom events when the profile should highlight launches, appearances, or tour stops.
+
+Commands:
+
+```bash
+linkme profile events list
+linkme profile events add \
+  --title "Album Release Show" \
+  --location "Los Angeles, CA" \
+  --starts-at 2026-05-01T20:00:00Z \
+  --ticket-url https://tickets.example.com/release-show \
+  --venue "The Regent" \
+  --pinned
+```
+
+What this module does:
+
+- surfaces time-sensitive events on profile
+- supports pinned events
+- supports sold-out and all-day state
+- supports per-event colors with `--text-color`, `--bg-color1`, `--bg-color2`
+
+### Forms
+
+Use forms for lead capture, waitlists, booking inquiries, or fan signups.
+
+Commands:
+
+```bash
+linkme profile forms list
+linkme profile forms create \
+  --name "VIP Waitlist" \
+  --description "Get first access to tickets and merch." \
+  --field "Name:text:required" \
+  --field "Email:email:required" \
+  --field "City:text:optional" \
+  --text-color "#FFFFFF" \
+  --bg-color-1 "#1F2937" \
+  --bg-color-2 "#111827"
+```
+
+What this module does:
+
+- creates conversion-focused forms directly on profile
+- supports typed fields with required or optional rules
+- supports form theming
+- supports submission review and CSV export
+
+Useful follow-ups:
+
+```bash
+linkme profile forms submissions <form-id>
+linkme profile forms export <form-id>
+```
+
+### Profile video
+
+Use profile video when motion will improve the page header.
+
+Commands:
+
+```bash
+linkme profile video set --file ./intro.mp4 --variation 4 --ping-pong
+```
+
+What this module does:
+
+- uploads a hero-style profile video
+- applies a style variation
+- supports seamless looping with `--ping-pong`
+
+Remove it with:
+
+```bash
+linkme profile video remove
+```
+
+### BandsInTown
+
+Use BandsInTown when the user is an artist and wants live event sync.
+
+Commands:
+
+```bash
+linkme profile bands-in-town show
+linkme profile bands-in-town sync --api-key <bandsintown-api-key> --artist "The Midnight Arcade"
+linkme profile bands-in-town events
+linkme profile bands-in-town colors --text-color "#FFFFFF" --bg-color-1 "#7C3AED" --bg-color-2 "#1D4ED8"
+```
+
+What this module does:
+
+- syncs artist events from BandsInTown
+- exposes synced events on profile
+- updates colors across all synced events
+
+## Recommended Order
+
+1. `linkme profile view`
+2. `linkme featured list`
+3. `linkme links list`, `linkme gallery list`
+4. `linkme profile edit ...` for bio/image/search settings
+5. `linkme profile theme ...`
+6. `linkme profile contact set ...`
+7. `linkme profile forms create ...` or `linkme profile events add ...`
+8. `linkme profile sections move ...`
+9. `linkme profile video set ...`
+
+## Operating Rules
+
+- Start by inspecting the current profile before changing it.
+- Start with featured links and public-facing content before deeper profile modules.
+- Prefer a short, concrete bio over a generic one.
+- Do not recommend changing username or display name unless the user asked or there is a strong reason.
+- Add at least one conversion module: contact info, a form, an event, or profile video.
+- Reorder sections after adding content so the strongest conversion block appears near the top.
+- Use `--json` when another tool needs structured output.