What problem does it solve? Deciding who gets which level of lab access (Slack guest, full workspace member, Vector account) is error-prone and inconsistent, especially for external collaborators with varying engagement levels. This Skill standardizes access-invite proposals, roster updates, and invite emails behind a consistent decision process. ## Core Features & Use Cases - Access Decision Rules: Chooses between Slack Connect guest invites and full workspace membership, including the DCS email prerequisite for UofT workspace members. - Collaborator Subgroups: Maps external collaborators to one of eight subgroups (interviewee through external_prof) that determine exactly which access items they receive. - Roster Integration: Calls adminbot lab-member tools to upsert members with the correct privilege level before proposing access changes, and maintains the Vector sponsor roster via a monthly cron sync. - Email Templates: Provides ready-to-fill templates for Slack Connect invites, DCS email setup instructions, practices docs, and recommendation letter declines. - Use Case: A sponsor asks to onboard a new coauthor working 20 hours per week. The Skill classifies them as coauthor_major, upserts them into the lab roster, drafts the Slack Connect invite email, and ensures they appear on the Vector sponsor roster. ## Quick Start Ask the assistant to propose Slack and Vector access for a new external collaborator, providing their name, email, project, and expected engagement level.
