agentsclimarketplace

Notes review

Skill laat/mor/skills/notes-review

Review the note store for quality issues — duplicates, stale content, broken links, tag inconsistencies, and cleanup opportunitiesFrom its SKILL.md

Install
npx -y skills add laat/mor --skill notes-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.3 KB, as published. Nobody here has run it

Audit the note store and produce a structured report of proposed changes. Do NOT apply changes — present proposals for user approval, then use /notes-consolidate or individual notes_update/notes_remove calls to execute approved changes.

Examples

/notes-review
/notes-review tag hygiene
/notes-review duplicates
/notes-review stale

Steps

1. Gather the full picture

  • notes_list with a high limit to get all notes
  • Aggregate tag and type distributions from the full list (count occurrences across all notes)
  • Note total count, tag distribution, type distribution

Success criteria: You have a complete inventory of all notes with their metadata.

2. Read and classify

Read notes in batches using notes_read (batch IDs). For each note, check:

IssueWhat to look for
DuplicatesNotes with very similar titles or overlapping content
StaleOutdated information, references to things that may have changed
Tag inconsistenciesSimilar tags that should be unified (e.g. "fs" vs "filesystem"), unused tags on single notes
Type mismatchesNotes whose type doesn't match their content (see type guidelines below)
Broken linksmor: links pointing to non-existent notes
Missing linksNotes that reference the same concepts but aren't cross-linked
Empty/thinNotes with very little content that could be merged into related notes
Title qualityVague titles that don't help with search

Type guidelines

  • file — a source file that can be dropped into a project as-is. Content should be a brief one-line description followed by a single fenced code block — nothing else. No prose sections, no multiple code blocks. If a file note has extra context (usage examples, design notes), split those into a separate snippet or knowledge note with a cross-reference link.
  • snippet — a code example, pattern, or recipe. Can have prose, multiple code blocks, and explanatory sections.
  • knowledge — concepts, design docs, references. Primarily prose.

If the user specified a focus area (e.g. "duplicates", "tag hygiene"), prioritize that.

Success criteria: Each note has been reviewed and issues catalogued.

3. Present the report

Output a structured report grouped by issue type:

  1. Duplicates — groups of notes that overlap, with merge suggestions
  2. Tag cleanup — tags to rename/unify, with affected notes
  3. Stale content — notes that may need updating or removal
  4. Broken links — dangling mor: references
  5. Missing links — suggested cross-references between related notes
  6. Other — type mismatches, thin notes, title improvements

For each proposal, include:

  • The note ID(s) and title(s)
  • What the issue is
  • Suggested action (merge, retag, update, remove, link)

End with a summary: "X notes reviewed, Y issues found across Z categories"

Success criteria: User can review and approve/reject each proposal individually.

4. Execute approved changes

After the user approves specific proposals:

  • Use notes_update for retags, title changes, content updates
  • Use /notes-consolidate for batch operations (retagging many notes, merging)
  • Use notes_remove for deletions
  • Report what was changed

Rules

  • Present ALL proposals before making any changes
  • Do NOT modify or delete notes without explicit user approval
  • Be conservative — flag uncertain issues as "possible" rather than definitive
  • For large stores (50+), focus on the highest-impact issues first
  • Short ID prefixes (8+ hex chars) work for all mor commands and links

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.