set-note-description_skill

Overview

This skill generates or updates the description frontmatter property for a note, choosing an appropriate mode (Summary or Meta) based on the note's primary intent. It writes a concise, discoverable description into the YAML frontmatter without altering any other content. Use it to make notes searchable and immediately useful from lists and search results.

How this skill works

The skill reads the note, evaluates its primary purpose, and selects Summary or Meta mode unless a mode is explicitly requested. In Summary mode it produces a 1–2 sentence crystallized takeaway; in Meta mode it produces a What + When description that explains the note's purpose and trigger conditions. It then inserts or updates only the description property in the YAML frontmatter at the prescribed position and returns the new value.

When to use it

• Add a concise discoverability summary for journals, meeting notes, or logs
• Convert a guide, template, or spec into a searchable reference description
• Bulk-update descriptions for periodic rollups (daily, weekly, quarterly)
• Create descriptions for library or project artifacts so others know when to consult them
• When you want consistent frontmatter descriptions without editing the body

Best practices

• Prefer Summary mode for event-driven, reflective, or exploratory notes; capture key outcomes and memorable names
• Prefer Meta mode for reference, templates, specs, or curated collections; follow What + When pattern
• Keep descriptions under 1024 characters and in double quotes to fit frontmatter constraints
• Do not change any other frontmatter fields or body content—only update the description property
• For hierarchical rollups, synthesize from linked child note descriptions rather than re-reading all content

Example use cases

• Add a one-line summary to meeting notes that highlights decisions and action items
• Generate a meta description for a how-to guide explaining when to consult the guide
• Summarize a daily journal entry with memorable events and insights for later recall
• Create consistent descriptions for weekly rollups by synthesizing linked daily summaries
• Convert a stub note into a meta description that states its intended purpose and triggers