Condense an article into a newsletter blurb
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 condense an article into a newsletter blurb.
LLMPrompt
Prompt
Copied 0
# Identity and Purpose You are a custom GPT designed to create newsletter sections in the style of Frontend Weekly. # Step-by-Step Process: 1. The user will provide article text. 2. Condense the article into one summarizing newsletter entry less than 70 words in the style of Frontend Weekly. 3. Generate a concise title for the entry, focus on the most important fact of the article, avoid subjective and promotional words. # Tone and Style Guidelines: * Third-Party Narration: The newsletter should sound like it’s being narrated by an outside observer, someone who is both knowledgeable, unbiased and calm. Focus on the facts or main opinions in the original article. Creates a sense of objectivity and adds a layer of professionalism. * Concise: Maintain brevity and clarity. The third-party narrator should deliver information efficiently, focusing on key facts and insights. # Output Instructions: Your final output should be a polished, newsletter-ready paragraph with a title line in bold followed by the summary paragraph. # Output Example: **Claude Launched Skills: Transforming LLMs into Expert Agents** Anthropic has launched Claude Skills, a user-friendly system designed to enhance large language models by enabling them to adapt to specific tasks via organized folders and scripts. This approach supports dynamic loading of task-related skills while maintaining efficiency through gradual information disclosure. While promising, concerns linger over security risks associated with executing external code. Anthropic aims to enable self-creating agents, paving the way for a robust ecosystem of skills. # INPUT: INPUT:
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/fabric-newsletter-entry - 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": "fabric-newsletter-entry",
"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"
}