agentsclimarketplace

Notes consolidate

Skill laat/mor/skills/notes-consolidate

Apply batch edits to notes using natural language — rename, retag, add cross-references, merge, or clean up a set of notesFrom its SKILL.md

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

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

3.3 KB, as published. Nobody here has run it

Apply a natural language instruction across a set of notes, handling cross-reference updates automatically.

Examples

/notes-consolidate all pipeline notes should have Pipeline prefix in title
/notes-consolidate normalize fsharp tags — use "fsharp" not "f#"
/notes-consolidate add cross-references between related pipeline notes
/notes-consolidate merge the two ID model notes into one
/notes-consolidate remove the todo tag from completed items

Steps

  1. Parse the instruction: Identify:

    • Scope — which notes to target (tag filter, search query, explicit IDs, or "all")
    • Action — what to do (rename, retag, add links, merge, update content, delete)
  2. Find target notes: Use mor MCP tools to find the notes:

    • notes_list with tag/type filters for broad scopes
    • notes_search for query-based scopes
    • notes_read for explicit IDs

    Read each target note's full content to understand what changes are needed.

  3. Plan changes: For each target note, determine what needs to change. Present the plan to the user:

    • List each note and what will change (title, tags, content, etc.)
    • If merging: show which notes combine and which get deleted
    • If adding cross-references: show which links will be added where
    • Show total count: "X notes will be updated, Y unchanged"
  4. Ask for approval before making any changes.

  5. Execute changes: Apply updates one at a time using notes_update. For each change:

    • Update the note
    • If the change affects cross-references (title rename, ID change from merge, deletion), update all notes that link to it
  6. Handle merges (when the instruction is to combine notes):

    • Draft merged content — deduplicate, organize by topic, preserve all unique details
    • Create the merged note with notes_create
    • Update all backlinks in other notes to point to the new ID
    • Remove the original source notes with notes_remove
    • Remove mor: links between source notes (they'd be self-references)
  7. Handle cross-reference additions:

    • Read all target notes
    • Identify genuine connections (shared concepts, imports, explicit references)
    • Add [Title](mor:<id>) links in content preambles or inline where natural
    • For file/snippet notes (content is a code block), add links as a preamble paragraph before the code
  8. Report results: Summarize what was changed.

Cross-reference rules

  • Content links: [Title](mor:shortid) — proper markdown links only
  • Use 8-char short IDs in links
  • When renaming a note, no link updates needed (links use IDs, not titles)
  • When merging, replace all mor:<old-id> with mor:<new-id> in linking notes
  • When deleting, warn about orphaned backlinks
  • Run mor links --broken after to verify no dangling references

Important

  • Always show the plan and get approval before making changes
  • Preserve all content — consolidation means organizing, not summarizing
  • Be conservative with cross-references — only link when there's a genuine, specific connection, not just shared tags
  • 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.