Xpersona
O

Olares Dashboard (olares-cli dashboard)

CLAWHUB · Unverified

Olares Dashboard (olares-cli dashboard) — query the Olares Dashboard SPA's Overview and Applications routes from the command line, scoped to the active Olare... Skill: Olares Dashboard (olares-cli dashboard) Owner: olares Summary: Olares Dashboard (olares-cli dashboard) — query the Olares Dashboard SPA's Overview and Applications routes from the command line, scoped to the active Olare... Tags: latest:4.0.1 Version history: v4.0.1 | 2026-05-29T05:54:52.953Z | user Migrate ownership from @pengpeng to @olares (no content change vs 4.0.0) v4.0.0 | 2026-05-29T04:53:57.489Z | use

62
Rank
84
Safety
989
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 989 downloads reported by the source. Last updated 10/11/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s1718vftp5x2gwbtzenpt3kxch87k6j0:olares-dashboard
  1. Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-olares-olares-dashboard/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

141,731 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: olares-dashboard
version: 4.0.1
description: "Olares Dashboard (olares-cli dashboard) — query the Olares Dashboard SPA's Overview and Applications routes from the command line, scoped to the active Olares ID. An AI-agent-first JSON mirror with a strict dual-shape envelope (leaf items / aggregated sections), stable Kind constants, and human-readable table output. Covers Overview leaves (CPU, memory, disk, network, pods, fan, GPU, ranking), Applications listing and detail, the --watch HTTP-polling loop (interval / iterations / timeout / NDJSON-per-iteration / SIGINT-graceful), --since (sliding window) vs --start/--end (fixed window) selection, three-state empty-data semantics (no_<feature>_integration / no_<feature>_detected / vgpu_unavailable), and capability gates (fan is hard-gated to Olares One hardware; GPU is a soft advisory mirroring the SPA sidebar). Use when the user mentions Olares, Olares ID, Olares Dashboard, Olares One (fan / cooling), olares-cli dashboard, the Olares overview / applications view, 'show CPU / memory / disk / pods / network / fan / GPU / ranking on Olares', wants JSON for an AI agent, or hits errors like 'fan is only available on Olares One devices' or 'gpu data temporarily unavailable'."
metadata:
  requires:
    bins: ["olares-cli"]
  cliHelp: "olares-cli dashboard --help"
---

# dashboard (overview + applications, AI-agent first)

**CRITICAL — before doing anything, MUST use the Read tool to read [`../olares-shared/SKILL.md`](../olares-shared/SKILL.md) for profile selection, login, automatic token refresh, and the auth-error recovery table.**

> **Source of truth for flags is always `olares-cli dashboard --help` (global flags) and `olares-cli dashboard <verb> --help` (per-leaf flags).** This file only carries what `--help` cannot give: the dual-shape JSON envelope contract, three-state empty-data semantics, capability gates, watch / window rules, and the verb index.

## Routing

This subtree is an **AI-agent-first JSON mirror of the Olares Dashboard SPA's Overview and Applications routes**. Use it when:

- The user asks for runtime metrics: CPU / memory / disk / pods / network / fan / GPU.
- The user wants the workload-grain or application-grain resource ranking.
- The user wants the JSON form of what the SPA Overview / Applications pages show.
- The user wants `--watch` for live-tailing one of the above.

Sibling-skill routing:

| User intent | Use instead |
|---|---|
| "What pods / workloads / nodes / namespaces exist?" (object inventory) | [`olares-cluster`](../olares-cluster/SKILL.md) |
| "Install / start / stop an Olares app" | [`olares-market`](../olares-market/SKILL.md) |
| "Configure my user settings" | [`olares-settings`](../olares-settings/SKILL.md) |
| "Browse files / drives" | [`olares-files`](../olares-files/SKILL.md) |

> **Mental model:** dashboard answers *"what's the resource usage and health"*. For inventory and lifecycle, route elsewhere.

## JSON envel

_meta.json

{
  "ownerId": "kn7153k9wp5dwxsm6getv104r985vrf5",
  "slug": "olares-dashboard",
  "version": "4.0.1",
  "publishedAt": 1780034092953
}

references/olares-dashboard-overview.md

# dashboard overview

> **Prerequisite:** Read [`../../olares-shared/SKILL.md`](../../olares-shared/SKILL.md) and the parent [`../SKILL.md`](../SKILL.md) first.
> **Flags & wire shapes:** `olares-cli dashboard overview --help` and `olares-cli dashboard overview <section> --help`.

The most flag-rich verb in this subtree. Three "framing" sections (`physical` / `user` / `ranking`) live at the top of the overview tree; seven "hardware" sections (`cpu` / `memory` / `disk` / `pods` / `network` / `fan` / `gpu`) live alongside.

## Default action (no subverb)

```bash
olares-cli dashboard overview
olares-cli dashboard overview -o json
```

Emits a **Shape B sections envelope** with the three "framing" sections fetched concurrently:

```json
{
  "kind": "dashboard.overview",
  "sections": {
    "physical": { "kind": "dashboard.overview.physical", "items": [...] },
    "user":     { "kind": "dashboard.overview.user",     "items": [...] },
    "ranking":  { "kind": "dashboard.overview.ranking",  "items": [...] }
  }
}
```

For per-hardware sections (CPU / disk / fan / GPU / etc.), invoke them explicitly — they are NOT part of the default envelope.

## 10-section matrix

| Section | Kind | When to use |
|---|---|---|
| `physical` | `dashboard.overview.physical` | 9-row cluster-level snapshot (CPU/Memory/Disk/Pods/Net + extras). The "single screen vital signs" view |
| `user` | `dashboard.overview.user` | Per-user CPU / memory quota usage. Accepts optional `<username>` positional — **admin-only** for non-self lookups. Mirrors SPA's User Resources panel |
| `ranking` | `dashboard.overview.ranking` | Workload-grain resource ranking (per-application). `--sort asc|desc` + `--head N` for top-N. Mirrors SPA's UsageRanking widget |
| `cpu` | `dashboard.overview.cpu` | Per-node CPU details (model / freq / cores / utilisation breakdown / temp / load avg) |
| `memory` | `dashboard.overview.memory` | Per-node memory breakdown. `--mode physical|swap` (default `physical`) |
| `disk` | `dashboard.overview.disk` (Shape B) | **Sections envelope**: `main` (per-disk table) + `partitions` (per-device partition tables). `disk main` and `disk partitions <device>` give individual views |
| `pods` | `dashboard.overview.pods` | Per-node pod count snapshot (last/avg/max running) |
| `network` | `dashboard.overview.network` | Per-physical-NIC table. `--test-connectivity` (default true) probes internet/IPv6 per interface |
| `fan` | `dashboard.overview.fan` (Shape B) | **Olares One only.** Sections envelope: `live` (real-time fan/temp/power) + `curve` (hardcoded fan-curve spec). Hard-gated on non-Olares-One: `meta.empty_reason=not_olares_one` |
| `gpu` | `dashboard.overview.gpu` (Shape B) | Sections envelope: `graphics` (GPU list) + `tasks` (vGPU tasks). **Soft-gated**; `meta.note` advises when the SPA would have hidden the entry. See parent SKILL.md for the soft-gate decision tree |

## Drilling into a section

```bash
# Per-section snap

references/olares-dashboard-watch.md

# dashboard --watch / windows / NDJSON contract

> **Prerequisite:** Read the parent [`../SKILL.md`](../SKILL.md) first.
> **Flags:** `olares-cli dashboard --help` (every flag here is a `dashboard`-root global flag inherited by every leaf).

`--watch` opts every leaf verb into an HTTP-polling loop that mirrors the SPA's `setTimeout` cadence. **Polling, not streaming** — every iteration is a fresh HTTP request, no chunked transfer encoding.

## `--watch` behaviour

```
invoke leaf cmd
   │
   ▼
--watch set? ── no ──> single execution → emit one envelope → exit 0/1
   │
   yes
   ▼
Runner.Run loop
   │
   ▼
RunOnce iteration N
   │
   ├── success         → emit envelope (Shape A or B) with meta.iteration=N
   │                       JSON mode → NDJSON line on stdout
   │                       table mode → clear-screen redraw
   │
   ├── transient err   → emit envelope with meta.error="...", items:[]
   │                       continue
   │
   └── ErrTokenInvalidated / ErrNotLoggedIn
                       → exit non-zero IMMEDIATELY
   ▼
3 consecutive errors? ──> exit non-zero
   │
   no
   ▼
--watch-iterations cap reached? ──> exit 0
   │
   no
   ▼
SIGINT (Ctrl-C) ──> exit 0 gracefully
   │
   no
   ▼
wait --watch-interval, loop back
```

## NDJSON contract (JSON mode)

- **One envelope per iteration; nothing else on stdout.** Pretty `-o json` is for one-shot mode; `--watch -o json` is **always NDJSON** (line-delimited, no leading newline, no trailing array bracket).
- A failed iteration emits `items: []` + `meta.error: "<msg>"` — **NDJSON keeps streaming**, the failure does not raise to process exit unless it's auth-class or the 3-consecutive cap trips.
- `meta.iteration` is **1-based** and present in every payload.
- Each envelope's `meta.fetched_at` reflects that iteration's HTTP-request start time.

```jsonc
{ "kind": "dashboard.overview.cpu", "meta": { "iteration": 1, ... }, "items": [...] }
{ "kind": "dashboard.overview.cpu", "meta": { "iteration": 2, "error": "...", ... }, "items": [] }
{ "kind": "dashboard.overview.cpu", "meta": { "iteration": 3, ... }, "items": [...] }
```

## Watch loop knobs

| Flag | Purpose | Default |
|---|---|---|
| `--watch` | Enable the loop | off |
| `--watch-interval D` | Time between iterations | command's `recommended_poll_seconds` (e.g. 30s for GPU, 60s for most others) |
| `--watch-iterations N` | Stop after N iterations | unbounded |
| `--watch-timeout D` | Stop after this much wall-clock time | unbounded |

**All three `--watch-*` knobs are REJECTED without `--watch`** — don't silently waste a flag.

## Window semantics — `--since` vs `--start/--end`

Mutually exclusive. Pick one.

| Form | Semantics | Behaviour under `--watch` |
|---|---|---|
| `--since 5m` | Window = `[now - 5m, now]` | **Sliding** — each iteration recomputes `now` |
| `--start <RFC3339> --end <RFC3339>` | Window = `[start, end]` | **Fixed** — same window ever

skill-card.md

## Description:

Olares Dashboard helps agents query Olares Dashboard Overview and Applications data through olares-cli dashboard, including resource metrics, application rankings, JSON envelopes, and watch-mode output.

This skill is ready for commercial/non-commercial use.

## Publisher:

[olares](https://clawhub.ai/user/olares)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and operators use this skill to inspect Olares dashboard metrics and application resource usage from an active olares-cli profile. It guides agents toward the correct dashboard commands, JSON output shapes, watch behavior, and empty-data semantics for CPU, memory, disk, pods, network, fan, GPU, ranking, and applications views.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can guide an agent to query dashboard metrics through the active olares-cli profile, including admin-scoped views when --user targets another Olares ID.

Mitigation: Use the active profile intentionally, reserve --user for deliberate platform-admin visibility, and review profile scope before querying sensitive dashboard data.

Risk: Large result sets or live polling can add load or produce more output than needed.

Mitigation: Use output caps such as --head, --limit, --watch-iterations, and --watch-timeout, and respect the recommended polling cadence.

## Reference(s):

- [dashboard overview](references/olares-dashboard-overview.md)
- [dashboard --watch / windows / NDJSON contract](references/olares-dashboard-watch.md)
- [Olares Dashboard ClawHub skill page](https://clawhub.ai/olares/skills/olares-dashboard)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, configuration, guidance]

**Output Format:** [Markdown guidance with inline shell commands and JSON shape descriptions]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Agent-facing guidance centers on olares-cli dashboard output, including table, JSON, and NDJSON watch-mode behavior.]

## Skill Version(s):

4.0.1 (source: frontmatter and server release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Sponsored

Ads related to Olares Dashboard (olares-cli dashboard) and adjacent AI workflows.