{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "newsletter-brief",
  "name": "Newsletter brief",
  "category": "Writing",
  "summary": "Turn an update into a short newsletter item with a useful next step.",
  "use_cases": [
    "Community newsletters",
    "Product-update digests",
    "Member bulletins"
  ],
  "word_count": 144,
  "url": "https://sho.rten.it/methods/newsletter-brief/",
  "instructions_url": "https://sho.rten.it/methods/newsletter-brief/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/newsletter-brief/SKILL.md",
  "json_url": "https://sho.rten.it/methods/newsletter-brief/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/newsletter-brief/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#newsletter-brief",
  "skill_name": "newsletter-brief",
  "skill_description": "Turn an update into a short newsletter item with a useful next step. Use for Community newsletters, Product-update digests, Member bulletins.",
  "agents_md_url": "https://sho.rten.it/methods/newsletter-brief/AGENTS.md",
  "sources": [],
  "instructions": "Condense the supplied update into one newsletter item for the stated audience. Keep it useful when read among several unrelated items. Identify what changed, who it affects, when it matters, and any supported next step.\n\nWrite an informative short heading and one compact paragraph. Add a separate action line only if it improves scanning. Keep dates, access conditions, prices, exceptions, and a supplied destination needed to act. If the source gives no action, finish with the update; do not invent a subscription, registration, or purchase request.\n\nRemove greetings, repeated announcements, internal planning history, generic enthusiasm, and background the reader does not need. Use a neutral or supplied house tone. Preserve tentative plans as tentative and attribute claims that come from someone else. Do not convert an internal draft into an approved public announcement. Return only the newsletter item, without an explanation of the edit.",
  "example": {
    "context": "Member newsletter item",
    "before": "We would like to share an update about Saturday opening hours at the repair workshop. Starting on 3 October, the workshop will open on the first Saturday of each month from 10:00 to 13:00. This is a three-month trial. Members may bring one small electrical item per visit. Volunteers will assess it, but repair is not guaranteed. Advance booking is required through the member portal. Weekday opening hours will stay the same. We hope the extra session will be useful to members.",
    "after": "Saturday repair sessions start 3 October\n\nThe workshop will open 10:00–13:00 on the first Saturday of each month for a three-month trial. Members can bring one small electrical item per visit. Volunteers will assess it; repair is not guaranteed. Book in advance through the member portal. Weekday hours stay the same.",
    "must_preserve": [
      "Start date and recurring hours",
      "Three-month trial",
      "Members: one small electrical item per visit",
      "Repair is not guaranteed",
      "Volunteers will assess the item",
      "Advance booking required through the member portal",
      "Weekday hours unchanged"
    ],
    "omitted": [
      "Drops the greeting and a general expression of enthusiasm."
    ],
    "kind": "illustrative"
  }
}