VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Marketing Kit

/ak:marketing-dashboard

Local Assets, Brand, and Settings dashboard

Operate the local Assets, Brand, and Settings dashboard by treating its dashboard documentation and live skill catalog as the source of truth.

01

Read authority

02

Avoid inference

03

Resolve install

04

Run dashboard

Rule 01

Current dashboard docs beat assumptions

Rule 02

Live installation paths beat hardcoded paths

Rule 03

Report exact printed URLs

Rule 04

Surface SQLite remediation verbatim

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Read authority Read the dashboard README when present because it owns current features, routes, storage, commands, configuration, validation, and troubleshooting.
  2. 2 Avoid inference Do not infer campaign, content-generation, automation, or authentication behavior from the skill name or older versions.
02

Work

Agent / skill execution

  1. 3 Resolve install Resolve the installed skill directory through the runtime's live skill catalog before running referenced scripts.
  2. 4 Run dashboard Use only the commands documented by the dashboard authority for the current installation.
03

Verify

Gate, review, validation

  1. 5 Report URLs Report the URLs printed by the script so the user knows exactly where the local dashboard is running.
  2. 6 Surface fixes If SQLite driver remediation appears, surface it verbatim instead of paraphrasing or hiding it.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:marketing-dashboard [start|stop|status|open]

Arguments

[start|stop|status|open]

Dashboard operation

Optional local dashboard action. Omit it to inspect authority docs and reuse an already running matching process. Do not infer campaign or auth behavior from the name.

/ak:marketing-dashboard status

Subcommands

start Start
/ak:marketing-dashboard start

Start the local dashboard after resolving the installed skill directory and reusing a matching project process when one exists.

Outcome: Dashboard process started or reused, with printed loopback URLs and any SQLite driver remediation quoted verbatim.

/ak:marketing-dashboard start
stop Stop
/ak:marketing-dashboard stop

Stop a dashboard process this skill owns after verifying ownership. Do not kill an unrelated listener on the same port.

Outcome: Owned dashboard process stopped; unrelated port listeners are left untouched.

/ak:marketing-dashboard stop
status Status
/ak:marketing-dashboard status

Inspect whether a matching local dashboard process is running and report PID, port, and printed URLs.

Outcome: Running or not-running status with exact printed URLs, without guessing campaign features.

/ak:marketing-dashboard status
open Open
/ak:marketing-dashboard open

Open or report the live local Assets, Brand, and Settings dashboard using documented loopback URLs.

Outcome: Exact printed dashboard URLs for Assets, Brand, and Settings, taken from the running process or documented start output.

/ak:marketing-dashboard open

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default inspect Recommended 
/ak:marketing-dashboard
Use when:
You need the local Assets, Brand, and Settings dashboard without guessing extra product surfaces.
Expected:
Reads the dashboard README, resolves the installed skill path, reuses a matching process when present, and reports the exact printed loopback URLs.
Start dashboard 
/ak:marketing-dashboard start
Use when:
No matching local dashboard process is running and you need documented start commands.
Expected:
Resolves the live install, starts only documented dashboard scripts, tracks PID and port, and quotes any SQLite driver remediation verbatim.
Stop dashboard 
/ak:marketing-dashboard stop
Use when:
You started the dashboard and now need to stop only the owned process.
Expected:
Verifies ownership before stopping, avoids killing unrelated listeners on the same port, and reports that the owned dashboard process has stopped.
Dashboard status 
/ak:marketing-dashboard status
Use when:
You need to know whether the local dashboard is already running before starting another copy.
Expected:
Inspects existing project processes, reports PID, port, and printed URLs when a match exists, and does not invent campaign or authentication features.
Open dashboard 
/ak:marketing-dashboard open
Use when:
You want the live local dashboard URLs, not a guessed campaign or content-generation surface.
Expected:
Opens or reports the documented loopback URLs for Assets, Brand, and Settings from the running process or start output.

Handled Scope

  • Assets dashboard
  • Brand dashboard
  • Settings dashboard
  • Local script operation
  • SQLite driver troubleshooting

Next