Guidelines for writing or refining conference presentation abstracts. Use this skill when creating, editing, or reviewing abstracts for conference talk submissions.
This skill provides guidance for crafting effective conference presentation abstracts that grab attention and communicate value clearly.
Before diving into abstract writing, ask the user:
"Are you targeting a specific conference? If so, I can research past talks and abstracts to help tailor your submission. Would you like me to do that first?"
If yes, use the conference-research skill to:
Then return here with those insights to inform the abstract writing.
Based on Kent Beck's approach, aim for an abstract with four key sentences (flexibly applied):
[Problem]: Many developers struggle with testing code that uses HttpClient. [Why it matters]: Without proper testing, bugs slip through and refactoring becomes risky. [Startling sentence]: You can fully mock HttpClient in three simple patterns without any external libraries. [Implication]: Attendees will leave with reusable patterns they can apply immediately in their own projects.
When the abstract needs to hint at depth, remember the full talk should follow:
When refining an existing abstract: