date-picker-widget
Skill8 starsChanged 7 months agoMITView on GitHub
Picks a date in a calendar-style date-picker widget — clicks the input, navigates months if needed, clicks the target day. The famous "vision agent failure case" that motivates this whole library.
In this repository14 other files it gives its agents.
- detect-captchaSkill
- dismiss-cookie-bannerSkill
- dismiss-newsletter-popupSkill
- exit-tracking-popupSkill
- extract-table-paginationSkill
- fill-multi-step-formSkill
- handle-infinite-scrollSkill
- handle-modal-dialogSkill
- login-flowSkill
- pagination-next-pageSkill
- searchable-dropdownSkill
- search-and-filterSkill
- upload-download-fileSkill
- verify-page-loadedSkill
The file
Files
Date Picker Widget
When to invoke
The user task requires picking a date (booking demos, scheduling
demos, date-range filters). vars.target_date is an ISO-8601 date
string (e.g., "2026-06-15").
The matcher recognizes calendar widgets via their ARIA roles. The
<input type="date"> native picker is the easy path — fill it
directly. The hard path is custom calendars (booking.com,
airbnb.com, hotels.com style), and that's what this skill targets.
Recipe
Easy path (native <input type="date">)
- fill selector="input[type='date']" value="$vars.target_date"
Hard path (custom calendar)
- wait_for_dom_ready timeout=3s
- click selector="[data-element='calendar-trigger'], [aria-label*='date' i][role='button']"
- wait_for_selector selector="[role='dialog'][aria-label*='calendar' i]" state=visible timeout=2s
- click selector="[aria-label='$vars.target_date'], [data-date='$vars.target_date']"
- wait extra=300ms
(Month-navigation logic — "click 'next month' until target month is visible" — is
deferred to v0.2 with the loop verb. v0.1 handles the case where the target
date is already visible on the initial calendar open. For booking-style sites
where check-in is in the current month, this is enough.)
Success criteria
- assert input_has_value selector="[data-element='check-in']" value_contains="$vars.target_date"
When NOT to use
- Date range pickers — use
vars.range_start/vars.range_endand the agent composes two invocations. - Calendars that don't expose
aria-labelordata-dateattributes on day cells. Vision fallback is currently the only recourse.
Known failures
- Disabled past dates: the click is ignored. The agent sees no state change and should re-plan.
- Calendars opening below the fold: the day cells render but
aren't clickable until scrolled. Add a
scroll_into_viewstep. - Calendars that require keyboard nav only: v0.1 doesn't support
keyboard nav loops; the
press_keyprimitive could be composed but there's no standardized pattern. - Month navigation: v0.1 only picks dates in the currently-visible month. v0.2 adds month-navigation loops.
Related skills
dismiss-cookie-banner— booking sites are EU-heavy; cookie banner firstverify-page-loaded— wait for the calendar UI to rendersearchable-dropdown— often co-occurs (date + party-size selectors)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

