Ops Deck
v1.1.0Full operational dashboard for AI agent setups. Cron job calendar, agent intel feeds, security audit panel, network infrastructure map, code search, repo arc...
⭐ 0· 105·1 current·1 all-time
bySolomon Neas@solomonneas
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill describes a local dashboard (UI + API + local code search) and the documented prerequisites (Node, Python, Ollama, PM2, SQLite) align with the claimed capabilities (Express API, FastAPI code search, local embeddings). It does not request unrelated credentials or unusual binaries.
Instruction Scope
SKILL.md repeatedly states the dashboard reads static JSON files you provide and does not run privileged system commands; that keeps scope narrow. However the dashboard is designed to display agent configuration files (AGENTS.md, SOUL.md, IDENTITY.md, etc.) and repo/cron data — those files often contain sensitive information, so you must control what is placed in the dashboard data directory. The setup text is truncated in the copy provided, so some implementation details (how/where files are read, whether any sample cron scripts include commands) are missing and should be inspected before use.
Install Mechanism
This is an instruction-only skill with no install spec and no code files; there is no automatic installer. The SKILL.md tells users to run standard package installs (npm, pip, ollama pull) themselves. That is lower risk than an automated download/install, but you should run those commands manually and inspect any scripts they reference.
Credentials
The skill declares no required environment variables or credentials, which matches its self-hosted local-first design. Still, it expects access to local JSON files and optionally to local git repos and an Ollama model — ensure these data sources do not contain secrets you wouldn't want aggregated into a single dashboard. The requirement to pull a local embedding model (qwen3-embedding:8b) is justified by the semantic code search but implies sizable local storage/network activity.
Persistence & Privilege
The skill is not always-enabled and uses normal autonomous invocation defaults. It does not declare actions that modify other skills or request system-wide privileges. Because it's instruction-only, it cannot force persistent system changes by itself; any persistent services will be created only if you run the provided setup (PM2, etc.).
Assessment
This skill is an instructions-only guide for a local dashboard and appears internally consistent, but take these precautions before running anything:
- Inspect the full SKILL.md and any installation/setup scripts (the provided copy is truncated). Confirm there are no hidden network calls, telemetry, or unexpected remote downloads in scripts you run.
- Treat the dashboard as a potential aggregator of sensitive data. Only place agent config files, cron/journal JSONs, or repo data into its data directory after reviewing them for secrets (API keys, private SSH keys, credentials, tokens, identity material).
- Run the services locally on an isolated machine or VM and do not expose the API/ports to the public internet unless you add proper authentication and firewall rules.
- Review any example cron scripts before installing them; the project claims automation is optional and that you should review scripts — follow that guidance.
- Be aware pulling the embedding model (ollama pull qwen3-embedding:8b) will download large model artifacts and may have licensing/usage implications.
If you want higher confidence, ask the publisher for the full repository or the complete setup scripts so you (or an auditor) can review them before running installation commands or adding real agent/config data.Like a lobster shell, security has layers — review code before you run it.
latestvk97dqanrzkyemge6k7xw2exffx83ama2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.