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.

66

Quality

78%

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

Fix and improve this skill with Tessl

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

Quality

Content

100%Weight 40%Scale 1-3

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 concise, actionable, well-sequenced instruction skill: it specifies exact config paths, fields, frontmatter, and a confirmation prompt, with explicit validation checkpoints for the risky shared-write. No changes needed for the evaluated dimensions.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows; every line (config paths, fields to resolve, frontmatter keys, the confirmation prompt) earns its place, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Guidance is concrete and copy-paste-ready: exact config paths, fields to resolve, the frontmatter key 'shared_from: <source permalink>', the observation format, and the prompt template 'Share "<title>" to <target>/<promoteFolder>?'; absence of code is not penalized for this actionable instruction-only skill.

3 / 3

Workflow Clarity

Seven clearly sequenced steps with explicit checkpoints for a consequential shared-write (step 5 'Confirm before writing', step 7 'Confirm with the new team permalink') plus ambiguity gates (steps 2-4), matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references and no nested/deep references; the body is well-organized into an intro plus numbered Steps, qualifying for 3 per the simple-skills scoring note. The only bundle file (assets/icon.svg) is an icon, not a content reference, and the body references no missing files.

3 / 3

Total

12

/

12

Passed

Description

57%Weight 40%Scale 1-3

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, clearly conveying a niche share-with-attribution action, but it lacks an explicit 'when to use' trigger clause and broader natural-language variations. Adding a 'Use when...' sentence would lift completeness and trigger-term quality.

Suggestions

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

Broaden natural trigger terms to cover variations users might say ('publish', 'post', 'promote', 'sync to team').

Optionally enumerate a couple more concrete actions (e.g. 'copies the note, adds a shared_from attribution, and confirms with the new permalink') to push specificity toward 3.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Share a personal Basic Memory note', 'with attribution and explicit confirmation') but does not enumerate a comprehensive set of distinct actions, matching the 'names domain and some actions' anchor rather than the multiple-specific-actions level 3.

2 / 3

Completeness

It clearly states what the skill does but provides no 'when to use it' trigger guidance, so per the rubric a missing 'Use when...' clause caps completeness at 2; it is not level 1 because the 'what' is explicit.

2 / 3

Trigger Term Quality

Natural terms like 'share', 'note', and 'team project' are present alongside product-specific 'Basic Memory' and 'Codex', but common variations and an explicit trigger clause are missing, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The niche is sharply defined by 'Basic Memory note', 'team project', 'Codex', and 'attribution and explicit confirmation', making it unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

12

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.