Skip to content
Skills Library
Personal productivity · Writing

set-note-description

/set-note-description

Use when writing a note's description property for recall or retrieval. Summarizes a note's own content; parent-period synthesis belongs to periodic-rollup or the environment's specific rollup workflow.

Author
nweii ↗
Repository
agent-stuff ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when writing a note's description property for recall or retrieval. Summarizes a note's own content; parent-period synthesis belongs to periodic-rollup or the environment's specific rollup workflow.

Arguments

/set-note-description Note title(s)
Original author description

Use when writing a note's description property for recall or retrieval. Summarizes a note's own content; parent-period synthesis belongs to periodic-rollup or the environment's specific rollup workflow.

How it works

  1. Mode selection
  2. Edge cases
  3. Summary mode
  4. Meta mode
  5. Output
  6. Frontmatter placement
  7. Critical rules
  8. Periodic notes handling
Original SKILL.md headings · 150 lines, 1,196 words
SKILL.md preview
---
name: set-note-description
description: "Use when writing a note's description property for recall or retrieval. Summarizes a note's own content; parent-period synthesis belongs to periodic-rollup or the environment's specific rollup workflow."
argument-hint: "Note title(s)"
compatibility: "Readable and writable Markdown notes through filesystem or vault tools."
metadata:
  author: nweii
  version: "1.3.1"
---

# Summarize frontmatter

Generate a `description` property for the requested notes and write it to each note’s YAML frontmatter.

Read the target vault's instructions first. For a periodic note, prefer the vault's specific rollup workflow when it covers the requested scale. For a parent period synthesized from child notes, use `periodic-rollup` if available. Use this skill for a note's own content, or as a fallback when no more specific workflow is available.

If no note is specified, ask which note to summarize before proceeding.

---

Act as a markdown file analysis assistant. Read the note and generate a description for discoverability. Either follow any specified mode or intelligently select based on content type.

## Mode selection

If the user specifies a mode, use it. Otherwise, select based on content type:

### Use Summary mode for

- **Ephemeral content**: daily logs, weekly rollups, journal entries, periodic notes
- **Time-bound artifacts**: meeting notes, event recaps, trip logs
- **Exploratory thinking**: musings, brainstorms, working-through-problems
- **Personal reflections**: emotional processing, retrospectives, lessons learned

These are documents where the _insights or events_ are the value—you likely won't re-read the whole thing, you need the crystallized takeaway or memory anchor.

### Use Meta mode for

- **Reference material**: guides, how-tos, documentation, templates
- **Evergreen resources**: processes, checklists, policies, standards
- **Knowledge base entries**: concept explanations, topic overviews
- **Curated collections**: link indexes, reading lists, resource compilations
- **Project artifacts**: specs, designs, briefs (the document serves a structural purpose)

These are documents you _retrieve by need_—you're searching for something that solves a problem or answers a question, not recalling what you concluded.

### Evaluating the primary intent

Evaluate what the document _fundamentally is_ (rather than looking at individual sentences to infer purpose). If signals conflict, default to the document's primary purpose:

- **Journal, log, or record of events** → Summary  
  Recalling _what happened_ or _what was discussed_.
- **Manual, template, or reference guide** → Meta  
  Knowing _when to employ_ this tool.
- **Person thinking out loud or reflecting** → Summary  
  Captures point-in-time realizations and personal insights.
- **Encyclopedia entry, spec, or project brief** → Meta  
  Structural artifact defining the scope or requirements of a topic or project.
- **List of decisions or meeting outcomes** → Summary  
  Surfaces the _actual conclusions_ without reading the doc.
- **Curated collection or index of links** → Meta  
  Defining the collection's scope is more useful here than summarizing each link.

---

## Edge cases

**Hybrid documents** (e.g., daily log containing a reusable process):
Default to the document's _primary purpose_. A daily log with an incidental process note is still a daily log—use summary and mention the process as a notable item. If the process becomes valuable enough, it should be extracted to its own note.

**Meeting notes**:
Use summary. Focus on decisions, action items, and key discussion points—not "Notes from the Q3 planning meeting. Use when..."

**Book/article notes**:

- If primarily highlights and quotes with minimal synthesis → meta ("Notes on [Title] covering [topics]. Use when thinking about [domains].")
- If substantial personal commentary, insights, or arguments with the text → summary (capture YOUR takeaways)

**Specs, briefs, proposals**:
Use meta. These are structural documents—readers need to know what problem space they address, not a summary of their conclusions.

**Stubs and placeholders**:
Use meta. Describe intended purpose: "Placeholder for API authentication documentation. Use when documenting the auth flow."

**Content that defies categorization**:
Default to summary. Capturing what's actually there is more useful than a vague meta-description of ambiguous content.

---

## Summary mode

In a sentence or two, summarize what the content says or what happened: the crystallized takeaways, plus the concrete names, events, and small details that anchor recall. For exploratory content, capture the main themes.

Keep it plain and light. Lead with the thing itself, not an evaluative or framing opener ("Productive morning…", "A day spent…"). Trim articles and filler at the word level, but keep plain sentences over dense semicolon-stacked fragments. Avoid connective adverbs ("followed by", "then", "however") and narrative arc (causation, resolution); capture the essence, not exhaustive detail.

For periodic notes:

- Skip time-period prefixes (filename covers this)
- Minimize weight on slip box, addendum, or secondary sections
- Focus on actual content, activities, insights

### Summary examples

- `"Timeline padding 20-30% prevents Acme Corp delays; upfront alignment with Sarah's team saves more time than detailed technical planning."`
- `"Struggling to delegate Marcus's onboarding—equate doing it myself with caring; reframe delegation as trust-building."`
- `"Shopify integration through the morning; afternoon lost to an AWS outage and a family appointment. Kleppmann reading surfaced gaps in distributed systems."`

---

## Meta mode

Describe what this document IS—type, purpose, scope—plus when to reference it. Follow the **What + When** pattern:

`[Document type/topic] [scope or focus]. Use when [explicit trigger conditions].`

Be specific about trigger conditions. "Use when relevant" is useless; "Use when debugging authentication failures or onboarding new backend engineers" is searchable.

For periodic notes in meta mode (rare, but possible if requested): focus on domains, projects, or themes as searchable anchors.

### Meta examples

- `"Guide to vault metadata conventions and Base file integration. Use when designing folder structure, troubleshooting queries, or onboarding to the knowledge system."`
- `"Template for project retrospectives with prompts for timeline, collaboration, and technical debt. Use when closing out projects or preparing team retros."`
- `"Reading list on distributed systems with progress notes. Use when selecting next technical reading or recommending resources to others."`
- `"Spec for Shopify inventory sync covering error handling and retry logic. Use when implementing inventory features or debugging sync failures."`

---

## Output

Fit the length to what the note holds: as a soft default, aim for roughly 150–250 characters (a sentence or two), and go well under for a simple or sparse note — never pad to fill space. Treat that as a starting point and adjust to the note and to how the user works with descriptions in their own system. Stay well under 1024 characters; avoid paragraph length.

## Frontmatter placement

Add or update the `description` property in the YAML frontmatter at this position:

1. Identity & routing (aliases, icon, publish, permalink, url)
2. Content/classification (tags, description) ← INSERT HERE
3. People/time/relations (author, members, meeting time, related)
4. Status/provenance (reviewed, created, modified)

## Critical rules

- **ONLY modify the description property** — never change, escape, or reformat any other content
- Put the summary value in double quotes
- Preserve all existing formatting and Obsidian-specific syntax exactly
- If unable to write to the file, output a markdown code block with just: `description: "your summary here"`

## Periodic notes handling

For periodic notes:

- Don't add temporal prefixes if the filename already indicates the time period
- Minimize weight given to "slip box" or inbox sections—areas used to collect items you plan to reorganize or turn into different notes later (e.g., scratchpads, raw captures, external links) so they don't skew the summary
- Focus on the day's actual content, activities, and insights

### Hierarchical rollup pattern

For weekly, quarterly, or yearly synthesis from child notes, follow the environment's rollup workflow or `periodic-rollup`. That workflow owns child selection, missing-note handling, and parent synthesis; do not combine its procedure with a second independent summary pass here.

Versions

The database has no other skills named set-note-description.

Database snapshot: 13.11.2026 · package version 7d07d8cde711 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90periodic-rollup
    Use when synthesizing child periodic-note descriptions into a parent week, quarter, or year, or compiling project/topic history. Prefer a vault-specific rollup workflow when the environment provides one.
  • 90to-note
    Save content as a Markdown note in the user's Obsidian vault. Use for /to-note, or when asked to save, record, or send something to Obsidian or the notes vault.
  • 100note
    Create and manage notes during work. Use for "take note", "remember this", and "save for later".
  • 96suiji-note
    连接随记的 HTTP MCP 服务,读取、搜索并写入本地笔记;写入前必须让用户审查具体改动并明确确认。用户提到随记、MCP 笔记、读取/整理本地笔记时使用。
  • 100note
    Record reading notes to a structured notes file. Use when the user says "take notes" or "record this" during reading sessions.
  • 100note-assistant
    Create, search, and organize the user's local QuickNotes store through the `quicknotes` CLI or the QuickNotes MCP server. Use whenever the user asks to save a note, look something up in their notes, review recent notes, pin something important, or export notes to Markdown.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.