From team-memory
Read and write a Hivespace team's shared drive through the hivespace CLI (`hivespace fs …`) — the team's shared context as a filesystem. Load `.memory/` (shared team memory) at session start, keep coding-agent knowledge in `.memory/coding/`, store larger files elsewhere on the drive, and contribute durable knowledge back for the team's other agents. Triggers on "/team-memory", "load team memory", "team context", "team files", "team drive", "remember this for the team", "hivespace fs".
How this skill is triggered — by the user, by Claude, or both
Slash command
/team-memory:team-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A Hivespace team's shared context is a **filesystem** — a team-wide drive reached
A Hivespace team's shared context is a filesystem — a team-wide drive reached
through hivespace fs … (which talks to the Hivespace API as the logged-in user).
Three areas matter:
.memory/ — shared team memory. Distilled, durable knowledge every agent
loads each session: purpose, people and ownership, conventions, recurring
gotchas, current focus. Small and curated; MEMORY.md is its index (a Summary
plus one line per file). Hivespace's own workflow agents and humans read it too,
so keep the top level cross-cutting..memory/coding/ — coding-agent memory. The same, but for knowledge mainly
useful to other coding agents: coding/deployment rules, build/test quirks, repo
gotchas, local tooling, codegen conventions. Keeps the shared memory uncluttered. It mirrors .memory/
exactly — a CODING.md index plus flat topic files. The first agent to
need it creates it and links it with one line in the root MEMORY.md; after
that, just read and extend it..artifact/, transcripts/, elsewhere — stored files. Docs, specs,
transcripts, datasets, artifacts, scratch — kept for retrieval, not loaded each
session. Link to them from .memory/ when agents should know they exist.Lead with memory and leave it better than you found it: load .memory/MEMORY.md
first, and write back what you learn (step 3) so the next agent inherits it.
hivespace auth whoami
command not found → install with uv tool install hivespace (or pipx /
pip) and stop.hivespace auth login (for a
non-default server, export HIVESPACE_SERVER=<url> first). Don't run login
yourself — the user pastes their own token.On more than one team, fs may report it's ambiguous — pass --team <slug> (from
whoami) on every command.
hivespace fs cat .memory/MEMORY.md # index: Summary + one line per file
hivespace fs ls .memory # list memory files
hivespace fs cat .memory/<file> # read what's relevant (incl. .memory/coding/)
Read MEMORY.md and the topic files whose index lines fit the task (all of them
if it's broad). Then act on it: follow its conventions, refer to the people and
projects it names, respect the current focus. If a request contradicts the memory,
surface that rather than silently overriding it; don't echo memory back unless
asked. For anything bigger — a spec, a transcript, an artifact — follow memory's
pointers or browse the drive.
Loading memory is the easy half; it only compounds if agents write to it — what one learns, every future agent inherits. So a session of real work should leave memory better than it found it: watch for anything durable and proactively offer to persist it — don't wait to be asked.
When you write: a read-only PAT can't — say so and stop; otherwise extend
the right file rather than duplicate it, keep it high-level, and update its line
in the MEMORY.md / CODING.md index.
hivespace fs operates on the whole drive; the same auth and read/write rules
apply everywhere.
hivespace fs ls <path> # browse a directory
hivespace fs cat <path> # read a file
hivespace fs write <path> # create/overwrite (stdin or --from <local file>)
hivespace fs edit <path> --old "…" --new "…" # in-place find/replace
hivespace fs mkdir|mv|rm|cp … # the usual filesystem ops
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub rllm-org/skills --plugin team-memory