kg-mail-list

Converts weekly Awesome Search History entries into a self-contained HTML email digest.

1.6k|143|Updated Sep 9, 2019
One-click install
npx skills add https://github.com/frutik/awesome-search --skill kg-mail-list
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kg-mail-list
Source: https://github.com/frutik/awesome-search/tree/main/claude-skills/kg-mail-list
Command: npx skills add https://github.com/frutik/awesome-search --skill kg-mail-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a week of changelog-style History notes into a readable mailing-list email is repetitive manual work: stripping bookkeeping counts, converting wikilinks to published-site URLs, and formatting consistent HTML. This Skill automates that entire transformation into one reproducible step.

Core Features & Use Cases

  • Weekly digest generation: Reads History/<year>.<week>.md via the Obsidian MCP server and renders every entry, in file order, into a single self-contained HTML file at mails/<year>.<week>.html.
  • Statistics-free output: Drops all note counts, totals, and tallies so the email contains only the substance of what changed, plus Corrections bullets and typed New/Updated link lists.
  • Wikilink resolution: Converts every [[wikilink]] into a link to the published Quartz site, reporting any unresolved targets instead of emitting broken links.
  • Use Case: At the end of each week, run /kg-mail-list 2026.34 to produce mails/2026.34.html, a standalone email-ready digest of that week's Awesome Search updates, staged with git but never committed automatically.

Quick Start

Ask the assistant to write this week's mailing-list digest, optionally specifying a week like 2026.34, and it will generate the HTML email file in the mails folder.

Frequently Asked Questions about kg-mail-list

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly email digest from markdown changelog entries?▼

Run the skill with a week argument like /kg-mail-list 2026.34, or invoke it with no argument to use the current ISO week. It reads the matching History file and writes a self-contained HTML digest to mails/<year>.<week>.html.

How are Obsidian wikilinks converted for email output?▼

Each [[wikilink]] is resolved to its note file under the vault and rewritten as an anchor tag pointing to the published site at frutik.github.io/awesome-search, using Quartz slugification rules. Unresolved targets are kept as plain text and reported.

Does the generated email include note counts or weekly statistics?▼

No. All counts, totals, and tallies are deliberately excluded, including the per-entry heading counts. The email contains only entry titles, prose paragraphs, Corrections bullets, and linked New/Updated note names.

What happens if the requested week file does not exist?▼

The skill reports that the History file for that week is missing and stops. It never fabricates content or substitutes a different week's entries.

Does the skill commit or push the generated HTML file?▼

No. It only stages the file with git add. Committing and pushing remain the user's explicit decision, keeping publishing under manual control.