{ "schema_version": 2, "kind": "shortening-method", "format": "agent-skill", "id": "abstract", "name": "Abstract", "category": "Writing", "summary": "Condense a complete report into its purpose, method, findings, and limits.", "use_cases": [ "Report abstracts", "Project summaries", "Study overviews" ], "word_count": 151, "url": "https://sho.rten.it/methods/abstract/", "instructions_url": "https://sho.rten.it/methods/abstract/SKILL.md", "skill_url": "https://sho.rten.it/methods/abstract/SKILL.md", "json_url": "https://sho.rten.it/methods/abstract/llms.txt", "plain_text_url": "https://sho.rten.it/methods/abstract/prompt.txt", "license": "MIT", "sources_url": "https://sho.rten.it/sources/#abstract", "skill_name": "abstract", "skill_description": "Condense a complete report into its purpose, method, findings, and limits. Use for Report abstracts, Project summaries, Study overviews.", "agents_md_url": "https://sho.rten.it/methods/abstract/AGENTS.md", "sources": [], "instructions": "Write a compact, self-contained abstract of the supplied report. Use this for the report's own overview, rather than a review that evaluates another author's work.\n\nIdentify the question or purpose, the approach, the principal result, and the conclusion supported by that result. Give each necessary part a short sentence. Use one paragraph unless a structured abstract is requested. Keep the population or setting, comparison, sample size, material quantities, and limits needed to interpret the finding. Preserve whether work is proposed, ongoing, or complete.\n\nCut background that does not explain the question, procedural detail that does not affect interpretation, repeated results, and claims of importance unsupported by the report. Do not turn correlation into causation or a pilot result into a general finding. If the report supplies no result, say so; do not fill a conventional abstract section with invented content. Return only the abstract, within a requested limit when accuracy permits.", "example": { "context": "Abstract for a completed pilot report", "before": "Our project set out to find whether an optional reminder could reduce missed equipment returns. We ran a four-week pilot with 80 library borrowers. Forty borrowers opted in to a reminder, while 40 did not. In the reminder group, 6 borrowers returned equipment late. In the other group, 12 returned it late. These counts suggest that reminders may help. However, borrowers chose whether to receive a reminder, so the pilot cannot establish that reminders caused the difference. A randomized follow-up would test that question.", "after": "A four-week pilot examined optional reminders for 80 library borrowers. Late returns occurred among 6 of 40 reminder recipients and 12 of 40 nonrecipients. Reminders may help, but self-selection prevents a causal conclusion. A randomized follow-up could test the effect.", "must_preserve": [ "Four weeks and 80 borrowers", "6 of 40 versus 12 of 40 late returns", "Optional participation prevents a causal conclusion", "Randomized follow-up is proposed, not completed" ], "omitted": [ "Removes repeated descriptions of the groups and the project setup." ], "kind": "illustrative" } }