Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when proposing meeting times to someone — turns open availability into a tight, ranked offer of exactly the number of slots asked for, each annotated with the relevant timezone(s), honoring every stated constraint and never landing inside a declared no-meeting window. Do NOT use for detecting calendar conflicts or double-bookings (that is the conflict check upstream), for writing the meeting agenda, or for a general reply that happens to mention a time.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | 216% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 402% | 0% |
| case-01 | ✗→✗ | = Same ✗ | 208% | 0% |
| case-03 | ✗→✗ | = Same ✗ | 298% | 0% |
| case-04 | ✗→✗ | = Same ✗ | 533% | 0% |
Someone asks you to suggest times for a meeting. The times themselves are already conflict-free — some upstream check has confirmed the calendar is open. Your job is the offer: how those times get presented so the recipient can reply with a single pick.
Handed this, base models produce a wall of options — every open half-hour across the next week, hedged with "I also have other slots if none of these work," clock times with no timezone or only the sender's, no ranking, and often a slot that quietly violates something the requester already said. A good offer is the opposite: short, ranked, unambiguous about timezone, and clean of anything they told you to avoid.
not five. If no number is stated, offer a small ranked set (two or three), never an exhaustive dump of every open block.
the last is the fallback. Don't present them as an unordered pool.
the moment more than one zone is in play. When participants span timezones, show each proposed time in every relevant zone (for example, a slot rendered as both the East Coast time and the London time), not just yours. When only one zone is involved, still name it once so there is no guessing.
only," "not before 10," a hard deadline to meet by — whatever they said, every slot in the offer satisfies all of it. One convenient-but-non-conforming slot spoils the offer.
focus, block lunch, or hold no meetings after a certain hour, nothing in the offer may fall in that window — not even the last-resort option. A no-meeting window is a hard floor, not a soft preference to trade against convenience.
or listing every remaining opening. A tight ranked set is easier to answer than a grid.
If you cannot produce the requested number of valid slots without breaking a constraint or entering a no-meeting window, do not pad the list to hit the count. Offer the valid slots you do have, say plainly that the constraints allow only that many, and name what would have to give (a wider date range, a shorter duration) to get more. Fewer honest slots beat the requested count with one rule quietly broken.
Other measured skills in the registry, with their headline benchmark lift.