CtrlK
BlogDocsLog inGet started
Tessl Logo

bm-share

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

68

Quality

81%

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.

The body is concise, highly actionable, and well-structured with explicit confirmation checkpoints appropriate to a shared-write operation. The only gap is the absence of an error-recovery feedback loop, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The ~35-line body is lean: steps are direct imperatives with no over-explanation of concepts Claude already knows, and the one framing line ('This is the deliberate shared-write path. Automatic checkpoints and quick remembers stay personal.') is useful boundary disambiguation, not padding; every token earns its place.

5 / 5

Actionability

Concrete, copy-paste-ready guidance throughout: specific config paths ('~/.codex/basic-memory.json'), specific keys ('primaryProject', 'teamProjects', 'promoteFolder'), an exact prompt template ('Share "<title>" to <target>/<promoteFolder>?'), and exact frontmatter ('shared_from: <source permalink>', '- [context] Shared from <source permalink>'); absence of code is appropriate for this instruction skill.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit checkpoints (stop if no team projects in step 2, ask-if-ambiguous in steps 3-4, confirm-before-writing in step 5, confirm-with-permalink in step 7); not a 5 because there is no error-recovery feedback loop (e.g., what to do if the write fails or the permalink is invalid).

4 / 5

Progressive Disclosure

A self-contained skill under 50 lines with well-organized sections (# Share A Note, ## Steps) and no need for external references; the only bundle file is assets/icon.svg (an icon, not a content reference), so the simple-skill exception applies and clean structure earns a 5.

5 / 5

Total

19

/

20

Passed

Description

70%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 distinctive with a clear 'what', but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 3 and limits the overall score. Adding a concrete trigger phrase would lift it substantially.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to share or publish a Basic Memory note to a team project from Codex.'

Include natural synonyms a user might say (publish, send, sync to team) alongside 'share'.

Keep the existing specificity and distinctiveness; they are the description's strengths.

DimensionReasoningScore

Specificity

Quotes 'Share a personal Basic Memory note to a configured team project from Codex with attribution and explicit confirmation' name the domain (Basic Memory notes, team project) and several concrete actions/aspects (share, attribution, explicit confirmation); not a 5 because it is fundamentally one primary action with modifiers rather than a comprehensive list of distinct actions.

4 / 5

Completeness

The 'what' is clear ('Share a personal Basic Memory note to a configured team project... with attribution and explicit confirmation') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural trigger phrases like 'Share a personal Basic Memory note' and 'team project' are terms a user would plausibly say; not a 5 because synonyms/variations (publish, send, sync) and explicit 'Use when' phrasing are absent, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The combination 'Basic Memory note', 'configured team project', 'Codex', 'attribution', 'explicit confirmation' carves a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
basicmachines-co/basic-memory
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.