notes-audit — analyze, then PROPOSE (never act unilaterally)

Self-Evolving skill — if the smell table stops matching how the operator actually organizes (new smells found, false positives), evolve the table in this SKILL.md; see the Post-Execution Reflection at the bottom.

This skill is an analysis workflow, not a script: you (Claude) gather the data with the plugin's CLIs, reason over it, and present a proposal. No reorganization happens in this skill — execution belongs to notes-organize, only after operator approval.

1. Gather

NC="$HOME/.claude/plugins/marketplaces/cc-skills/plugins/notes-commander/scripts/notes.ts"
bun "$NC" inventory --json          # folder tree + counts (fast; always do this)
bun "$NC" export                    # full snapshot when content-level analysis is wanted

For content-level auditing, Read the snapshot's manifest.json (note names, per-note modified dates, char counts) and sample individual markdown files — do NOT paste hundreds of notes into context; sample representatives per folder.