Write a Session Abstract That Gets Accepted

Turns a talk idea into a CFP-ready submission: title options, an abstract within the word limit, learning outcomes and a bio, checked against the guidelines and for pitch language.

Example prompts

Once the skill is added, start a chat with one of these and attach your file if you have one.

  • Here's our CFP guidelines page text and my talk idea. Write a 150-word abstract and 3 learning outcomes.

  • Rewrite this abstract so it doesn't read like a product pitch.

  • Give me 5 title options for a talk on cutting trade show costs by 30%.

What this skill does

This skill writes conference session submissions fitted to a specific call for papers. It pulls the hard limits and stated priorities from the guidelines you paste, then writes five title options across different angles, an abstract that fits the word limit exactly, three learning outcomes and a speaker bio.

Before handing over, it runs a pitch check that strips product names and hype reviewers mark down, and a fit check that rates the draft against each CFP criterion with a fix for anything weak. It works for field marketers writing on behalf of executives and customer co-presenters too.

When to use it

  • Submitting to a conference call for papers or call for speakers
  • Rewriting an abstract that reads like a product pitch
  • Writing title options for a talk
  • Ghostwriting a submission for an executive or customer
  • Editing session descriptions for your own event's agenda

How it works

  1. 1Extract the rulesLists every word limit, required field, format and stated priority from the pasted CFP.
  2. 2Find the promiseWrites the one sentence that says what attendees will be able to do and why this speaker can teach it.
  3. 3Draft the submissionWrites title options, the abstract, learning outcomes, level, format and bio to the exact limits.
  4. 4Check for pitchRemoves product names, feature lists and hype, and replaces them with the method or the lesson.
  5. 5Check the fitRates the draft against each CFP criterion and gives a fix for anything weak.

What you'll need

  • CFP guidelines text
  • Talk idea and evidence
  • Speaker background
  • Preferred format and level

What you get

A submission pack with the extracted CFP rules, a one-sentence promise, five title options with a recommendation, the abstract with its word count, three learning outcomes, level and format, a bio with its word count, a fit check table, a list of pitch phrases removed and any open questions.

Tips

  • Paste the full CFP guidelines, including scoring criteria if they're published.
  • Let a customer's story lead the abstract; reviewers favor sessions attendees can apply anywhere.
  • Only include numbers the speaker can source from their own work.
  • Give panels a clear point of disagreement so they don't read as filler.

What's in the download

  • session-abstract-writer/SKILL.md6.0 KB
  • session-abstract-writer/references/examples.md2.3 KB
  • session-abstract-writer/references/review-red-flags.md1.7 KB
Read the SKILL.md
---
name: session-abstract-writer
description: Writes and tightens conference session submissions for a call for papers or call for speakers. Produces title options, an abstract within the word limit, learning outcomes, audience level, session format and a speaker bio fitted to a specific CFP's guidelines and audience, then runs a fit check and strips product-pitch language reviewers reject. Use when submitting to a CFP, applying to speak at a conference, rewriting an abstract that reads like a pitch or editing session descriptions for an agenda.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: content-and-speakers
  source: https://eventmarketingsoftware.com/skills/session-abstract-writer
---

# Session Abstract Writer

Turns a talk idea into a submission a program committee wants to accept: a clear title, an abstract that fits the word limit, outcomes attendees can use, and a bio that shows why this speaker. It writes to the specific call for papers in front of it, because every CFP scores slightly differently.

Reviewers usually reject for the same reasons: it's a product pitch, it's vague, it doesn't fit the audience, or it ignores the guidelines. This skill checks for all four.

## Intake

If the user has an `event-context.md` file, read it first (company, positioning, approved customer stories) and don't ask for what it answers.

Ask for whatever is missing in ONE message:

1. The CFP text: guidelines, tracks or themes, audience, word and character limits, required fields, formats offered, scoring criteria if published, deadline. Pasted text, not a link.
2. The talk idea in a few sentences: the problem, the argument, what's new or contrarian, and the evidence (a story, data the speaker owns, a framework).
3. Speaker or speakers: role, company, relevant experience, prior talks, and whether a customer co-presents.
4. Preferred format (talk, panel, workshop, case study, lightning) and level (beginner, intermediate, advanced).
5. What's off limits: product names, unreleased work, customer names without approval.

If the user only has a topic, propose 3 angles first and ask them to pick one.

## Data sources

- Works from pasted text and uploaded documents only. No connectors needed.
- Don't fetch the CFP page or any URL. Ask the user to paste the guidelines.
- Never require a paid service.

## Method

1. **Extract the rules.** List the CFP's hard limits (word counts per field, title length, number of outcomes, format list) and what it says it values. Keep this list visible; every draft gets checked against it.
2. **Find the one-sentence promise.** "Attendees will leave able to [do X] because [speaker] has [evidence]." If you can't write it, ask the user for the missing evidence before drafting.
3. **Write 5 title options** across angles: outcome, number, contrarian, question, plain descriptive. Keep under the CFP's limit (default about 70 characters). No puns that hide the topic.
4. **Write the abstract** in this order: the problem the audience has (in their words), why the usual approach falls short, what this session covers and the evidence behind it, what attendees take away. Fit the word limit exactly; give the count.
5. **Write learning outcomes.** 3 by default, each starting with a measurable verb (compare, build, apply, decide, calculate, avoid), each something an attendee could do the next week.
6. **Set level and format.** Pick from the CFP's list and justify in one line. Suggest a format change if the content fits a workshop or case study better.
7. **Write the bio** in third person at the requested length: current role, the credential that matters for this talk, one concrete result or experience, optional human detail. Cut "thought leader", "visionary", "passionate".
8. **Run the pitch check.** Use [references/review-red-flags.md](references/review-red-flags.md). Remove product names, feature lists and "our platform" language unless the CFP is a vendor track. Replace with the method, the lesson or the customer's story. Make sure a competitor's customer would still find the session useful.
9. **Run the fit check** and score each CFP criterion as Strong, OK or Weak, with the fix for each Weak.

Domain rules that matter:
- Respect every limit exactly. Over-limit submissions are often rejected unread.
- Customer co-presenters make a session stronger; the customer's story leads, not the vendor's.
- Claims with numbers need a source the speaker owns ("our 2025 customer data") or must be cut.
- Panels need a stated point of tension or they read as filler.
- Don't promise content the speaker can't deliver in the time slot.

## Output template

```
## CFP rules extracted
[bulleted list of limits and stated priorities]

## One-sentence promise

## Title options
1. [Outcome] ...
2. [Number] ...
3. [Contrarian] ...
4. [Question] ...
5. [Descriptive] ...
Recommended: [n], because ...

## Abstract ([n] words, limit [n])

## Learning outcomes
1. ...

## Level and format

## Speaker bio ([n] words)

## Fit check
| CFP criterion | Rating | Why | Fix |
|---|---|---|---|

## Pitch check
[Phrases removed or changed, and why]

## Open questions
```

Before and after examples: [references/examples.md](references/examples.md).

## Validation checklist

- [ ] Every field is within the CFP's limit, with counts shown.
- [ ] Title options cover different angles and none hides the topic.
- [ ] Abstract names the audience's problem in the first two sentences.
- [ ] Each learning outcome starts with an action verb and is doable next week.
- [ ] No product names or feature lists unless the CFP allows them.
- [ ] Every number in the abstract has a source the speaker owns.
- [ ] Bio has no unsupported superlatives.
- [ ] House style: contractions, plain words, no dashes as punctuation.

## Approval gates

- Return drafts only. Never submit to a CFP portal or send email on the user's behalf.
- If a customer is named, remind the user to get the customer's approval before submitting.

## Related skills

cfp-review-scorer (the organizer's side of the same process), speaker-management (once accepted), event-social-kit (promoting the session).

FAQ

How do I write a conference abstract that gets accepted?
Follow the CFP's limits exactly, open with the audience's problem in their words, explain why the usual approach falls short, say what the session covers and the evidence behind it, and end with concrete takeaways. Keep product names out. The skill drafts all of this and checks it against each CFP criterion.
Why do CFP reviewers reject sessions?
The most common reasons are a thinly veiled product pitch, vague promises like best practices, no evidence, a poor fit with the track or level, going over word limits, and titles that hide the topic. The skill runs a red flag check for each of these and tells you what it changed.
How many learning outcomes should a session have?
Three is a common default unless the CFP asks for a different number. Each should start with an action verb like build, compare or apply, and describe something an attendee could do the following week. The skill writes them to match the guidelines you paste.
Can I use this for a customer speaker?
Yes. Customer co-presenters usually strengthen a submission, especially when their story leads. The skill writes the abstract and bio around the customer's experience and reminds you to get their approval, and their comms team's if needed, before submitting anything that names them or their results.