---
name: "notes"
description: "Read, write, and curate a subject-organized notes collection."
metadata:
  createdAt: "2026-09-11T18:46:00.191366+00:00"
  repoUrl: "https://skillz.supply/skills/did:plc:xbtmt2zjwlrfegqvch7fboei/skills.notes/SKILL.md"
---

# notes

Locate the user's notes collection from the request or project configuration.
Ask for its location if it cannot be identified; do not assume a personal checkout,
publishing domain, taxonomy, memory store, or build command.

Search existing subjects before adding a note. Treat notes as dated evidence,
not unquestionable authority; follow primary sources when accuracy matters.
Use available repository history or citations to establish provenance.

Keep reusable knowledge independently understandable. If a claim only makes sense
inside one project, put it in that project's documentation. Extend an existing
subject for a small addition; create a new note when it has a distinct purpose.
Follow the collection's established organization.

Lead with the idea, explain its mechanism, and include a small example when useful.
Name the subject in the title. Cite the sources supporting substantive claims,
including versions or dates when behavior changes over time.

When curating, consolidate duplicates, move misplaced subjects with appropriate
links, and rewrite stale claims instead of appending contradictory corrections.
Keep project incident narratives separate from general guidance.

Use the repository's documented validation and publishing workflow. Editing a note
does not itself authorize publishing it.