bm-share

Share a personal Basic Memory note to a configured team project from Codex with attribution and explicit confirmation.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/codex/skills/bm-share/SKILL.md

Quality

Content

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

The body is an exemplar of lean instruction-only skill writing: a numbered workflow with explicit stop/ask/confirm checkpoints, concrete config keys and output formats, and no wasted tokens. The only gap is that the actual write mechanism ('route to the target project') is left implicit. No destructive or batch operations are performed, and validation is present throughout.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-dense: 'Read ~/.codex/basic-memory.json, then the nearest project .codex/basic-memory.json; project keys override user keys' with zero concept explanations or padding. Every token earns its place, matching the top anchor.	5 / 5
Actionability	Guidance is mostly executable for an instruction-only skill: exact config paths, key names, a literal confirmation prompt template, a 'shared_from: <source permalink>' frontmatter key, a formatted observation line, and a default 'shared' folder. It stops short of naming the actual write mechanism (e.g. the basic-memory CLI command) behind 'route to the target project', which keeps it below fully-executable.	4 / 5
Workflow Clarity	Steps 1-7 are a clear sequence with explicit validation checkpoints: stop if no team projects are configured ('Do not invent a team destination'), ask when the note or target is ambiguous, and confirm before writing with a specific prompt. This is a guarded single write, not a destructive or batch operation, so the workflow-clarity cap does not apply; it fits the top anchor better than 4 because every checkpoint is explicit.	5 / 5
Progressive Disclosure	The skill is under 50 lines with a single purpose and a well-organized '## Steps' section, and the bundle contains only an icon asset with no referenced files needed. Per the rubric's simple-skill guideline, this scores 5 with just well-organized sections.	5 / 5
	Total	19 / 20 Passed

Description

66%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 specific and well-scoped to its niche, with a clear statement of what the skill does. Its main weakness is the absence of any 'when to use' trigger guidance, which caps completeness at 3 and slightly weakens trigger-term coverage. Adding an explicit usage clause would move it into the top tier.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to share, publish, or promote a Basic Memory note to a team project' — this directly addresses the completeness gap.

Include common user phrasings/synonyms such as 'publish', 'promote', or 'send to the team' in the trigger clause to lift trigger-term quality from good to comprehensive.

Mention the attribution behavior (shared_from permalink) more concretely in the description to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('personal Basic Memory note', 'configured team project') and several concrete actions ('share', 'attribution', 'explicit confirmation'). It falls between the 3 and 5 anchors: more than 1-2 concrete actions, but coverage is not comprehensive enough for a 5.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3. It is not a 2 because the 'what' is concrete and unambiguous.	3 / 5
Trigger Term Quality	Natural keywords are present ('share', 'note', 'team project', 'Basic Memory') and would match user phrasing like 'share this note with the team'. A few natural synonyms ('publish', 'promote', 'sync to team') are missing, which keeps it below the comprehensive-synonyms anchor of 5.	4 / 5
Distinctiveness Conflict Risk	The scope is narrowly tied to Basic Memory notes, Codex, and configured team projects, making it mostly distinct. The generic verb 'share' leaves minor overlap risk with other sharing/publishing skills, so it does not clearly meet the minimal-conflict anchor of 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: basicmachines-co/basic-memory
Path: plugins/codex/skills/bm-share/SKILL.md
Commit: 194afe1

Reviewed: 7 days 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.