CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hivemind-memory

Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./harnesses/codex/skills/deeplake-memory/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, largely executable command reference with good section organization and a clear memory-read workflow. Its main weaknesses are the absence of validation steps around destructive member/skill/embedding operations and unresolved path placeholders for the auth command.

Suggestions

Add verification steps before destructive operations, e.g. run 'members' to confirm the user ID before 'remove <user-id>', and recommend '--dry-run' before 'skillify pull --force' or 'embeddings uninstall --prune'.

Resolve the auth command path once at the top and use that single concrete invocation throughout, removing the '$PLUGIN_ROOT ... or check the session context' and '<AUTH_CMD>' inconsistency.

Deduplicate the repeated 'Each argument is separate' note into one place and fold 'Getting Started' into the Organization Management section to trim redundant tokens.

DimensionReasoningScore

Conciseness

The body is a lean command reference with no explanations of concepts Claude already knows; only minor trimming is needed — 'Each argument is separate — do NOT quote subcommands together' is repeated in both the Organization Management and Skill Management sections, and 'Getting Started' re-states the auth command already listed above. Anchor 4, not 5.

4 / 5

Actionability

Highly concrete throughout: exact grep commands, the full auth-login.js subcommand list, and a complete skillify flag reference. Minor gaps keep it below anchor 5: the auth script path is an unresolved placeholder ('$PLUGIN_ROOT/bundle/commands/auth-login.js ... or check the session context', later '<AUTH_CMD>'), and the availability of the 'hivemind' CLI on PATH is never stated.

4 / 5

Workflow Clarity

'How to Search' is a well-sequenced 4-step read path (index → summaries → raw JSONL → grep) with an explicit 'Do NOT jump straight to reading raw JSONL' guardrail, but the skill includes destructive and batch operations (remove <user-id>, skillify unpull, embeddings uninstall --prune, skillify pull --force) with no validation or verification steps such as confirming a user ID via 'members' or running --dry-run before destructive runs — the rubric caps this at 3.

3 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-sectioned with clear headers and a memory-structure tree that make each area scannable. Minor gaps: ~100 lines of CLI reference (the skillify flag list alone is ~25 lines) that could live in a separate reference file, and the auth-login.js pointer reaches outside the skill without clear signaling. Anchor 4, not 5 — not an ideal split with well-signaled one-level-deep references.

4 / 5

Total

15

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is short and distinctive, with an explicit when-to-use clause, but it under-sells the skill's actual capabilities and relies on product names rather than natural trigger vocabulary. It describes one action (check both memories when recalling) while the body reveals a much richer toolset.

Suggestions

List the skill's core capabilities concretely, e.g. 'Search shared session memory via index and summaries, manage org/workspaces and members, mine and share skills across the team with skillify, and run semantic embeddings search.'

Add natural trigger terms users would actually say — 'remember', 'recall', 'shared memory', 'past sessions', 'team knowledge' — instead of leaning on product names like Activeloop and Hivemind.

Broaden the 'when' clause beyond recall to cover the other use cases (e.g. 'Use when recalling prior work, managing org members, or sharing reusable skills across the team').

DimensionReasoningScore

Specificity

Names the domain ('Global team and org memory powered by Activeloop') and one concrete action ('ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information'), but omits the skill's other capabilities (searching, org management, skillify, embeddings) — matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

Both 'what' ('Global team and org memory powered by Activeloop') and 'when' ('ALWAYS check ... when recalling information') are explicitly present, so it clears anchor 3's 'when missing or weakly implied', but the 'what' names no concrete actions and the 'when' covers only recall — not the explicit, concrete trigger phrases of anchor 5.

4 / 5

Trigger Term Quality

'memory' and 'recalling information' are natural user terms, but common synonyms ('remember', 'shared knowledge', 'past sessions') are absent and product jargon ('Activeloop', 'Hivemind') carries the description, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named product ('Hivemind memory', 'Activeloop') carves a distinct niche and explicitly differentiates from 'built-in memory', but the broad recall trigger fires on every memory-recall request, creating minor overlap with the built-in memory skill — anchor 4, not 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

activeloopai/hivemind

Path

harnesses/codex/skills/deeplake-memory/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.