Skills
Operate the local dashboard with ak:dashboard
Start, build, check, or stop the current local Marketing Dashboard while respecting its process, storage, and network boundaries.
Use ak:dashboard as the launcher for the co-packaged local Marketing
Dashboard. Its supported mode tokens are dev (default), build, prod, and
stop; check routes to the status check. The launcher's older feature list is
not current product authority: use ak:marketing-dashboard and its README for
the implemented Assets, Brand, and Settings surface.
Choose the launcher for a local operation
Use ak:dashboard when
- You want to start development mode, build, start production mode, stop, or inspect the local dashboard processes.
- You accept local dependency, build, PID, SQLite, and port effects.
Choose another workflow when
- You need the current routes, storage, or troubleshooting contract. Use
ak:marketing-dashboarddirectly. - You expect campaign management, content generation, automation recipes, or AI endpoints. The current application does not implement them.
- You want cloud deployment or publishing.
prodserves a local build; it does not deploy one.
Prepare the local environment
Resolve the installed ak-marketing-dashboard Skill directory through the
runtime's live catalog. Use Node.js 20 LTS where possible, ensure ports 3457
and 5173 are available, and review existing work under its data, build, and
shared asset paths. First start can run npm install, which writes dependencies
and contacts npm. build writes app/dist/; the server creates
data/marketing.db and PID files.
| Runtime | Invocation | Availability boundary |
|---|---|---|
| Claude Code | /ak:dashboard ... | Can route to packaged scripts when their installed directory is resolved. |
| Cursor | /ak:dashboard ... | Slash invocation is user-verified; shell and process behavior remains environment-specific. |
| Codex | $ak:dashboard ... | Native Skill discovery is supported; script execution still needs local permission and tools. |
Run the Skill
/ak:dashboard dev/ak:dashboard dev$ak:dashboard devUse ak:dashboard check for status, ak:dashboard build before
ak:dashboard prod, and ak:dashboard stop only after checking process
ownership.
Understand the stages
- Resolve the live installed Skill directory and selected mode.
- Review dependency installation, build, network, storage, and process effects.
- Run the matching dashboard script or bounded health check.
- Report the actual URLs, PIDs, health response, and SQLite remediation.
- Stop only the intended processes and verify ports afterward.
Keep process and network approval with you
Local does not mean authenticated or consequence-free
The current server does not enforce API-key authentication. Do not expose it
to an untrusted network. stop.sh falls back to killing processes on ports
3457 and 5173 when saved PID files are unavailable, so verify ownership
before approving that fallback.
Starting does not authorize package installation, logo upload, asset metadata changes, external publishing, provider calls, or spend. Approve each separately.
Verify outputs and evidence
Development should report frontend http://localhost:5173, API
http://localhost:3457, and health http://localhost:3457/health. Production
serves the built app from http://localhost:3457. Record mode, dependency or
build changes, PIDs, health status, and any database error.
Troubleshoot and know the limits
| Symptom | Safe next step |
|---|---|
| Production build missing | Run ak:dashboard build, inspect app/dist/, then request prod. |
| SQLite driver unavailable | From server/, run npm install; prefer Node.js 20 LTS and surface the packaged remediation verbatim. |
| Port is occupied | Identify the owning process before using stop; do not kill an unrelated service. |
| Expected campaign or AI feature is absent | This is current scope, not a startup failure. Use only Assets, Brand, and Settings. |
| Runtime cannot find the Skill | Follow Runtime cannot find a Skill or Agent. |
The launcher guarantees neither dependency installation, port availability, network isolation, nor runtime parity. See Marketing Dashboard and Marketing Kit.
Route a marketing report with ak:analyze
Select a supported analysis type or reporting period, gather approved data, and produce a qualified marketing report.
Browse local assets with ak:marketing-dashboard
Run and inspect the current local Assets, Brand, and Settings dashboard with explicit storage, privacy, and authentication boundaries.