AugmentClaude

OwnMem Console

Open a local dashboard to view memory metrics, adoption rates, and recall quality.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/dashboard-grpcer/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Open OwnMem Console, the local dashboard for this repository's memory. Use when the user asks to open the dashboard, see memory metrics, check adoption or recall quality, or set up the optional embedding lane. Requires a repository initialized with the dashboard layer.

What this skill does

Open OwnMem Console

OwnMem Console renders this repository's memory metrics — adoption funnel, recall latency, corpus health, governance — in the browser. It binds 127.0.0.1 only; nothing is served off this machine.

If npx ownmem dashboard fails because the layer is missing, the repository was initialized without it. Re-run init with --layers dashboard (see the init skill), then retry.

Start it for the user

The server stays resident. Start it in the background; if an instance is already running, the same command returns "reused": true instead of starting a second one.

Do not redirect --json output to /tmp or any other shared directory. That JSON contains a long-lived access token, and /tmp is commonly world-readable.

In Claude Code, use the Bash tool with run_in_background: true. In other hosts, start the process in the background without capturing the token to a world-readable file:

npx ownmem dashboard --json

Then read the URL from the private instance record (mode 0600 under .local-test/):

npx ownmem dashboard --status --json

Open the url field in the browser. Keep the #t= fragment — the access token lives in the URL fragment and never reaches the server; without it the page only shows an access notice.

The CLI defaults to a random port. Pass --port 45300 (or another free local port) when the user needs a stable bookmark, and keep using that port later.

After opening, run npx ownmem report --since 7d once and give the user a one-line summary: adoption north star, latency P50/P95, and the most notable gap or warning. When the sample is small, say so instead of dressing process metrics up as adoption.

Lifecycle

npx ownmem dashboard --status --json
npx ownmem dashboard --stop
npx ownmem dashboard --open

Related skills