Mission Control - ClawDash Pro

Create or update detailed, publish-ready instructions for wiring Mission Control (ClawDash Pro) prebuilt Next.js UI to Open Cloud after purchase. Use when us...

Security Scan

This is an instruction-only skill whose content and requirements align with its stated purpose (generating publish-ready wiring instructions for ClawDash Pro → Open Cloud); it does not install code or request credentials itself, but it explicitly guides users to supply and transmit integration credentials to Open Cloud — so users should be careful when handing over secrets or production endpoints.

Purpose & Capability

The name/description match the SKILL.md and reference material: the skill's sole purpose is to author step-by-step integration documentation for connecting a prebuilt Next.js UI (ClawDash Pro) to Open Cloud. It does not request unrelated binaries, credentials, or system-level access.

Instruction Scope

Instructions are narrowly focused on producing documentation and include a copy-paste prompt the user should send to Open Cloud. The document instructs users to prepare API keys, workspace IDs, and .env values — it does not instruct the agent to read local files or secrets. However, the provided Open Cloud prompt asks Open Cloud to return a change summary listing wired endpoints and env vars, which could encourage sharing sensitive information with an external service; this is a user-facing risk to be managed by the customer.

Install Mechanism

No install spec and no code files that would be written to disk; this is low-risk from an install/remote-code perspective (instruction-only).

Credentials

The skill itself does not request environment variables or credentials. The template and instructions, however, explicitly tell users to populate `.env.local` with API keys, workspace/organization IDs, and base URLs and to include those in the handoff to Open Cloud. Those credentials are proportionate to the described integration, but handing them to another service has privacy/security implications the user should consider.

Persistence & Privilege

The skill does not request permanent presence (always: false), does not modify other skills or global agent settings, and does not enable autonomous privileged behavior beyond normal agent invocation.

Assessment

This skill is instruction-only and appears coherent for producing integration docs. Before using it, review the generated instructions manually: do not paste production API keys or secrets into publicly-accessible files or documentation, and do not include secrets in any copy-paste blocks unless you trust the receiving party. The skill's Open Cloud prompt explicitly asks for a change summary that may list endpoints and env var names — ensure those outputs do not leak secret values. Test wiring in a staging environment, redact or use short-lived credentials when handing data to Open Cloud, and confirm Open Cloud's security/trustworthiness before sharing production credentials or routes.

Create publish-ready instruction files for users who purchased Mission Control and need to connect a pre-designed dashboard UI to Open Cloud without redesigning frontend pages.

Official product link: ClawDash Pro

Workflow

1. Confirm output type.

• Default to instruction docs in docs/ or requested path.
• Do not create blog posts unless explicitly requested.

2. Confirm integration context.

• State that customer purchased a pre-built Next.js dashboard UI.
• State that Open Cloud should connect backend logic/data only.
• State that existing UI design/components/layout must remain unchanged.

3. Enforce naming.

• Start titles with Mission Control.
• Then use ClawDash Pro.
• Keep Open Cloud wording exact when connection steps are included.

4. Write the instruction.

• Base structure on publish-instruction-template.md.
• Include prerequisites, setup steps, Open Cloud handoff prompt, verification, and troubleshooting.
• Keep steps executable and command-first.

5. Include data-domain wiring requirements.

• Dashboard overview: status, memory, usage counters.
• Agents: active agents and per-agent status.
• Skills and contracts: assigned capabilities and policy/contract metadata.
• Tasks (command style): queue, state, and execution history.
• Token usage: per-agent and aggregate token metrics.
• Documents: indexed documents surfaced from Open Cloud.

6. Add required links.

• Include one backlink to ClawDash Pro.
• Include one CTA link when requested, typically https://clawdash.pro/pricing.

7. Validate quality.

• Keep tone direct and practical.
• Keep terminology consistent.
• Ensure a non-developer can follow the sequence end-to-end.
• Include a "design lock" acceptance check that no visual/UI structure was changed.
• Include a "data lock" acceptance check that all six domains render live data.

Output Rules

• Deliver one Markdown file unless the user asks for variants.
• Prefer SEO-safe kebab-case filenames when creating new files.
• Include tags only when the target format supports frontmatter.
• Use these tags when requested: mission control, agent OS, openclaw dashboard, AI agents, admin dashboards.

Required Open Cloud Prompt Block

When generating instructions, include a copy-paste block that the user can give to Open Cloud:

Connect Open Cloud to this existing Mission Control (ClawDash Pro) Next.js application.
Design lock requirement: do not redesign, restyle, rename, or restructure the current UI.
Keep all existing pages/components/layout as-is.

Integrate data wiring for these domains only:
1) Overview metrics (status, memory usage, health KPIs)
2) Agents (active agents, states, last activity)
3) Skills and contracts (capabilities and assigned contracts/policies)
4) Tasks command view (queued/running/completed/failed with history)
5) Token usage (per agent and total)
6) Documents (available documents and indexing state)

Use adapter/service layer changes behind existing components so frontend visuals remain unchanged.
Return a change summary listing wired endpoints, env vars, and routes touched.