newsletter-in-a-nutshell

Newsletter In a Nutshell

Use this skill when the user wants to compose, update, or finalize the In a Nutshell section for RSoW or BBtn.

Use ../_shared/reference/vault-structure.md, ../_shared/reference/newsletter-context.md, and ../_shared/reference/section-map.md for shared vault, language, placeholder, and folder rules.

Inputs

• RSoW source notes are in 00 Inbox/01 In a Nutshell.
• BBtn source notes are in 00 Inbox/01 In a Nutshell.
• The target issue folder is either 02 RSoW/rsow-###/ or 01 BBtn/bbtn-###/.
• The target section folder is 01 In a Nutshell inside the issue folder.
• The target section folder note is _01 In a Nutshell.md.
• The issue folder note is _rsow-###.md or _bbtn-###.md.

When the issue number or newsletter is ambiguous, infer it from the existing vault structure when safe. Ask the human editor only when the target issue cannot be identified.

Required Reading

Before writing output:

1. Read every file in 00 Inbox/01 In a Nutshell, including Markdown notes and non-Markdown asset notes when possible.
2. Extract every URL from every source file.
3. Open every extracted URL using an available browsing tool, MCP server, or local computer tool.
4. Use the linked source as the primary factual basis for the summary.
5. Keep a source link for every summary item.

If a URL cannot be opened, still process the note if it contains enough context, but mark the item for editor attention in the working output.

Source Handling

• Work independently as much as practical.
• Do not ask the human editor to read links or summarize source material.
• Ask the human editor only when a source file cannot be interpreted, when link access fails and the note has insufficient context, or when a file in the inbox has no clear relation to the section.
• After creating or updating the working output, move the source files that were used from 00 Inbox/01 In a Nutshell into the issue folder's 01 In a Nutshell subfolder.
• Leave unused source files in their original location.
• Never archive source files from this workflow.

Language

• For RSoW, write summaries in Czech.
• For BBtn, write summaries in English.
• For BBtn, omit items that are only relevant to Czech readers and have no useful value for an international audience.

Summary Style

• Each summary must be as objective as possible.
• Use dry humor and mild snark when it helps, but never be mean, cruel, or malicious.
• Each summary starts with exactly one emoji.
• Use a single space after the emoji.
• Use each emoji at most once in the section.
• Ideal summary length is about 40 characters.
• A summary may be up to 100 characters only when necessary.
• The link should cover only the key message.
• Choose link text that makes sense even when read on its own.
• For very short summaries, the whole summary may be linked.
• Italicize names of people, companies, products, services, and brands.
• Do not use bold, code, or other emphasis.
• Avoid dashes and quotation marks.

Ordering

Order the list by editorial importance:

1. Most important information first.
2. Newsletter context first, especially Czech context for RSoW.
3. UX, web business, digital product, and internet business items above general technology items.
4. Fun or curiosity items near the end.

Working Output

The first output is for human editorial processing. Write it to the section folder note:

• RSoW example: 02 RSoW/rsow-112/01 In a Nutshell/_01 In a Nutshell.md
• BBtn example: 01 BBtn/bbtn-112/01 In a Nutshell/_01 In a Nutshell.md

Create the issue section folder and folder note if missing. This is a non-destructive structure completion.

Use a checked Markdown task list. Items are checked by default. The human editor may rewrite summaries, change links, reorder items, add text, or uncheck items. Unchecked items must not be copied into the final issue text.

RSoW Working Output

## In a Nutshell

- [x] {{shrnutí s odkazy}}
- [x] {{shrnutí s odkazy}}
- [x] {{shrnutí s odkazy}}

Sledujte nás také přes [RSS feed](https://www.reknisioweb.cz/feed?sectionId=130962), [Bluesky](https://bsky.app/profile/www.reknisioweb.cz) nebo [Linkedin](https://www.linkedin.com/company/reknisioweb/).

BBtn Working Output

## In a Nutshell

- [x] {{summary with links}}
- [x] {{summary with links}}
- [x] {{summary with links}}

Follow us also via [RSS feed](https://www.better-button.com/feed), [Bluesky](https://bsky.app/profile/better-buton.com), or [LinkedIn](https://www.linkedin.com/company/better-button/).

Updating Existing Working Output

If the section folder note already exists:

• Preserve human edits wherever possible.
• Keep existing checked and unchecked states.
• Do not overwrite rewritten summaries.
• Add newly discovered items as checked items unless there is a clear reason to mark them for editor attention.
• Preserve editor ordering unless the user explicitly asks for reordering.
• Remove an item only when its source file is no longer relevant and removal is clearly requested.

Final Newsletter Output

When converting the editorial checklist into the final issue newsletter:

• Use only checked - [x] items.
• Remove task list markers.
• Put every item on its own line.
• Do not use bullets.
• End every item line with a backslash \ so Markdown keeps line breaks without separate paragraphs.
• Keep the emoji as the visual bullet.
• Keep the social follow paragraph after the list.

Final item example:

🏗️ [Vláda odsunula digitalizaci stavebního zákona](https://www.lupa.cz/aktuality/digitalizace-stavebniho-rizeni-se-posouva-do-let-2030-az-2031-potvrzuje-vladni-plan/) na roky 2030 až 2031.\

Style Reference

Use reference/rsow-in-a-nutshell-examples.md for compact examples extracted from resources/examples/rsow/. Treat resources/examples/ as the canonical source if more examples are needed.