CtrlK
BlogDocsLog inGet started
Tessl Logo

updating-thoughts

Use when editing, correcting, rewriting, re-tagging, re-classifying, or annotating an existing Open Brain thought — "update that note", "fix the thought about X", "add a status/tag to it", "mark it superseded". Uses the update_thought MCP tool (open-brain-update-thought connector). Not for creating a new thought (that is capture) or removing one (see deleting-thoughts).

70

Quality

86%

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

78%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 tight, well-organized instruction skill that gives concrete field-level guidance and includes validation plus a retry loop for an overwrite-capable tool. It would benefit from concrete example payloads for each update mode and from treating the read-modify-write guard as recommended rather than optional.

Suggestions

Add a short example payload for each mode (e.g., a metadata_patch call and a content call) so the guidance is copy-paste ready.

Promote the if_unchanged_since guard from 'optional' to recommended for content overwrites, since this is a destructive-in-place operation.

Trim the Overview's narrative framing to state the tag-vs-rewrite tradeoff directly.

DimensionReasoningScore

Conciseness

Lean and well-structured with no padding about what Open Brain or embeddings are, but the Overview's framing ("Choosing how to update is the non-obvious part") is slightly narrative and could be trimmed.

4 / 5

Actionability

Concrete field names (metadata_patch, content, if_unchanged_since) and tool names are specified with a merge example ({"status":"done"}), but full example payloads for each mode are absent, leaving minor gaps.

4 / 5

Workflow Clarity

Clear three-step sequence with an inspect-before-editing checkpoint and a STALE_READ re-fetch-and-retry feedback loop, but the primary read-modify-write guard is explicitly marked optional, a minor validation gap.

4 / 5

Progressive Disclosure

Self-contained single-purpose skill with no bundle files and clear section organization (Overview, When to Use, Process, Quick Reference, Output, Common Mistakes, Notes); no external references are needed.

5 / 5

Total

17

/

20

Passed

Description

95%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 that clearly states the skill's purpose, surfaces natural trigger phrases, and explicitly draws boundaries against sibling skills. The only minor weakness is that the listed actions are overlapping synonyms of two underlying modes rather than a breadth of distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("editing, correcting, rewriting, re-tagging, re-classifying, or annotating"), but these are largely synonymous variants of two real modes (content change vs. metadata change) rather than fully distinct operations, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Uses the update_thought MCP tool") and when ("Use when editing, correcting, rewriting...") with concrete trigger phrases plus explicit not-for boundaries.

5 / 5

Trigger Term Quality

Includes multiple natural quoted phrases a user would actually say ("update that note", "fix the thought about X", "add a status/tag to it", "mark it superseded"), giving comprehensive synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche (updating an existing Open Brain thought) with explicit disambiguation from capture (creating) and the deleting-thoughts skill, minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NateBJones-Projects/OB1
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.