hivemind-goals
Create, track and update team goals + KPIs via the Deeplake virtual filesystem at memory/goal/ and memory/kpi/. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy `hivemind tasks` CLI and now covers both objectives and tasks.
activeloopai · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add activeloopai/hivemind --skill hivemind-goals技能说明
name: hivemind-goals
description: Create, track and update team goals + KPIs via the Deeplake virtual filesystem at memory/goal/ and memory/kpi/. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy hivemind tasks CLI and now covers both objectives and tasks.
allowed-tools: Read Bash
Hivemind Goals
Track goals and KPIs as Markdown files inside the Deeplake virtual filesystem. Each file is one row in a dedicated team-shared table — the path encodes the structural metadata, the file body holds the human-readable description.
When to use this skill
Activate when the user expresses any of:
- "I want to track X / aim for X / track my progress on Y"
- "add a goal", "add a KPI", "what are my goals?"
- "mark this as done", "close that goal"
- "shipping X by Friday", "5 PRs this week", any measurable target
- "create a task", "add a todo", "remind me to fix X", any work item (the goals system absorbs the old
hivemind tasksCLI — there is no separate task store)
For "list my goals" → run ls ~/.deeplake/memory/goal/<userName>/opened/ and ls ~/.deeplake/memory/goal/<userName>/in_progress/. If empty, ask the user if they want to create one.
Path conventions (LEARN THESE)
~/.deeplake/memory/goal/<owner>/<status>/<goal_id>.md
~/.deeplake/memory/kpi/<goal_id>/<kpi_id>.md
<owner>— user identifier (use the userName fromhivemind whoamior the credentials)<status>— one ofopened,in_progress,closed<goal_id>— UUIDv4 you generate at create time<kpi_id>— short slug likek-prsork-demos
Path encoding is the source of truth. The owner, status, goal_id, and kpi_id come from the path — NOT from the file body. Do NOT write owner/status/goal_id/kpi_id inside the file content.
File body format
Goal file body — plain markdown, free form:
ship the goals-graph feature
Notes: focus on KPI tracking via VFS, no separate CLI.
Due: 2026-05-30.
KPI file body — markdown with a few mandatory key:value lines so the commit-driven auto-progress worker can parse and bump:
PRs merged
- target: 5
- current: 2
- unit: count
The target:, current:, unit: lines must stay on a single line each. The first line is the human-readable name. Anything else is free notes.
Operations
1. Create a new goal
When the user expresses a new goal:
- Get the current owner with
hivemind whoami(use the userName, e.g.emanuele.fenocchi). - Generate a UUIDv4:
uuidgen(do NOT usenode -e— Node is not available under the VFS path). - Write the goal file via Bash (Write / Edit are denied on memory paths; only Bash is intercepted and routed to SQL):
For a single-line goal,cat > ~/.deeplake/memory/goal/<owner>/opened/<uuid>.md <<'EOF' <goal description here, multiple lines OK> EOFecho '<text>' > ~/.deeplake/memory/goal/<owner>/opened/<uuid>.mdis equivalent. - Respond to the user that the goal is created.
Do NOT auto-generate KPIs. A goal is created with zero KPI files by default. Generate KPIs ONLY when the user explicitly asks you to ("aggiungi KPI per …", "add metrics for this goal", "track these metrics: …"). When the user asks, write each KPI as a separate file at ~/.deeplake/memory/kpi/<goal_id>/<kpi-slug>.md with the body format documented above.
1a. Capture a task for later (with resumable context)
Use this when the user parks a tangential task mid-session — "save this for later", "remind me to …", "don't let me forget …", "let's do X later", "capture this in Hivemind". The value is NOT the one-liner — it's storing enough context to resume cold in a future session without the user re-explaining anything.
Write it via the CLI (not the VFS heredoc) so the row is tagged agent: capture, which separates parked side-tasks from hand-made goals:
hivemind goal add --agent capture "Add rate-limiting to the webhook handler
Start here: add a per-IP token bucket on the handler entry path
Files: src/webhook/handler.ts:120-160, src/webhook/limits.ts
Branch: feat/webhook-hardening
Run: pnpm test webhook
Why: bursty clients hammer the endpoint; agreed to defer until the retry-backoff work lands"
- Line 1 is the label — keep it short; it's what
goal listand the SessionStart banner show. - Fill
Start here / Files / Branch / Run / Whyfrom the live conversation — you already know the files you just touched and the branch. Include only the lines you can fill; omit the rest.Start here:is the most important — the concrete first action. - Pass the whole package as one double-quoted argument (the newlines are preserved into the stored body).
- Confirm to the user: the label + that it'll resume cleanly next session.
1b. Resume a parked task (automatic context transfer)
When the user says "let's work on that task / that goal", "let's start the <X> task", or "pick up the parked <X>", pull its stored context back into the session and continue — the user should NOT have to re-explain anything.
- Find it:
hivemind goal list --mineand match the user's reference to agoal_id(by label / topic). If ambiguous, show the candidates and ask which one. - Transfer the context:
hivemind goal get <goal_id>prints the full package (Start here / Files / Branch / Run / Why). Read it as your working context —goal listonly shows the first line, so always usegoal getfor the full body. - Flip to in_progress:
mv ~/.deeplake/memory/goal/<owner>/opened/<uuid>.md ~/.deeplake/memory/goal/<owner>/in_progress/<uuid>.md - Act on it: open the
Files:, switch to theBranch:if given, and begin fromStart here:. You are now resumed — continue as if the context was never lost. Close it (section 5) when the wor