Claude Skill

hivemind-goals

Create, track and update team goals in Hivemind via the `hivemind` CLI. Use whenever the user mentions a goal, objective, 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

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download activeloopai-hivemind-harnesses_hermes_skills_hivemind-goals-3fdfd6e.zip · 1 KB
Part of activeloopai/hivemind — 9 skills

Install

skills CLI npx skills add https://github.com/activeloopai/hivemind/tree/main/harnesses/hermes/skills/hivemind-goals
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install activeloopai-hivemind@llmmart
Git git clone https://github.com/activeloopai/hivemind.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole activeloopai/hivemind collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Hivemind Goals — CLI only (Hermes)

⚠️ CRITICAL: On this runtime (Hermes), you MUST use the hivemind shell CLI for goals. DO NOT use write_file on ~/.deeplake/memory/goal/... paths — those writes go to the local filesystem and never reach the team-shared hivemind_goals table. Other team members will NOT see them.

The hivemind-memory skill describes a generic memory layout — it does NOT apply to goals. For goals, use the CLI below.

Commands (invoke via terminal tool)

hivemind goal add "<text>"                                  # create goal, prints goal_id
hivemind goal list [--mine|--all]                           # list (default --mine)
hivemind goal done <goal_id>                                # mark closed
hivemind goal progress <goal_id> <opened|in_progress|closed>

Workflow when the user expresses a goal

  1. hivemind goal add "<short description>" — capture stdout, that's the goal_id (UUID).
  2. Tell the user the goal_id and that it is now team-visible in Deeplake.

Capture a task for later (with resumable context)

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" — store enough context to resume cold later, not just a one-liner. Tag it --agent capture so parked side-tasks are separable 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; defer until retry-backoff lands"

Line 1 is the label (what goal list shows). Fill Start here / Files / Branch / Run / Why from the conversation; Start here: matters most. Pass the whole package as one double-quoted argument so the newlines are preserved.

Resume a parked task (automatic context transfer)

When the user says "let's work on that task / goal" or "pick up the <X> task":

  1. hivemind goal list --mine — match the user's reference to a goal_id.
  2. hivemind goal get <goal_id> — prints the full package (goal list shows only the first line, so always use goal get). Read it as your working context.
  3. hivemind goal progress <goal_id> in_progress — mark it started.
  4. Begin from Start here: using the Files / Branch / Run lines. Continue as if the context was never lost.

What NOT to do

  • Do NOT call write_file on any path under ~/.deeplake/memory/goal/.
  • Do NOT do mkdir / cat > to create those files manually via terminal.

If the user wants to inspect goals you created, run hivemind goal list --mine (terminal) and present the output.

Files (hivemind)
  • SKILL.md 3.2 KB
    ---
    name: hivemind-goals
    description: Create, track and update team goals in Hivemind via the `hivemind` CLI. Use whenever the user mentions a goal, objective, 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: terminal
    ---
    
    # Hivemind Goals — CLI only (Hermes)
    
    ⚠️  **CRITICAL: On this runtime (Hermes), you MUST use the `hivemind` shell CLI for goals. DO NOT use `write_file` on `~/.deeplake/memory/goal/...` paths — those writes go to the local filesystem and never reach the team-shared `hivemind_goals` table. Other team members will NOT see them.**
    
    The hivemind-memory skill describes a generic memory layout — it does NOT apply to goals. For goals, use the CLI below.
    
    ## Commands (invoke via terminal tool)
    
    ```
    hivemind goal add "<text>"                                  # create goal, prints goal_id
    hivemind goal list [--mine|--all]                           # list (default --mine)
    hivemind goal done <goal_id>                                # mark closed
    hivemind goal progress <goal_id> <opened|in_progress|closed>
    ```
    
    ## Workflow when the user expresses a goal
    
    1. `hivemind goal add "<short description>"` — capture stdout, that's the `goal_id` (UUID).
    2. Tell the user the goal_id and that it is now team-visible in Deeplake.
    
    ## Capture a task for later (with resumable context)
    
    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" — store enough **context to resume cold** later, not just a one-liner. Tag it `--agent capture` so parked side-tasks are separable 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; defer until retry-backoff lands"
    ```
    
    Line 1 is the label (what `goal list` shows). Fill `Start here / Files / Branch / Run / Why` from the conversation; `Start here:` matters most. Pass the whole package as **one double-quoted argument** so the newlines are preserved.
    
    ## Resume a parked task (automatic context transfer)
    
    When the user says "let's work on that task / goal" or "pick up the `<X>` task":
    
    1. `hivemind goal list --mine` — match the user's reference to a `goal_id`.
    2. `hivemind goal get <goal_id>` — prints the **full** package (`goal list` shows only the first line, so always use `goal get`). Read it as your working context.
    3. `hivemind goal progress <goal_id> in_progress` — mark it started.
    4. Begin from `Start here:` using the `Files` / `Branch` / `Run` lines. Continue as if the context was never lost.
    
    ## What NOT to do
    
    - Do NOT call `write_file` on any path under `~/.deeplake/memory/goal/`.
    - Do NOT do `mkdir` / `cat >` to create those files manually via terminal.
    
    If the user wants to inspect goals you created, run `hivemind goal list --mine` (terminal) and present the output.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related