conference-cfp-submission

Writes submission-ready conference CFP proposals with titles, abstracts, takeaways, and reviewer-only fields.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill conference-cfp-submission-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conference-cfp-submission
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/conference-cfp-submission
Command: npx skills add https://github.com/samber/developer-relations-skills --skill conference-cfp-submission-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a talk idea into a conference proposal that survives committee review is hard: abstracts get rejected for vague angles, missing evidence, wrong tracks, or rule violations like per-person caps and AI policies. This Skill produces every field of a specific event's submission form, written to the criteria reviewers actually score on. ## Core Features & Use Cases - Full proposal pack generation: Produces track choice, ranked title options, an attendee-facing abstract with character counts, verb-first takeaways, a minute-budgeted outline, reviewer-only fields, bio, and supplemental links, all matched to the event's caps and rules. - Angle selection and event targeting: Ranks war story, contrarian thesis, and practical playbook angles against the user's constraints, and helps choose which conferences to target with a season-wide submission calendar. - Reviewer-style self-review: Scores the draft on Content, Originality, Relevance, and Speaker axes with written reasons, plus a pre-submit checklist covering anonymity rules, submission caps, panel composition, and AI policies. - Use Case: A staff engineer with an incident story and a CFP deadline in nine days gets a ranked set of angles, a compliant proposal pack for the target event, and a scored self-review before hitting submit. ## Quick Start Ask the assistant to turn your talk idea into a submission-ready CFP proposal for a specific conference, including the abstract, takeaways, and reviewer-only fields.

Frequently Asked Questions about conference-cfp-submission

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conference CFP proposal that gets accepted?

Start from the event's CFP page, pick an angle backed by first-hand experience, and write the abstract for attendees with a hook, promise, and payoff. Then fill reviewer-only fields with evidence, and self-score the pack on content, originality, relevance, and speaker credibility before submitting.

How do I choose which conferences to submit my talk to?

Rank candidate events by track fit, audience fit, vendor neutrality, your track record, compliance lead time, and travel fit rather than name recognition. Plan deadlines across a season in one calendar and sequence a regional event before a flagship submission.

What should go in the notes to reviewers field of a CFP form?

Use reviewer-only fields to argue your case: why you are the right speaker, what material already exists, how the demo is derisked, and what makes the angle new for this event. Never repeat the abstract, since that wastes the only persuasive space reviewers see.

Can I submit the same proposal to multiple conferences?

Yes, a proposal is reusable across a season, but avoid overlapping review windows unless you have decided which acceptance you would take. Also check each event's recycled-content rule if the talk was already delivered elsewhere.

What are common reasons conference talk proposals get rejected?

Common rejection patterns include a topic with no angle, credibility asserted rather than evidenced, scope too broad for the slot, the wrong track, and violating published rules like per-person submission caps or AI-generated text policies.

Does anonymous review change how I write my abstract?

Yes. When the first review round is anonymous, the title, abstract, and outline must not name you or your employer. Disclose affiliation only in the form fields that ask for it, and confirm the review model on the event's CFP page.