Run any Skill in Manus with one click

newsletter-assembler

Build a full internal or external newsletter from source notes, launches, events, and updates. Use when assembling recurring newsletters.

Run Skill in Manus

Overview

Build a full internal or external newsletter from source notes, launches, events, and updates. Use when assembling recurring newsletters.

Install command

npx skills add https://github.com/00PrabalK00/claude-skills --skill newsletter-assembler

Copy and paste this command into Claude Code to install the skill

Source

00PrabalK00/claude-skills

Stars1

Forks0

UpdatedMarch 16, 2026 at 12:51

File Explorer

2 files

SKILL.md

readonly

name	newsletter-assembler
description	Build a full internal or external newsletter from source notes, launches, events, and updates. Use when assembling recurring newsletters.

Newsletter Assembler

Overview

Build a full internal or external newsletter from source notes, launches, events, and updates.

Core Workflow

Gather the source material, existing conventions, templates, and destination format before drafting.
Extract the information that matters most for the intended audience and discard low-signal noise.
Structure the output so it matches repo, team, or domain expectations instead of starting from a blank generic outline.
Draft the artifact, then surface any missing facts or decisions that still need human input.

Deliver

A ready-to-edit draft in the expected structure and tone.
The main sections, decisions, or states the artifact should include.
Open questions or missing facts that would improve the final output.

Guardrails

Do not invent facts, metrics, approvals, or guarantees that are not supported by the inputs.
Prefer existing repo or team conventions over generic formatting.
Keep the output useful and specific rather than padded.
Do not invent metrics, policy decisions, customer commitments, or ownership that the inputs do not support.

More from this repository

same repository

accessibility-auditor

00PrabalK00/claude-skills

Audit interfaces for accessibility issues across semantics, keyboard use, focus management, color contrast, labels, and announcements. Use when reviewing or fixing UI accessibility.

2026-03-161

api-contract-builder

00PrabalK00/claude-skills

Design and document API contracts including routes, request and response schemas, validation rules, error envelopes, auth expectations, naming conventions, and examples. Use when creating or revising endpoints, OpenAPI specs, or service interfaces.

2026-03-161

api-regression-guard

00PrabalK00/claude-skills

Check whether code changes silently broke API contracts, behavior, schemas, or compatibility expectations. Use when reviewing endpoint changes, SDK updates, or public interface diffs.

2026-03-161

app-store-metadata-builder

00PrabalK00/claude-skills

Draft app titles, descriptions, changelogs, and keyword sets for app-store releases. Use when preparing App Store or Play Store metadata.

2026-03-161

backup-restore-validator

00PrabalK00/claude-skills

Check whether backup and restore plans are actually restorable, verifiable, and operationally safe. Use when auditing data protection workflows.

2026-03-161

bag-replay-debugger

00PrabalK00/claude-skills

Check rosbag or recorded data replay issues involving topic names, clocks, remaps, timing, and consumer mismatch. Use when replayed data does not reproduce expected behavior.

2026-03-161

Source

00PrabalK00

00PrabalK00/claude-skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Correspondence ClerksOffice and Administrative Support Occupations43-4021L4

name	newsletter-assembler
description	Build a full internal or external newsletter from source notes, launches, events, and updates. Use when assembling recurring newsletters.

Newsletter Assembler

Overview

Build a full internal or external newsletter from source notes, launches, events, and updates.

Core Workflow

Gather the source material, existing conventions, templates, and destination format before drafting.
Extract the information that matters most for the intended audience and discard low-signal noise.
Structure the output so it matches repo, team, or domain expectations instead of starting from a blank generic outline.
Draft the artifact, then surface any missing facts or decisions that still need human input.

Deliver

A ready-to-edit draft in the expected structure and tone.
The main sections, decisions, or states the artifact should include.
Open questions or missing facts that would improve the final output.

Guardrails

Do not invent facts, metrics, approvals, or guarantees that are not supported by the inputs.
Prefer existing repo or team conventions over generic formatting.
Keep the output useful and specific rather than padded.
Do not invent metrics, policy decisions, customer commitments, or ownership that the inputs do not support.