[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79F32YPJ8ETCE88FXHWNXHG":3,"skill-same:01M79F32YPJ8ETCE88FXHWNXHG":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79F32YPJ8ETCE88FXHWNXHG","outlook-calendar-group-scheduler",null,"Find and rank good meeting times for several people using Outlook Calendar data. Use when the user wants to schedule a meeting, compare candidate slots across attendees, find the best compromise time, or add a room\u002Fresource check after narrowing the attendee-compatible options.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Foutlook-calendar-group-scheduler\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: outlook-calendar-group-scheduler\ndescription: Find and rank good meeting times for several people using Outlook Calendar data. Use when the user wants to schedule a meeting, compare candidate slots across attendees, find the best compromise time, or add a room\u002Fresource check after narrowing the attendee-compatible options.\n---\n\n# Outlook Calendar Group Scheduler\n\nUse this skill when the scheduling problem is the task.\n\n## Relevant Actions\n\n- Use `get_schedule` for attendee and room\u002Fresource free-busy windows once you know the concrete schedule identifiers.\n- Use `find_available_slots` when the problem is mostly about the user's own calendar and buffered openings.\n- Use `search_events` or `list_events` when you need conflict context before ranking options.\n- Use `create_event` only after the winning slot and attendee set are settled.\n\n## Outlook Product Framing\n\n- Treat free\u002Fbusy visibility, work hours, and work location as first-class scheduling evidence when full event detail is unavailable.\n- Treat attendee response state and organizer logistics as part of scheduling, not just the final event body.\n- When rooms or resources are visible, treat them as Outlook-style scheduling constraints rather than a separate \"room finder\" workflow.\n\n## Workflow\n\n1. Ground the scheduling problem first: date window, duration, timezone, required attendees, optional attendees, and any hard constraints such as \"this week\", \"afternoons only\", or \"avoid lunch\".\n2. If the scheduling window is ambiguous, assess the meeting stakes before choosing a default search window. For relatively high-stakes meetings, go back to the user and suggest tightening the timeline, for example to the next week. For lower-stakes or more casual group scheduling, default to a near-term search such as the next 1 to 3 weeks.\n3. Normalize the request into explicit candidate windows before ranking anything.\n4. Rank slots, do not enumerate everything. Optimize for a short list of strong options.\n5. Treat `Busy` and `Out of Office` as harder constraints than `Tentative` or `Working Elsewhere` unless the user says otherwise.\n6. Prefer slots that minimize conflict cost, fit within work hours, and avoid avoidable hybrid-work friction such as forcing an in-office room meeting onto remote-heavy attendees.\n7. When rooms, resources, or building context are available, prefer slots that keep the meeting logistically coherent instead of treating time as the only variable.\n8. If shared-calendar visibility is partial, say when a recommendation is based on free\u002Fbusy signals rather than full event detail.\n\n## Ranking Heuristics\n\n- Favor required-attendee fit over optional-attendee fit.\n- Favor slots that avoid very early or very late local times for distributed attendees.\n- Favor slots that stay inside work hours and avoid consuming the only large free block in someone's day unless the meeting is clearly important.\n- Favor a small number of high-confidence options over a long weak list.\n- When two slots are similar, prefer the one that causes less calendar fragmentation.\n- When one attendee is only `Tentative` or `Working Elsewhere`, describe that as a softer constraint instead of silently treating it as unavailable.\n- When one option aligns better with attendees' work locations or room logistics, explain that advantage explicitly.\n\n## Output Conventions\n\n- Return 2-4 candidate slots by default.\n- For each slot, say why it works and who, if anyone, would be inconvenienced.\n- If there is no clean option, say what tradeoff the best slot is making.\n","# Outlook Calendar Group Scheduler\n\nUse this skill when the scheduling problem is the task.\n\n## Relevant Actions\n\n- Use `get_schedule` for attendee and room\u002Fresource free-busy windows once you know the concrete schedule identifiers.\n- Use `find_available_slots` when the problem is mostly about the user's own calendar and buffered openings.\n- Use `search_events` or `list_events` when you need conflict context before ranking options.\n- Use `create_event` only after the winning slot and attendee set are settled.\n\n## Outlook Product Framing\n\n- Treat free\u002Fbusy visibility, work hours, and work location as first-class scheduling evidence when full event detail is unavailable.\n- Treat attendee response state and organizer logistics as part of scheduling, not just the final event body.\n- When rooms or resources are visible, treat them as Outlook-style scheduling constraints rather than a separate \"room finder\" workflow.\n\n## Workflow\n\n1. Ground the scheduling problem first: date window, duration, timezone, required attendees, optional attendees, and any hard constraints such as \"this week\", \"afternoons only\", or \"avoid lunch\".\n2. If the scheduling window is ambiguous, assess the meeting stakes before choosing a default search window. For relatively high-stakes meetings, go back to the user and suggest tightening the timeline, for example to the next week. For lower-stakes or more casual group scheduling, default to a near-term search such as the next 1 to 3 weeks.\n3. Normalize the request into explicit candidate windows before ranking anything.\n4. Rank slots, do not enumerate everything. Optimize for a short list of strong options.\n5. Treat `Busy` and `Out of Office` as harder constraints than `Tentative` or `Working Elsewhere` unless the user says otherwise.\n6. Prefer slots that minimize conflict cost, fit within work hours, and avoid avoidable hybrid-work friction such as forcing an in-office room meeting onto remote-heavy attendees.\n7. When rooms, resources, or building context are available, prefer slots that keep the meeting logistically coherent instead of treating time as the only variable.\n8. If shared-calendar visibility is partial, say when a recommendation is based on free\u002Fbusy signals rather than full event detail.\n\n## Ranking Heuristics\n\n- Favor required-attendee fit over optional-attendee fit.\n- Favor slots that avoid very early or very late local times for distributed attendees.\n- Favor slots that stay inside work hours and avoid consuming the only large free block in someone's day unless the meeting is clearly important.\n- Favor a small number of high-confidence options over a long weak list.\n- When two slots are similar, prefer the one that causes less calendar fragmentation.\n- When one attendee is only `Tentative` or `Working Elsewhere`, describe that as a softer constraint instead of silently treating it as unavailable.\n- When one option aligns better with attendees' work locations or room logistics, explain that advantage explicitly.\n\n## Output Conventions\n\n- Return 2-4 candidate slots by default.\n- For each slot, say why it works and who, if anyone, would be inconvenienced.\n- If there is no clean option, say what tradeoff the best slot is making.\n",{"name":5,"description":7},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Foutlook-calendar-group-scheduler","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill outlook-calendar-group-scheduler",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill outlook-calendar-group-scheduler",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill outlook-calendar-group-scheduler","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Foutlook-calendar-group-scheduler\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",274,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Foutlook-calendar-group-scheduler\u002Fagents\u002Fopenai.yaml",[52,59,66,73,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]