CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hivemind-goals

Create, track, and read team goals via Hivemind from openclaw. 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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

An exemplary lean skill body: concrete tool calls, a copy-paste-ready context-capture template, explicit resume mechanics, and a sharp "What NOT to do" section guarding against the main failure mode. The only meaningful gap is handling the outcome of the duplicate-check search in the create workflow.

DimensionReasoningScore

Conciseness

The body is lean and operational throughout — tool signatures, a compact resumable-context template, and short prohibition notes. Every parenthetical (provenance flag, status-move tools, Deeplake filesystem) carries real guidance rather than padding; nothing explains concepts Claude already knows.

5 / 5

Actionability

Fully executable guidance: exact tool call signatures (hivemind_goal_add({ text })), a copy-paste-ready multi-line example showing the full context package, and the explicit memory path pattern "memory/goal/<owner>/opened/<goal_id>.md" for resuming.

5 / 5

Workflow Clarity

The three workflows (express a goal, capture a task, resume a task) are clearly numbered with checkpoints — duplicate-prevention search first, capturing the returned goal_id, and confirming to the user. Minor gap: the pre-creation search surfaces an existing related goal but gives no instruction on what to do when one is found, and resume has no fallback if the search misses.

4 / 5

Progressive Disclosure

At ~48 lines with no bundle files (no references/, scripts/, or assets/ exist), this fits the rubric's simple-skill exception: well-organized sections with no need for external references score 5.

5 / 5

Total

19

/

20

Passed

Description

87%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.

A strong description with an explicit what-and-when structure and unusually comprehensive natural trigger terms. Its main weakness is breadth: by claiming every actionable work item ("task", "todo", "fix X") it risks triggering for unrelated work, reducing distinctiveness.

Suggestions

Narrow the catch-all triggers ("fix X", "any actionable work item") or scope them to persistence/team-visibility intent so ordinary coding requests don't fire this skill.

Separate the legacy-migration note ("replaced the legacy hivemind tasks CLI") from the trigger clause so it informs rather than inflates the activation conditions.

Add one differentiating capability (e.g., team-shared/visible goals across sessions) to sharpen the niche against generic todo-tracking skills.

DimensionReasoningScore

Specificity

"Create, track, and read team goals via Hivemind from openclaw" names the domain and several specific actions. It falls short of anchor 5 because coverage has minor gaps (no mention of goal status, ownership, or update semantics) but lists more than the 1-2 concrete actions of anchor 3.

4 / 5

Completeness

Explicitly answers both: what ("Create, track, and read team goals via Hivemind from openclaw") and when ("Use whenever the user mentions… ALSO use when the user says…") with concrete trigger phrases. Matches the anchor 5 example pattern.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage: "goal, objective, target, milestone, track progress, task, todo, work item, remind me to, fix X" — including synonyms and the exact phrasings a user would naturally say. Matches anchor 5.

5 / 5

Distinctiveness Conflict Risk

The Hivemind/openclaw goal niche is identifiable, but triggers like "task", "todo", "fix X", and "any actionable work item" would fire on nearly any ordinary coding or reminder request, overlapping heavily with generic task-tracking skills. Somewhat specific but with real overlap risk — anchor 3 rather than 4.

3 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

activeloopai/hivemind

Path

harnesses/openclaw/skills/hivemind-goals/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.