Realtime Dashboard
v1.0.0Complete guide to building real-time dashboards with streaming data, WebSocket/SSE, and live updates. Orchestrates dual-stream architecture, React hooks, and data visualization. Use when building trading dashboards, monitoring UIs, or live analytics. Triggers on realtime dashboard, live data, streaming dashboard, trading UI, monitoring.
⭐ 0· 1k·6 current·6 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name, description, and SKILL.md all describe the same purpose (real-time dashboards). There are no unexpected environment variables, binaries, or install steps required by the skill itself.
Instruction Scope
Instructions are example-driven and stay within the dashboard domain (dual-stream publishing, WebSocket/SSE, React hooks, visualization). It references internal skill paths like ai/skills/realtime/... and gives example endpoints (e.g., '/api/events', 'wss://api/ws') and local installation copy commands (~/.ai-skills). These are examples/reference pointers rather than directives to exfiltrate data, but you should not blindly run any shell commands that copy files from hidden home directories or invoke installers without inspection.
Install Mechanism
No install spec and no code files are included; the skill is instruction-only so nothing will be written to disk by the skill itself. README examples mention npx-based commands, but those are user-run examples rather than an automated installer embedded in the skill.
Credentials
The skill declares no required environment variables, credentials, or config paths. Example snippets include network endpoints appropriate for a dashboard (WebSocket URLs, local API routes); no unrelated secrets are requested.
Persistence & Privilege
always is false and the skill does not request permanent presence or modify other skills' configs. Model invocation is allowed (platform default) but that is normal for skills and not itself a concern here.
Assessment
This is a documentation/meta-skill and appears internally consistent with its stated purpose. Before installing or following its shell commands: (1) verify the provenance — the registry lists an owner ID but no homepage or known repo; (2) inspect any external installer commands (e.g., npx clawhub install, 'npx add <repo>') before running them; (3) don't blindly run copy/move commands that read from hidden home directories (e.g., ~/.ai-skills) unless you understand what those files contain; (4) review the referenced component skills (dual-stream-architecture, websocket-hub-patterns, etc.) if you plan to use or install them, since this meta-skill links to them but doesn't include their code; (5) treat example endpoints like 'wss://api/ws' as placeholders — replace with your own endpoints rather than using unknown public endpoints. Overall the skill is coherent and not requesting disproportionate privileges, but verify origin and any follow-up installs before executing commands.Like a lobster shell, security has layers — review code before you run it.
latestvk97d777tq7bp6q07aarr0k7kan80w77f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.