القائمة
First-run setup for Schedule-Manager. Picks MCP aliases, creates Drive folder tree, optionally nominates a diary workspace, writes config.json.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Manage meeting agendas as Google Docs — create, link to a calendar event description, share with attendees, or email. One skill, four sub-actions.
Assign due dates to Todoist tasks in batch. Walks the user through each undated task and applies their choice.
Assign priorities to Todoist tasks in batch. Walks the user through each unprioritised task and applies their choice.
Create multiple Google Calendar events from a structured list. Resolves attendees once across the batch, confirms the table, then writes.
Create multiple Todoist tasks from a structured list. Confirms the table, then writes serially.
Create a single Google Calendar event. Resolves attendees via the contacts MCP. Optionally links a Drive doc (agenda) into the description.
| name | onboard |
| description | First-run setup for Schedule-Manager. Picks MCP aliases, creates Drive folder tree, optionally nominates a diary workspace, writes config.json. |
Run this once before any other Schedule-Manager skill. Subsequent skills require $CLAUDE_USER_DATA/schedule-manager/config.json to exist.
Resolve data root.
DATA_ROOT="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/schedule-manager"
mkdir -p "$DATA_ROOT"
Pick MCP aliases. Ask the user for the MCP server aliases configured in their environment for:
gemini-cli-extensions/workspace.Diary-Contacts-MCP or any People API MCP.doist/todoist-mcp.Verify each alias resolves to a tool list including the expected capabilities. If a given MCP isn't registered, tell the user how to add it; do not proceed without all three.
Create Drive folder tree. Using the workspace MCP, create (or locate) folders under a root the user nominates (default name Schedule-Manager):
AgendasMinutesWrapupsMorning-Briefs (optional, ask)Capture each folder ID for config.json.
Diary workspace (optional). Ask the user if they want a markdown diary. If yes, ask for an absolute path (suggest ~/Documents/Diary or a synced folder; do not default to $CLAUDE_USER_DATA). Verify the folder exists or create it. If no, set diary.enabled = false.
Defaults. Confirm calendar (default primary), Todoist project (default inbox), timezone (default user's locale).
Write config.json following the schema in lib/CONFIG.md. Use chmod 600 on the file.
Tell the user what was written and which skills are now ready. Mention setup-automation for hooking up morning-brief / wrapup on a schedule.
Re-running should detect existing config and offer to update individual sections (MCP aliases, folder IDs, diary workspace) rather than overwriting blindly.