brain-ops

Brain knowledge base operations. The core read/write cycle: brain-first lookup, read-enrich-write loop, source attribution, ambient enrichment, back-linking. Read this before any brain interaction.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/brain-ops/SKILL.md

Quality

Content

77%

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

The content is concise, highly actionable, and well-sequenced with concrete commands. Its weaknesses are missing explicit validation/verification around mutating brain writes and broken external references that undermine progressive disclosure.

Suggestions

Add an explicit validation/verification checkpoint to the put_page write loop (e.g., confirm the returned auto_links/errors before proceeding) so mutating operations have a feedback loop.

Either supply the referenced bundle files (skills/conventions/brain-first.md, skills/conventions/quality.md) or move their content inline so the references are not broken.

Consider moving the cross-source citation (v0.18.0+) detail and auto-link reconciliation specifics into a separate reference file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence (no padding about what a brain or knowledge base is), and every section earns its place, matching the score-3 'every token earns its place' anchor.	3 / 3
Actionability	Provides concrete, copy-paste-ready commands ('gbrain search "name"', 'gbrain config set auto_link false') and explicit citation formats like '[source-id:slug]', matching the score-3 fully executable anchor.	3 / 3
Workflow Clarity	Phases are clearly sequenced (1→2→2.5→3→4) with some checkpoints, but the mutating put_page write loop lacks an explicit validate/verify step; per the guidelines, missing validation for destructive/batch operations caps workflow clarity at 2.	2 / 3
Progressive Disclosure	References are signaled ('See skills/conventions/brain-first.md', 'skills/conventions/quality.md') but those bundle files do not exist, so navigation is broken; some inline content (cross-source citation, auto-link details) could be split out.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 conveys a clear, specific niche with multiple concrete capabilities and good distinctiveness. It falls short on completeness and trigger quality because it lacks an explicit 'Use when' clause and relies on internal jargon rather than natural user phrasing.

Suggestions

Add an explicit 'Use when ...' trigger clause naming natural user phrases (e.g., 'Use when the user mentions a person, company, or deal; when recalling or citing prior context; or before any brain lookup, read, write, or citation').

Replace internal jargon ('brain-first lookup', 'ambient enrichment') with user-facing terms alongside the technical names so trigger-term quality covers how users actually phrase requests.

Keep the concrete action list but trim 'Read this before any brain interaction' into a true trigger condition rather than an imperative instruction.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('brain-first lookup, read-enrich-write loop, source attribution, ambient enrichment, back-linking') matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Clearly states what the skill does, but the 'when' is an instruction ('Read this before any brain interaction') rather than an explicit 'Use when' trigger clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Has 'brain read/write/lookup/citation' and 'brain interaction' but these are internal jargon rather than natural terms a user would say; missing common user-facing variations.	2 / 3
Distinctiveness Conflict Risk	The niche ('Brain knowledge base operations') is distinct and scoped to a single brain-specific context, making it unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: garrytan/gbrain
Path: skills/brain-ops/SKILL.md
Commit: c44cdb5

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.