CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bm-share

Promote a note from your personal Basic Memory project to a shared team project, with attribution. Use when the user says "share this with the team", "publish this decision", or runs /basic-memory:bm-share. This is the deliberate way to write to a team workspace — auto-capture never does.

Quality

92%

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

100%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 instruction-only skill: a tightly sequenced workflow with concrete tool invocations, argument-level detail, guardrails for every edge case, and confirmation gates before the outward-visible write. It is token-efficient, fully actionable, and appropriately scoped with no extraneous material.

DimensionReasoningScore

Conciseness

The ~55-line body is lean with zero explanation of concepts Claude already knows; every sentence carries non-obvious operational detail such as "append `settings.json` to the literal value of `CLAUDE_CONFIG_DIR` ... do not trim it, expand `~`, or treat an empty value as unset". Anchor 4 requires over-explanation that could be trimmed, but the only redundancy (the MCP routing note echoing step 5) is a single minor echo serving standalone readability, so the lean-and-efficient anchor fits best.

5 / 5

Actionability

Guidance is fully executable for an MCP-tool skill: exact tools (`bm_read`, `bm_write`), exact argument names and values (`project`, `directory` = promoteFolder, `title`, `content`), an exact frontmatter key (`shared_from: <source permalink>`), and literal templates ("Share '<title>' to <target>/<promoteFolder>?", "Shared → my-team-2/shared/<slug>"). Common cases — empty `$ARGUMENTS`, several targets, an existing note at the target — are all handled, so the anchor-4 'minor gaps' does not apply; per the rubric's code-vs-instruction note, absence of code blocks is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

A clear 6-step sequence with explicit validation checkpoints appropriate to a non-destructive, non-batch write: stop when "teamProjects is empty", confirm which note on ambiguity, ask when several targets exist, "wait for a yes. Never share silently", "Don't overwrite an existing note at the target unless the user says so", and report the new permalink on completion. Anchor 4's 'minor validation gaps' does not fit because every checkpoint this operation needs is present, and the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ are absent) and none are needed; the body is organized into clear Steps and Notes sections with no content that belongs in a separate file. The rubric's short-skill guidance (under ~50 lines, no external reference needs) applies directly, and no organization gaps exist to justify anchor 4.

5 / 5

Total

20

/

20

Passed

Description

82%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 well-crafted: it clearly states what the skill does and when to use it, using natural quoted trigger phrases and third-person voice. Its only weakness is that it names a single core action (promote a note with attribution) rather than enumerating several specific capabilities, which limits its specificity score.

DimensionReasoningScore

Specificity

Names the domain ("personal Basic Memory project to a shared team project") and one concrete action with a detail ("Promote a note ... with attribution"), matching the 1-2-concrete-actions anchor. It is not 4 because only a single core action is listed rather than several specific ones, and not 2 because the action named is concrete rather than generic.

3 / 5

Completeness

Explicitly answers both questions: what ("Promote a note from your personal Basic Memory project to a shared team project, with attribution") and when ("Use when the user says 'share this with the team', 'publish this decision', or runs /basic-memory:bm-share") with concrete trigger phrases. This matches the top anchor exactly; the 4-anchor's 'when could be more explicit' does not apply since the trigger phrases are quoted verbatim.

5 / 5

Trigger Term Quality

Quotes natural user phrases — "share this with the team", "publish this decision" — plus the explicit command trigger "/basic-memory:bm-share", giving good keyword coverage. It falls short of 5 because common synonyms such as "send this to the team" or "copy to shared" are missing, but exceeds 3 because it provides actual natural phrasing users would say rather than bare keywords.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche tied to "Basic Memory", personal-to-team project promotion, and a named plugin command, with distinct quoted triggers and minimal conflict risk. The 4-anchor's 'minor overlap risk with closely related skills' does not fit, as no competing skill would trigger on these phrases.

5 / 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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

basicmachines-co/basic-memory

Path

plugins/claude-code/skills/bm-share/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.