[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76GTYRX8AB0MJ4K08PQ4XT7":3,"skill-same:01M76GTYRX8AB0MJ4K08PQ4XT7":55},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M76GTYRX8AB0MJ4K08PQ4XT7","meeting-notes",null,"Transform raw meeting notes, transcripts, or recordings into structured, actionable summaries","meghal86\u002Fstacksignal","meghal86","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F37388715?v=4","01M6CS2EW8SK89GH52R2ZEN8QQ","01M728J5CGY456EETEFG6HJBTM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmeeting-notes\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: meeting-notes\ndescription: Transform raw meeting notes, transcripts, or recordings into structured, actionable summaries\nversion: 1.0.0\nauthor: Claude Office Skills Contributors\nlicense: MIT\ntags: [productivity, meetings, documentation]\n---\n\n# Meeting Notes\n\n## Overview\n\nThis skill transforms raw meeting notes, transcripts, or audio summaries into clear, structured documentation with action items, decisions, and key takeaways.\n\n**Use Cases:**\n- Converting messy handwritten notes to clean summaries\n- Processing meeting transcripts\n- Extracting action items and owners\n- Creating meeting minutes for distribution\n- Summarizing long discussions into key points\n\n## How to Use\n\n1. Paste your raw meeting notes, transcript, or description\n2. Tell me the meeting type (standup, project review, client call, etc.)\n3. Specify any required format or template\n4. I'll create structured notes with action items\n\n**Example prompts:**\n- \"Organize these meeting notes and extract action items\"\n- \"Create formal meeting minutes from this transcript\"\n- \"Summarize the key decisions from our project review\"\n- \"Turn this brainstorm session into a structured document\"\n\n## Meeting Note Templates\n\n### Standard Meeting Summary\n\n```markdown\n# Meeting Summary\n\n**Meeting:** [Title]\n**Date:** [Date]\n**Attendees:** [Names]\n**Duration:** [Time]\n\n## Purpose\n[One sentence describing meeting objective]\n\n## Key Discussion Points\n1. [Topic 1]\n   - [Key point]\n   - [Key point]\n\n2. [Topic 2]\n   - [Key point]\n   - [Key point]\n\n## Decisions Made\n- [ ] [Decision 1]\n- [ ] [Decision 2]\n\n## Action Items\n| Action | Owner | Due Date | Status |\n|--------|-------|----------|--------|\n| [Task] | [Name] | [Date] | Pending |\n\n## Next Steps\n- [Next meeting\u002Fmilestone]\n\n## Notes\n[Any additional context or parking lot items]\n```\n\n### Quick Standup Notes\n\n```markdown\n# Daily Standup - [Date]\n\n## [Team Member 1]\n**Yesterday:** [Completed tasks]\n**Today:** [Planned tasks]\n**Blockers:** [Issues, if any]\n\n## [Team Member 2]\n...\n\n## Team Blockers\n- [Blocker requiring escalation]\n\n## Announcements\n- [Team-wide updates]\n```\n\n### Client Meeting Notes\n\n```markdown\n# Client Meeting Notes\n\n**Client:** [Company Name]\n**Date:** [Date]\n**Our Team:** [Names]\n**Client Team:** [Names]\n\n## Meeting Objective\n[Why we met]\n\n## Client Feedback\u002FRequests\n1. [Feedback point]\n2. [Request]\n\n## Our Commitments\n- [What we promised to deliver]\n- [Timeline]\n\n## Client Commitments\n- [What they will provide]\n- [Timeline]\n\n## Follow-up Required\n| Item | Owner | Due |\n|------|-------|-----|\n| [Task] | [Name] | [Date] |\n\n## Next Meeting\n[Date\u002FTime\u002FAgenda preview]\n```\n\n### Project Review Notes\n\n```markdown\n# Project Review: [Project Name]\n\n**Date:** [Date]\n**Phase:** [Current phase]\n**Status:** 🟢 On Track \u002F 🟡 At Risk \u002F 🔴 Off Track\n\n## Progress Update\n- **Completed:** [Milestones achieved]\n- **In Progress:** [Current work]\n- **Upcoming:** [Next milestones]\n\n## Metrics\n| Metric | Target | Actual | Status |\n|--------|--------|--------|--------|\n| [KPI] | [Target] | [Actual] | ✅\u002F⚠️\u002F❌ |\n\n## Risks & Issues\n| Risk\u002FIssue | Impact | Mitigation | Owner |\n|------------|--------|------------|-------|\n| [Description] | High\u002FMed\u002FLow | [Plan] | [Name] |\n\n## Decisions Needed\n- [Decision requiring escalation]\n\n## Action Items\n- [ ] [Task] - @[Owner] - Due: [Date]\n```\n\n## Processing Guidelines\n\n### Extracting Action Items\n\nLook for phrases indicating tasks:\n- \"We need to...\" \u002F \"Someone should...\"\n- \"Can you...\" \u002F \"Will you...\"\n- \"Let's...\" \u002F \"Action:\"\n- Names + verbs (e.g., \"John will prepare...\")\n- Deadlines mentioned with tasks\n\n### Identifying Decisions\n\nLook for:\n- \"We've decided...\" \u002F \"The decision is...\"\n- \"Going forward, we will...\"\n- \"Agreed:\" \u002F \"Confirmed:\"\n- Consensus language (\"everyone agreed...\")\n\n### Determining Owners\n\n- Explicitly named: \"Sarah will handle...\"\n- Role-based: \"The design team will...\"\n- Default to meeting organizer if unclear\n- Flag unassigned items for follow-up\n\n## Output Format\n\n```markdown\n## Meeting Summary: [Title]\n\n📅 **Date:** [Date]\n👥 **Attendees:** [List]\n\n### 📋 Summary\n[2-3 sentence overview]\n\n### 💡 Key Points\n1. [Point 1]\n2. [Point 2]\n3. [Point 3]\n\n### ✅ Decisions\n- [Decision 1]\n- [Decision 2]\n\n### 📌 Action Items\n| # | Action | Owner | Due | Priority |\n|---|--------|-------|-----|----------|\n| 1 | [Task] | [Name] | [Date] | High\u002FMed\u002FLow |\n\n### 🔜 Next Steps\n- [Next meeting or milestone]\n\n### 📝 Parking Lot\n- [Items to address later]\n```\n\n## Customization Options\n\nTell me your preferences:\n- **Format:** Bullet points, table, prose, or formal minutes\n- **Detail level:** Executive summary, standard, or detailed\n- **Focus:** Action items only, decisions only, or comprehensive\n- **Style:** Casual team notes or formal documentation\n\n## Limitations\n\n- Cannot attend or record meetings\n- Accuracy depends on quality of input notes\n- May need clarification on ambiguous pronouns or acronyms\n- Cannot verify commitments or deadlines - review before distributing\n\n## Examples\n\n### Example: Raw Notes to Structured Summary\n\n**Input:**\n```\nproduct meeting 3\u002F15\ntalked about launch timeline, sarah thinks we need 2 more weeks\njohn mentioned the bug in checkout - high priority\ndecided to push launch to april 1\nneed to update stakeholders\nmaria will fix the checkout bug by friday\nalso discussed new feature requests from customers - will prioritize next sprint\njohn to send customer feedback summary\n```\n\n**Output:**\n\n## Meeting Summary: Product Launch Review\n\n📅 **Date:** March 15, 2024\n👥 **Attendees:** Sarah, John, Maria\n\n### 📋 Summary\nReviewed launch timeline and decided to postpone launch by 2 weeks to April 1 due to critical checkout bug. Discussed customer feature requests for future prioritization.\n\n### 💡 Key Points\n1. Original launch timeline insufficient - need 2 more weeks\n2. Critical checkout bug discovered - must fix before launch\n3. Customer feature requests collected for next sprint prioritization\n\n### ✅ Decisions\n- Launch date moved from mid-March to **April 1**\n- Checkout bug is **highest priority**\n- Feature requests to be prioritized in next sprint planning\n\n### 📌 Action Items\n| # | Action | Owner | Due | Priority |\n|---|--------|-------|-----|----------|\n| 1 | Fix checkout bug | Maria | Friday (3\u002F17) | 🔴 High |\n| 2 | Update stakeholders on new launch date | [Unassigned] | ASAP | 🔴 High |\n| 3 | Send customer feedback summary | John | [TBD] | 🟡 Medium |\n\n### 🔜 Next Steps\n- Follow-up on bug fix progress\n- Stakeholder communication about timeline change\n- Sprint planning to prioritize customer requests\n","# Meeting Notes\n\n## Overview\n\nThis skill transforms raw meeting notes, transcripts, or audio summaries into clear, structured documentation with action items, decisions, and key takeaways.\n\n**Use Cases:**\n- Converting messy handwritten notes to clean summaries\n- Processing meeting transcripts\n- Extracting action items and owners\n- Creating meeting minutes for distribution\n- Summarizing long discussions into key points\n\n## How to Use\n\n1. Paste your raw meeting notes, transcript, or description\n2. Tell me the meeting type (standup, project review, client call, etc.)\n3. Specify any required format or template\n4. I'll create structured notes with action items\n\n**Example prompts:**\n- \"Organize these meeting notes and extract action items\"\n- \"Create formal meeting minutes from this transcript\"\n- \"Summarize the key decisions from our project review\"\n- \"Turn this brainstorm session into a structured document\"\n\n## Meeting Note Templates\n\n### Standard Meeting Summary\n\n```markdown\n# Meeting Summary\n\n**Meeting:** [Title]\n**Date:** [Date]\n**Attendees:** [Names]\n**Duration:** [Time]\n\n## Purpose\n[One sentence describing meeting objective]\n\n## Key Discussion Points\n1. [Topic 1]\n   - [Key point]\n   - [Key point]\n\n2. [Topic 2]\n   - [Key point]\n   - [Key point]\n\n## Decisions Made\n- [ ] [Decision 1]\n- [ ] [Decision 2]\n\n## Action Items\n| Action | Owner | Due Date | Status |\n|--------|-------|----------|--------|\n| [Task] | [Name] | [Date] | Pending |\n\n## Next Steps\n- [Next meeting\u002Fmilestone]\n\n## Notes\n[Any additional context or parking lot items]\n```\n\n### Quick Standup Notes\n\n```markdown\n# Daily Standup - [Date]\n\n## [Team Member 1]\n**Yesterday:** [Completed tasks]\n**Today:** [Planned tasks]\n**Blockers:** [Issues, if any]\n\n## [Team Member 2]\n...\n\n## Team Blockers\n- [Blocker requiring escalation]\n\n## Announcements\n- [Team-wide updates]\n```\n\n### Client Meeting Notes\n\n```markdown\n# Client Meeting Notes\n\n**Client:** [Company Name]\n**Date:** [Date]\n**Our Team:** [Names]\n**Client Team:** [Names]\n\n## Meeting Objective\n[Why we met]\n\n## Client Feedback\u002FRequests\n1. [Feedback point]\n2. [Request]\n\n## Our Commitments\n- [What we promised to deliver]\n- [Timeline]\n\n## Client Commitments\n- [What they will provide]\n- [Timeline]\n\n## Follow-up Required\n| Item | Owner | Due |\n|------|-------|-----|\n| [Task] | [Name] | [Date] |\n\n## Next Meeting\n[Date\u002FTime\u002FAgenda preview]\n```\n\n### Project Review Notes\n\n```markdown\n# Project Review: [Project Name]\n\n**Date:** [Date]\n**Phase:** [Current phase]\n**Status:** 🟢 On Track \u002F 🟡 At Risk \u002F 🔴 Off Track\n\n## Progress Update\n- **Completed:** [Milestones achieved]\n- **In Progress:** [Current work]\n- **Upcoming:** [Next milestones]\n\n## Metrics\n| Metric | Target | Actual | Status |\n|--------|--------|--------|--------|\n| [KPI] | [Target] | [Actual] | ✅\u002F⚠️\u002F❌ |\n\n## Risks & Issues\n| Risk\u002FIssue | Impact | Mitigation | Owner |\n|------------|--------|------------|-------|\n| [Description] | High\u002FMed\u002FLow | [Plan] | [Name] |\n\n## Decisions Needed\n- [Decision requiring escalation]\n\n## Action Items\n- [ ] [Task] - @[Owner] - Due: [Date]\n```\n\n## Processing Guidelines\n\n### Extracting Action Items\n\nLook for phrases indicating tasks:\n- \"We need to...\" \u002F \"Someone should...\"\n- \"Can you...\" \u002F \"Will you...\"\n- \"Let's...\" \u002F \"Action:\"\n- Names + verbs (e.g., \"John will prepare...\")\n- Deadlines mentioned with tasks\n\n### Identifying Decisions\n\nLook for:\n- \"We've decided...\" \u002F \"The decision is...\"\n- \"Going forward, we will...\"\n- \"Agreed:\" \u002F \"Confirmed:\"\n- Consensus language (\"everyone agreed...\")\n\n### Determining Owners\n\n- Explicitly named: \"Sarah will handle...\"\n- Role-based: \"The design team will...\"\n- Default to meeting organizer if unclear\n- Flag unassigned items for follow-up\n\n## Output Format\n\n```markdown\n## Meeting Summary: [Title]\n\n📅 **Date:** [Date]\n👥 **Attendees:** [List]\n\n### 📋 Summary\n[2-3 sentence overview]\n\n### 💡 Key Points\n1. [Point 1]\n2. [Point 2]\n3. [Point 3]\n\n### ✅ Decisions\n- [Decision 1]\n- [Decision 2]\n\n### 📌 Action Items\n| # | Action | Owner | Due | Priority |\n|---|--------|-------|-----|----------|\n| 1 | [Task] | [Name] | [Date] | High\u002FMed\u002FLow |\n\n### 🔜 Next Steps\n- [Next meeting or milestone]\n\n### 📝 Parking Lot\n- [Items to address later]\n```\n\n## Customization Options\n\nTell me your preferences:\n- **Format:** Bullet points, table, prose, or formal minutes\n- **Detail level:** Executive summary, standard, or detailed\n- **Focus:** Action items only, decisions only, or comprehensive\n- **Style:** Casual team notes or formal documentation\n\n## Limitations\n\n- Cannot attend or record meetings\n- Accuracy depends on quality of input notes\n- May need clarification on ambiguous pronouns or acronyms\n- Cannot verify commitments or deadlines - review before distributing\n\n## Examples\n\n### Example: Raw Notes to Structured Summary\n\n**Input:**\n```\nproduct meeting 3\u002F15\ntalked about launch timeline, sarah thinks we need 2 more weeks\njohn mentioned the bug in checkout - high priority\ndecided to push launch to april 1\nneed to update stakeholders\nmaria will fix the checkout bug by friday\nalso discussed new feature requests from customers - will prioritize next sprint\njohn to send customer feedback summary\n```\n\n**Output:**\n\n## Meeting Summary: Product Launch Review\n\n📅 **Date:** March 15, 2024\n👥 **Attendees:** Sarah, John, Maria\n\n### 📋 Summary\nReviewed launch timeline and decided to postpone launch by 2 weeks to April 1 due to critical checkout bug. Discussed customer feature requests for future prioritization.\n\n### 💡 Key Points\n1. Original launch timeline insufficient - need 2 more weeks\n2. Critical checkout bug discovered - must fix before launch\n3. Customer feature requests collected for next sprint prioritization\n\n### ✅ Decisions\n- Launch date moved from mid-March to **April 1**\n- Checkout bug is **highest priority**\n- Feature requests to be prioritized in next sprint planning\n\n### 📌 Action Items\n| # | Action | Owner | Due | Priority |\n|---|--------|-------|-----|----------|\n| 1 | Fix checkout bug | Maria | Friday (3\u002F17) | 🔴 High |\n| 2 | Update stakeholders on new launch date | [Unassigned] | ASAP | 🔴 High |\n| 3 | Send customer feedback summary | John | [TBD] | 🟡 Medium |\n\n### 🔜 Next Steps\n- Follow-up on bug fix progress\n- Stakeholder communication about timeline change\n- Sprint planning to prioritize customer requests\n",{"name":5,"tags":23,"author":27,"license":14,"version":28,"description":7},[24,25,26],"productivity","meetings","documentation","Claude Office Skills Contributors","1.0.0","main","54afe4b75ed2eb8f0feabb2f5b57dfa4bcbb3c44",".agents\u002Fskills\u002Fmeeting-notes","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal","https:\u002F\u002Fgithub.com\u002Fmeghal86","2026-05-17 14:11:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add meghal86\u002Fstacksignal --skill meeting-notes",{"tool":41,"command":42},"bunx","bunx skills add meghal86\u002Fstacksignal --skill meeting-notes",{"tool":44,"command":45},"pnpm","pnpm dlx skills add meghal86\u002Fstacksignal --skill meeting-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmeeting-notes\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"_meta.json","REFERENCE","参考文档",286,"https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmeeting-notes\u002F_meta.json",[56,65,73,81,89,96],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":64},"01M78XH0FRP65NYEDHF2BT7NB1","zvukogram","Text-to-Speech via Zvukogram API with SSML support. Use when you need to generate speech from text, create podcasts, voice notifications, or work with audio. Supports speed control, stress marks, English word transcription, and audio fragment merging.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzvukogram\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzvukogram\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":64},"01M78XEND5ASXYB6MN8AQQGJAF","zohomail","Zoho Mail API integration with managed OAuth. Send, receive, and manage emails, folders, and labels.\nUse this skill when users want to send emails, read messages, manage folders, or work with email labels in Zoho Mail.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzohomail\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzohomail\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":64},"01M78XEBBV3C6DRZFAJXP6RDKS","zoho-recruit","Zoho Recruit API integration with managed OAuth. Manage candidates, job openings, interviews, and recruitment workflows.\nUse this skill when users want to read, create, update, or search recruitment data like candidates, job openings, interviews, and applications in Zoho Recruit.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-recruit\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-recruit\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":64},"01M78XE5CQG75DZWYSKGXFR99T","zoho-people","Zoho People API integration with managed OAuth. Manage employees, departments, designations, attendance, and leave.\nUse this skill when users want to read, create, update, or query HR data like employees, departments, designations, and forms in Zoho People.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-people\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-people\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":64},"01M78XDZKMZAJYFJJFT7MR5ZN2","zoho-mail","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-mail\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-mail\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":64},"01M78XDST8JK0WVDA1F3VPNWXD","zoho-inventory","Zoho Inventory API integration with managed OAuth. Manage items, sales orders, invoices, purchase orders, bills, contacts, and shipments.\nUse this skill when users want to read, create, update, or delete inventory items, sales orders, invoices, purchase orders, bills, or other inventory records in Zoho Inventory.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-inventory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-inventory\u002FSKILL.md",[],[]]