# CFP Blueprint

> Design the call for papers of a technical event - the published call, not the selection behind it - then write the
> organizers' design brief or the public call itself. Enter the event date, the planned CFP dates, the formats with their
> form fields, the review posture, the drafted criteria and the drafted speaker benefits. Built on the SkillSafe skill
> @samber/event-cfp-design (samber/dev-event-organizer-skills, MIT).

https://cfp-blueprint.skillsafe.ai/

## What is free
- The timeline against the sourced floor: open at least a month, close at least 6-8 weeks before the event, two weeks to review, speakers told in time to travel; below the floor the open call is deleted and the program goes invited.
- The timeline rung the dates make and the page's pick (standard by default, floor-compressed under a hard date, long for a first edition, international speakers or a mentor pool), with the promotion cost of a long window.
- The call's formats matched to the structure's, each with its own form; the form depth (minimal, standard, extended), the abstract and "why me" split, the abstract length and the per-person cap.
- The review posture: named, opt-in anonymous (a platform capability, not a fairness posture) or mandatory blind, with the two-phase mechanics a blind call must publish.
- The drafted criteria against the six community-call points, the open-space routing or the lesson-transfer test, and only confirmed benefits with the free-ticket floor.
- First-time-speaker support (worked examples, encouragement, proposal mentorship), slots held outside the call, and the outreach warning.
- Form fields CSV, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (brief or call), `event`, `design` and `facts`.
- `brief` replies with `summary`, `timeline`, `formats`, `form`, `review`, `criteria`, `benefits`, `support`, `measurement` and `caveats`; the page holds every pick, flag, date and count to its own.
- `call` replies with `title`, `intro`, `dates`, `formats`, `cap`, `review`, `criteria`, `benefits`, `firsttimers`, `reserved` and `contact`; the page requires the planned dates, every structure format with its slots, the cap, every drafted criterion, only confirmed benefits, and the blind-review phase when blind. Not available below the timeline floor.

## Links
- API tutorial: https://cfp-blueprint.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-cfp-design