[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H9MC5WP19YV8ACRTZ5JM2F":3,"skill-same:01M6H9MC5WP19YV8ACRTZ5JM2F":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6H9MC5WP19YV8ACRTZ5JM2F","calendar-to-workflow",null,"Converts calendar events and schedules into Claude Code workflows, meeting prep\ndocuments, and standup notes. Use when the user mentions calendar events, meeting\nprep, standup generation, or scheduling workflows. Trigger with phrases like\n\"prep for my meetings\", \"generate standup notes\", \"create workflow from calendar\",\nor \"summarize today's schedule\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fskill-enhancers\u002Fcalendar-to-workflow\u002Fskills\u002Fcalendar-to-workflow\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"calendar to workflow","calendar","workflow","read","my","events","io","standup notes","claude code workflows","edit","write","schedule","Bash","meeting prep","code","generate","create","notes","documents","workflows","2026-11-10 10:12:30",false,"---\nname: calendar-to-workflow\ndescription: |\n  Converts calendar events and schedules into Claude Code workflows, meeting prep\n  documents, and standup notes. Use when the user mentions calendar events, meeting\n  prep, standup generation, or scheduling workflows. Trigger with phrases like\n  \"prep for my meetings\", \"generate standup notes\", \"create workflow from calendar\",\n  or \"summarize today's schedule\".\nallowed-tools: Read, Write, Edit, Bash, Glob, Grep\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex\ntags: [calendar, automation, meetings, productivity, workflow]\n---\n\n# Calendar to Workflow\n\nAutomate meeting preparation, standup generation, and workflow creation from calendar data.\n\n## Overview\n\nThis skill transforms calendar events and scheduling data into actionable Claude Code workflows. Rather than manually reviewing your calendar and preparing for each meeting, this skill reads calendar exports (ICS files, JSON feeds, or pasted event details) and produces structured outputs: meeting briefings with participant context, standup notes summarizing yesterday's activity, and repeatable workflow scripts that integrate calendar triggers with development tasks.\n\nThe skill bridges the gap between time management and development workflows. It understands meeting types (standup, sprint planning, 1:1, design review) and tailors its output accordingly, pulling in relevant repository activity, recent commits, and open PRs to provide full context for each event.\n\n## Instructions\n\n1. **Provide calendar data** in one of these formats:\n   - Paste raw ICS\u002FiCal content directly into the conversation\n   - Point to an `.ics` file on disk: \"read my calendar export at `~\u002Fcalendar.ics`\"\n   - Describe events manually: \"I have a standup at 9am, sprint planning at 10am, and a 1:1 with Sarah at 2pm\"\n\n2. **Specify the desired output** by telling Claude what you need:\n   - \"Prep for today's meetings\" -- generates a briefing document for each event\n   - \"Create standup notes from yesterday\" -- summarizes git activity and calendar events\n   - \"Build a weekly workflow\" -- creates a repeatable workflow script\n\n3. **Add context** to improve the output:\n   - Mention the repository or project: \"for the payments-api repo\"\n   - Specify participants: \"Sarah is the engineering manager\"\n   - Note priorities: \"focus on the deployment blockers\"\n\n4. **Review and refine** the generated output. The skill produces Markdown documents or shell scripts that you can edit, commit, or execute directly.\n\n## Output\n\nThe skill produces one or more of the following depending on the request:\n\n- **Meeting Briefing Document** (Markdown): For each meeting, includes the event title, time, participants, agenda items inferred from context, relevant recent commits or PRs, and suggested talking points.\n- **Standup Notes** (Markdown): A formatted summary covering what was done yesterday (from git log and calendar), what is planned today (from upcoming events), and any blockers identified from open issues or failing CI.\n- **Workflow Script** (Bash\u002FMarkdown): A repeatable workflow that can be triggered on a schedule, combining calendar checks with development tasks like running tests, updating dashboards, or posting summaries to Slack.\n\n## Examples\n\n### Example 1: Daily Meeting Prep\n\n**User:** \"I have a sprint planning at 10am with the backend team and a design review at 2pm. Prep briefings for both.\"\n\nThe skill will:\n1. Create a sprint planning briefing listing open sprint issues, velocity from the last sprint, and items ready for estimation.\n2. Create a design review briefing pulling recent UI\u002FUX changes from git history, linking to relevant Figma or mockup files found in the repo, and summarizing outstanding design-related issues.\n3. Output both as a single Markdown document with clear section headers.\n\n### Example 2: Standup Notes from Git Activity\n\n**User:** \"Generate standup notes for today based on yesterday's work.\"\n\nThe skill will:\n1. Run `git log --since=\"yesterday\" --oneline` to gather recent commits.\n2. Check for any open PRs with `gh pr list --author @me`.\n3. Identify any failing CI checks with `gh run list --limit 5`.\n4. Format the output as: \"Yesterday I... \u002F Today I plan to... \u002F Blockers: ...\"\n\n### Example 3: Weekly Recurring Workflow\n\n**User:** \"Create a Monday morning workflow that preps me for the week.\"\n\nThe skill will generate a script that:\n1. Reads the week's calendar events from an ICS file.\n2. Summarizes each day's meetings with participant counts and estimated time commitment.\n3. Pulls the current sprint board status.\n4. Outputs a weekly overview document to `docs\u002Fweekly-prep.md`.\n\n## Error Handling\n\n- **No calendar data provided:** Prompts the user to paste events, point to an ICS file, or describe their schedule.\n- **Unrecognized format:** Attempts best-effort parsing and asks the user to confirm the extracted events.\n- **Missing git context:** Skips repository-specific sections and notes which parts were omitted.\n- **Permission errors:** Suggests checking file permissions or GitHub CLI authentication status.\n","# Calendar to Workflow\n\nAutomate meeting preparation, standup generation, and workflow creation from calendar data.\n\n## Overview\n\nThis skill transforms calendar events and scheduling data into actionable Claude Code workflows. Rather than manually reviewing your calendar and preparing for each meeting, this skill reads calendar exports (ICS files, JSON feeds, or pasted event details) and produces structured outputs: meeting briefings with participant context, standup notes summarizing yesterday's activity, and repeatable workflow scripts that integrate calendar triggers with development tasks.\n\nThe skill bridges the gap between time management and development workflows. It understands meeting types (standup, sprint planning, 1:1, design review) and tailors its output accordingly, pulling in relevant repository activity, recent commits, and open PRs to provide full context for each event.\n\n## Instructions\n\n1. **Provide calendar data** in one of these formats:\n   - Paste raw ICS\u002FiCal content directly into the conversation\n   - Point to an `.ics` file on disk: \"read my calendar export at `~\u002Fcalendar.ics`\"\n   - Describe events manually: \"I have a standup at 9am, sprint planning at 10am, and a 1:1 with Sarah at 2pm\"\n\n2. **Specify the desired output** by telling Claude what you need:\n   - \"Prep for today's meetings\" -- generates a briefing document for each event\n   - \"Create standup notes from yesterday\" -- summarizes git activity and calendar events\n   - \"Build a weekly workflow\" -- creates a repeatable workflow script\n\n3. **Add context** to improve the output:\n   - Mention the repository or project: \"for the payments-api repo\"\n   - Specify participants: \"Sarah is the engineering manager\"\n   - Note priorities: \"focus on the deployment blockers\"\n\n4. **Review and refine** the generated output. The skill produces Markdown documents or shell scripts that you can edit, commit, or execute directly.\n\n## Output\n\nThe skill produces one or more of the following depending on the request:\n\n- **Meeting Briefing Document** (Markdown): For each meeting, includes the event title, time, participants, agenda items inferred from context, relevant recent commits or PRs, and suggested talking points.\n- **Standup Notes** (Markdown): A formatted summary covering what was done yesterday (from git log and calendar), what is planned today (from upcoming events), and any blockers identified from open issues or failing CI.\n- **Workflow Script** (Bash\u002FMarkdown): A repeatable workflow that can be triggered on a schedule, combining calendar checks with development tasks like running tests, updating dashboards, or posting summaries to Slack.\n\n## Examples\n\n### Example 1: Daily Meeting Prep\n\n**User:** \"I have a sprint planning at 10am with the backend team and a design review at 2pm. Prep briefings for both.\"\n\nThe skill will:\n1. Create a sprint planning briefing listing open sprint issues, velocity from the last sprint, and items ready for estimation.\n2. Create a design review briefing pulling recent UI\u002FUX changes from git history, linking to relevant Figma or mockup files found in the repo, and summarizing outstanding design-related issues.\n3. Output both as a single Markdown document with clear section headers.\n\n### Example 2: Standup Notes from Git Activity\n\n**User:** \"Generate standup notes for today based on yesterday's work.\"\n\nThe skill will:\n1. Run `git log --since=\"yesterday\" --oneline` to gather recent commits.\n2. Check for any open PRs with `gh pr list --author @me`.\n3. Identify any failing CI checks with `gh run list --limit 5`.\n4. Format the output as: \"Yesterday I... \u002F Today I plan to... \u002F Blockers: ...\"\n\n### Example 3: Weekly Recurring Workflow\n\n**User:** \"Create a Monday morning workflow that preps me for the week.\"\n\nThe skill will generate a script that:\n1. Reads the week's calendar events from an ICS file.\n2. Summarizes each day's meetings with participant counts and estimated time commitment.\n3. Pulls the current sprint board status.\n4. Outputs a weekly overview document to `docs\u002Fweekly-prep.md`.\n\n## Error Handling\n\n- **No calendar data provided:** Prompts the user to paste events, point to an ICS file, or describe their schedule.\n- **Unrecognized format:** Attempts best-effort parsing and asks the user to confirm the extracted events.\n- **Missing git context:** Skips repository-specific sections and notes which parts were omitted.\n- **Permission errors:** Suggests checking file permissions or GitHub CLI authentication status.\n",{"name":5,"tags":48,"author":52,"license":14,"version":53,"description":54,"allowed-tools":55,"compatible-with":56},[24,49,50,51,25],"automation","meetings","productivity","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Converts calendar events and schedules into Claude Code workflows, meeting prep\ndocuments, and standup notes. Use when the user mentions calendar events, meeting\nprep, standup generation, or scheduling workflows. Trigger with phrases like\n\"prep for my meetings\", \"generate standup notes\", \"create workflow from calendar\",\nor \"summarize today's schedule\".\n","Read, Write, Edit, Bash, Glob, Grep","claude-code, codex","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fskill-enhancers\u002Fcalendar-to-workflow\u002Fskills\u002Fcalendar-to-workflow",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add micsapp\u002Fmicstec-skills --skill calendar-to-workflow",{"tool":70,"command":71},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill calendar-to-workflow",{"tool":73,"command":74},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill calendar-to-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fskill-enhancers\u002Fcalendar-to-workflow\u002Fskills\u002Fcalendar-to-workflow\u002FSKILL.md",true,[],[79,114,140,161,181,204],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":93,"publishedAt":43},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[85,88],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":126,"publishedAt":43},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[120,121,124,125],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":122,"categoryName":123,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[127,128,42,129,95,130,37,131,132,133,134,135,103,104,110,136,137,111,138,139],"deployment","apiops deployment","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":43},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[146],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},[148,149,150,151,95,98,103,104,152,153,154,155,156,157,158,111,159,160,139,113],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":169,"publishedAt":43},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[167,168],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[170,151,171,103,155,172,95,127,173,174,175,176,104,177,111,178,179,180,112,113],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":43},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[188,189,190,42,191,192,39,193,103,194,195,196,32,197,198,199,200,201,202,203],"cli","jira","jira cli","init","tasks","issues","common","work","command","list","view","project","project work","token","line","sprints",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":43},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[206,211,212,213,214,215,216,153,217,218],"npm","js","calculate","node","math","user","compute","errors"]