Rutgers SOC Skill
Use this skill when the user asks Rutgers class-planning questions.
For empty-room or room-availability requests, use the dedicated soc-room-finder skill.
Tool map
- •Find courses:
rutgers_soc_search_courses - •Full course detail + sections:
rutgers_soc_get_course_details - •Find sections by day/time/instructor/classroom:
rutgers_soc_search_sections - •Lookup a specific index:
rutgers_soc_get_section_by_index - •Validate overlap across section indices:
rutgers_soc_check_schedule_conflicts - •Prerequisite and unlock chain:
rutgers_soc_get_prerequisites - •Room availability windows by building/day/time:
rutgers_soc_find_room_availability - •Terms/subjects/schools/core codes/instructors:
rutgers_soc_browse_metadata
Rules
- •Call Rutgers SOC tools directly. Do not delegate to another agent.
- •Prefer
rutgers_soc_search_coursesfirst when the request is broad. - •Use
rutgers_soc_get_course_detailsafter search when the user asks section availability or meeting details. - •Use
rutgers_soc_check_schedule_conflictswhenever the user compares multiple index numbers. - •Keep responses concise: include course string, title, open/closed status, and index numbers when relevant.
- •If a user gives ambiguous classroom terms, normalize using
rutgers_soc_search_sectionsclassroom filters.
/soc command usage
When user invokes /soc ..., interpret the remaining text as a Rutgers SOC request and use the mapped tools above.