From newsletter-composer
Compose the RSoW or BBtn Events paragraph by selecting relevant events from the site event overview for the seven days starting on the newsletter publication date, then insert it only after editor approval.
npx claudepluginhub garcon/newsletter-composerThis skill uses the workspace's default tool permissions.
Use this skill when the user wants to compose, update, or finalize the `Events` paragraph for RSoW or BBtn.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Use this skill when the user wants to compose, update, or finalize the Events paragraph for RSoW or BBtn.
Use ../_shared/reference/vault-structure.md, ../_shared/reference/newsletter-context.md, ../_shared/reference/section-map.md, ../_shared/reference/publication-date.md, and ../_shared/reference/approval-workflow.md for shared vault, language, placeholder, publication-date, and approval rules.
00 Inbox/06 Events.Konference a akce.Events.02 RSoW/rsow-###/ or 01 BBtn/bbtn-###/.06 Events inside the issue folder._06 Events.md._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.
../_shared/reference/publication-date.md.Before writing output:
00 Inbox/06 Events if present.Konference a akce.Events.If the home-page link cannot be found, inspect the site navigation, archive, RSS feed, local resources, or existing examples. Ask the human editor only when the event overview cannot be identified responsibly.
The first output is for human editorial processing. Write it to the section folder note:
02 RSoW/rsow-112/06 Events/_06 Events.md01 BBtn/bbtn-112/06 Events/_06 Events.mdCreate the issue section folder and folder note if missing. This is a non-destructive structure completion.
The working output uses the same approval logic as Opinion. Add front matter:
---
approved: waiting
---
---
approved: waiting
---
{{jeden odstavec s vybranými akcemi v češtině}}
---
approved: waiting
---
{{one paragraph with selected events in English}}
Do not add a section heading unless the existing issue format explicitly uses one. The {{Events}} placeholder represents the paragraph itself.
resources/examples/.If the section folder note already exists:
approved property, add approved: waiting.approved: approved, approved: true, or approved: "true" unchanged.When converting the working output into the final issue newsletter:
approved: approved, approved: true, or approved: "true".approved is missing, waiting, false, or any other value, do not insert the paragraph into the final issue.{{Events}} in the issue folder note with the approved paragraph.00 Inbox/06 Events into the issue folder's 06 Events subfolder.Use reference/events-examples.md for compact examples extracted from resources/examples/rsow/ and resources/examples/bbtn/. Treat resources/examples/ as the canonical source if more examples are needed.