# Usecase newsletter digest Human Guide

## What This Is For
Summarize newsletter/email feed messages from the last N hours and propose follow-ups. It gives the agent a clearer input/output frame for email marketing: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Usecase newsletter digest agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for usecase newsletter digest.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Usecase newsletter digest guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Use when: Use when the user asks to summarize newsletter/email feed messages from the last N hours and propose follow-ups.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Newsletter Digest: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
- Use the usecase-newsletter-digest skill for this request.
- Help me with newsletter digest.
- Use when the user asks to summarize newsletter/email feed messages from the last N hours and propose follow-ups.
- Newsletter Digest: provide an actionable result.
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use usecase-newsletter-digest for unrelated requests.
- This request is outside newsletter digest scope.
- This is conceptual discussion only; no tool workflow is needed.

## Decision Points And Nuance
The original skill emphasizes: Purpose, Routing, Trigger Examples, Positive, Negative, Parameters, Runtime Prompt.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use usecase-newsletter-digest for unrelated requests.
- | Name | Type | Required | Description |

## Copy-And-Paste Prompt
```text
Use the Usecase newsletter digest human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the cowork-os/cowork-os skill entry for `usecase-newsletter-digest`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Newsletter Digest

## Purpose

Summarize newsletter/email feed messages from the last N hours and propose follow-ups.

## Routing

- Use when: Use when the user asks to summarize newsletter/email feed messages from the last N hours and propose follow-ups.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Newsletter Digest: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.

## Trigger Examples

### Positive

- Use the usecase-newsletter-digest skill for this request.
- Help me with newsletter digest.
- Use when the user asks to summarize newsletter/email feed messages from the last N hours and propose follow-ups.
- Newsletter Digest: provide an actionable result.

### Negative

- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use usecase-newsletter-digest for unrelated requests.
- This request is outside newsletter digest scope.
- This is conceptual discussion only; no tool workflow is needed.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| channel | select | Yes | Where the newsletter feed arrives |
| chat_hint | string | Yes | Name/keyword to identify the chat in channel_list_chats results |
| since | string | No | Time window (e.g., "24h") |
| message_limit | number | No | How many messages to fetch |
| output_format | select | No | How to format the digest |

## Runtime Prompt

- Current runtime prompt length: 882 characters.
- Runtime prompt is defined directly in `../usecase-newsletter-digest.json`.