Turn a week of saved links into a newsletter draft in your voice
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and turn a week of saved links into a newsletter draft in your voice.
LLMPrompt
Prompt
Copied 0
Draft this week's issue of my newsletter, [newsletter name], for [audience]. Links I saved this week: [paste links, or point to the file, bookmark folder or read-later list]. Three past issues, so you can match my voice: [paste or link]. Format: [intro of 2-4 sentences], then [3-5] themed sections, then [a short "also worth a look" list]. Step 1. Open every link. For each one, record: title, author, publish date, and whether you could read the full text (yes, partly, no). If a page is paywalled, blocked, or you only saw the URL, mark it "no". Do not summarise any page marked "no". STOP and show me this list before you write. Step 2. After I reply, for each readable link write a summary of 2-3 sentences with one concrete detail from the page. Keep numbers exactly as the page states them. If you quote, copy the words exactly and keep the quote under 20 words. Step 3. Group the items into themes. Drop items that do not fit the audience and tell me which ones you dropped and why. Step 4. Write the issue in my voice. Use short sentences. Do not add opinions I have not given you. Mark any place you want my own take with [MY TAKE: add your view here]. Rules: - Every item links to its source. - Never invent a title, author, book or statistic. If you are unsure, leave it out and tell me. - Do not send, schedule or publish anything.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/draft-a-newsletter-from-saved-links - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "draft-a-newsletter-from-saved-links",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}