spk-admin-dashboard

Open and manage the Spec Kitty localhost dashboard daemon with lifecycle validation.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-admin-dashboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-admin-dashboard
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-admin-dashboard
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-admin-dashboard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents agents from blindly trusting stale dashboard metadata by validating the Spec Kitty localhost daemon's project, token, health, and PID state before exposing its URL.

Core Features & Use Cases

  • Validated Dashboard Launch: Runs spec-kitty dashboard --open so lifecycle checks confirm project identity, token, health, and daemon state before showing a URL.
  • Metadata Diagnostics: Treats .kittify/.dashboard (URL, port, token, PID) as diagnostic data only, never as a trusted source without validation.
  • Daemon Control: Uses --json for machine-readable mission registry rows and --kill to stop the project daemon and clear stale metadata.
  • Use Case: When a user asks for the dashboard URL, run the open command, confirm the daemon is healthy, and only then present the localhost address.

Quick Start

Ask the assistant to open the Spec Kitty dashboard and show its validated localhost URL for the current project.

Frequently Asked Questions about spk-admin-dashboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open the Spec Kitty dashboard?

Run spec-kitty dashboard --open to start or locate the local daemon and open the browser. The command validates project identity, token, health, and daemon state before showing the URL.

How do I stop the Spec Kitty dashboard daemon?

Run spec-kitty dashboard --kill to stop the project daemon and clear the .kittify/.dashboard metadata file. Use this only when the user explicitly asks to stop the dashboard.

What is stored in the .kittify/.dashboard file?

The file holds dashboard metadata with two required lines (URL and port) and two optional lines (token and PID). It should be treated as diagnostic data only, not as a trusted source for the dashboard URL.

Why should I not trust the recorded dashboard URL directly?

Recorded metadata can be stale if the daemon stopped, the port changed, or the PID is dead. Always run spec-kitty dashboard --open so lifecycle validation confirms health, project, and token before showing the URL.

How do I get dashboard data in machine-readable format?

Use spec-kitty dashboard --json to print the mission registry as JSON. This command does not start the server, so it is safe for scripting and status checks.