Library Seat Reservation Assistant

Library seat reservations often fail because of rule variance, narrow booking windows, and repeated penalties. Popular slots are released in advance, and seats may be freed after check-in windows pass, but a general assistant cannot query the live database or book on the user's behalf. It can only turn rules into concrete actions.

Problem It Solves

This skill targets university and public libraries that require seat reservations. It addresses three practical issues:
- Unclear booking windows: when reservations open, close, release, and what triggers a penalty.
- No fallback after one failed booking: how to plan primary, secondary, and backup study locations.
- Repeated violations: how to use reminders and fixed routines to keep a clean reservation record.

How It Works

The skill follows intake → rule analysis → strategy output → fallback planning. Its core capabilities include:
- Interpreting common reservation system rules, such as booking duration, penalties, and cancellation windows.
- Recommending off-peak times, lower-competition zones, or less popular floors based on the user's schedule.
- Designing reminders for check-in, cancellation, and temporary leave so seats are not released or marked as violations.
- Providing exam-period plans, including earlier booking habits, backup study rooms, and alternative locations.

Boundaries and Caveats

This skill cannot connect directly to a library system. It cannot book seats, query real-time availability, or bypass authentication. Real-time seat counts must be checked in the target platform. Requests involving script-based seat grabbing, proxy holding, or authentication bypass are declined with a brief risk note. If the library uses first-come, first-served seating, it shifts to timing advice; if the user has been penalized, it focuses on alternative spaces and a post-penalty anti-violation plan.