{ "schema_version": 2, "kind": "shortening-method", "format": "agent-skill", "id": "email-thread", "name": "Email thread", "category": "Work", "summary": "Reduce a long email chain to its topic, decisions, and your next action.", "use_cases": [ "Long email chains", "Catching up on replies", "Inbox triage" ], "word_count": 120, "url": "https://sho.rten.it/methods/email-thread/", "instructions_url": "https://sho.rten.it/methods/email-thread/SKILL.md", "skill_url": "https://sho.rten.it/methods/email-thread/SKILL.md", "json_url": "https://sho.rten.it/methods/email-thread/llms.txt", "plain_text_url": "https://sho.rten.it/methods/email-thread/prompt.txt", "license": "MIT", "sources_url": "https://sho.rten.it/sources/#email-thread", "skill_name": "email-thread", "skill_description": "Reduce a long email chain to its topic, decisions, and your next action. Use for Long email chains, Catching up on replies, Inbox triage.", "agents_md_url": "https://sho.rten.it/methods/email-thread/AGENTS.md", "sources": [ { "title": "pnp/copilot-prompts · Summarize This Email Thread", "url": "https://github.com/pnp/copilot-prompts/blob/11e6e1e4d5b587f87e1fb4babbcda48c1c5c4746/samples/prompts/m365-outlook-thread-summary/README.md", "repository": "https://github.com/pnp/copilot-prompts", "revision": "11e6e1e4d5b587f87e1fb4babbcda48c1c5c4746", "path": "samples/prompts/m365-outlook-thread-summary/README.md", "license": "MIT", "license_url": "https://github.com/pnp/copilot-prompts/blob/11e6e1e4d5b587f87e1fb4babbcda48c1c5c4746/LICENSE", "license_file": "licenses/pnp--copilot-prompts.txt", "copyright": "Copyright (c) 2024 Microsoft 365 & Power Platform Community", "repository_stars": 875, "checked_at": "2026-09-10", "license_scope": "Root MIT license covers this repository's samples; no separate license or NOTICE files found in the pinned tree.", "adaptation": "Retains the exact three-part focus from the source. Makes it portable outside Outlook and adds chronology, ownership, and decision-status safeguards.", "author": "Sai Siva Ram Bandaru" } ], "instructions": "Summarize the supplied email thread in three concise bullets: main topic, key decisions, and what I need to do next.\n\nRead the thread in time order. Separate the latest agreed decision from earlier proposals, quoted replies, and superseded plans. Combine repeated points. Keep names, dates, amounts, and dependencies that affect the next action.\n\nIf the thread does not identify me, describe the named owner's action instead of assuming it is mine. State when no decision or next action is recorded. Preserve unresolved disagreements and missing deadlines. Do not infer agreement from silence or turn a request into a completed task. Return only the three bullets. Use the supplied text; this prompt does not request inbox access or send a reply.", "example": { "context": "Email thread with a superseded proposal and conditional agreement", "before": "Monday, 09:00 — Pat: Can we run the customer import on Tuesday? We still need Lee's mapping check.\nMonday, 11:00 — Lee: Tuesday is too soon. I can finish the check by Wednesday at 15:00 UTC. Thursday would work if it passes.\nMonday, 14:00 — Pat: Agreed: Thursday only if the mapping check passes. Lee, post the result in the migration ticket by Wednesday at 15:00 UTC. If it fails, pause the import; we have not picked another date.\nTuesday, 08:00 — Lee: Acknowledged. The check is still in progress.", "after": "- Topic: Customer import timing and mapping validation.\n- Decision: Thursday replaces Tuesday, conditional on a passing check. If it fails, pause; no alternative date agreed.\n- Next action: Lee posts the check result in the migration ticket by Wednesday, 15:00 UTC. Check still in progress.", "must_preserve": [ "Thursday supersedes Tuesday only if mapping check passes", "Failed check pauses import; no alternative date", "Lee owns posting result to migration ticket by Wednesday 15:00 UTC", "Check in progress, not complete; reader identity not supplied" ], "omitted": [ "Combines acknowledgements and repeated scheduling proposals; keeps the named owner rather than assuming the reader is Lee." ], "kind": "illustrative" } }