[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EX5N619FEPQA1B02JTYJ6P":3,"skill-same:01M6EX5N619FEPQA1B02JTYJ6P":107},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6EX5N619FEPQA1B02JTYJ6P","para-skill",null,"PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks \"where does this note belong?\". Works with existing Obsidian skills (obsidian-markdown, obsidian-cli) — never replaces them.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"para skill","para","knowledge","processing","resources","classify","structure","route","never","knowledge management","projects","review","markdown","audit","inbox","run","cleanup","notes","obsidian","cli","2026-11-10 10:12:30",false,"---\nname: para-skill\ndescription: >\n  PARA method knowledge management for Obsidian vaults. Use this skill whenever\n  the user wants to organize notes using PARA (Projects, Areas, Resources, Archive),\n  classify a note into a PARA category, route a note to the right vault folder,\n  normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit\n  vault structure, or process new knowledge inputs into an existing PARA-based vault.\n  Also trigger when the user mentions inbox processing, vault cleanup, note classification,\n  PARA review, or asks \"where does this note belong?\". Works with existing Obsidian\n  skills (obsidian-markdown, obsidian-cli) — never replaces them.\n---\n\n# PARA Obsidian Skill\n\n## What this skill does\n\nThis skill provides PARA-method decision logic for Obsidian vaults. It decides **where** notes belong, **when** to archive, and **how** to keep the vault healthy — while leaving file creation, markdown formatting, and Obsidian syntax to the installed base skills.\n\nPARA is an organizational framework by Tiago Forte that structures information by **action relevance**, not topic:\n- **Projects** — concrete initiatives with a goal and an endpoint\n- **Areas** — ongoing responsibilities with no fixed end date\n- **Resources** — reference knowledge for potential future use\n- **Archive** — completed, paused, or inactive content\n\nRead `references\u002Fclassification-rules.md` for detailed classification heuristics.\n\n---\n\n## Vault Configuration\n\nDefault paths for this vault (override in conversation if different):\n\n```yaml\npaths:\n  inbox: \"0_Inbox\"          # created on demand if missing\n  projects: \"1_Projects\"\n  areas: \"2_Areas\"\n  resources: \"3_Resources\"\n  archive: \"4_Archives\"\n```\n\nDefault mode: **cautious** — suggest first, act only when confident or explicitly asked.\n\n---\n\n## Core Workflow\n\nFor every PARA-related task, follow this sequence:\n\n1. **Read** the note content, title, existing frontmatter, tags, and current file path\n2. **Collect signals** — look for project indicators (deadlines, tasks, goals), area indicators (ongoing, recurring), resource indicators (reference, no action pressure), archive indicators (done, cancelled, historical)\n3. **Check conventions** — respect existing `para_type` frontmatter; existing folder placement is a strong signal\n4. **Classify** with a confidence level: `high`, `medium`, or `low`\n5. **Plan frontmatter** additions — only add fields from the schema, never overwrite non-PARA fields\n6. **Propose routing** — suggest the target path\n7. **Assess risk** — only act directly when confidence is high AND the user has given explicit permission or the mode is `balanced`\u002F`aggressive`\n8. **Log changes** when writing anything\n\nWhen in doubt: set `needs_review: true`, place in Inbox, and explain why.\n\nSee `references\u002Fclassification-rules.md` for the full decision tree.\n\n---\n\n## Available Actions\n\n### `capture` — Process new content\nAccept raw text, meeting notes, ideas, or document descriptions. Classify them, propose or create a note in the right location, and set frontmatter.\n\n**Example trigger:** \"Capture this: Vorbereitung Workshop Führungsteam April\"\n**Output:** PARA classification + proposed path + frontmatter draft\n\n### `classify` — Classify an existing note\nRead a note and determine its PARA type. Return classification, confidence level, and reasoning.\n\n**Example trigger:** \"Welcher PARA-Typ ist diese Notiz?\" or \"Klassifiziere 2_Areas\u002FWeiterbildung\u002F...\"\n**Output:** `para_type`, `confidence`, explanation, suggested changes\n\n### `route` — Determine or apply target location\nCalculate the correct target folder for a note. In cautious mode: suggest only. With explicit permission: move the file.\n\n**Example trigger:** \"Wo gehört diese Notiz hin?\" or \"Route diese Notiz korrekt ein\"\n**Output:** Current path → suggested path, reasoning, conflict check\n\n### `normalize` — Fix frontmatter\nAdd missing PARA frontmatter fields to a note without touching non-PARA fields. Never remove existing fields.\n\n**Example trigger:** \"Normalisiere das Frontmatter dieser Notiz\" or \"Füge PARA-Metadaten hinzu\"\n**Output:** Updated frontmatter block (show diff before applying)\n\n### `review` — PARA hygiene report\nScan a folder or the whole vault for hygiene issues. See `references\u002Freview-playbook.md` for what to check.\n\n**Example trigger:** \"Mach einen PARA-Review\" or \"Zeig mir, was im Vault aufgeräumt werden sollte\"\n**Output:** Structured report (projects without next steps, stale areas, inbox backlog, archiving candidates)\n\n### `archive` — Archive a note defensively\nMove a note to the Archive folder with `archived: true`, `archive_date`, and updated `status`. Never delete. Preserve all wikilinks.\n\n**Example trigger:** \"Archiviere dieses Projekt\" or \"Das Projekt ist abgeschlossen\"\n**Output:** Confirmation of move + frontmatter changes (dry-run by default)\n\n### `audit` — Full vault consistency audit\nScan all notes for PARA inconsistencies: missing frontmatter, wrong folder placement, orphaned notes, stale reviews. Produces a prioritized action list.\n\n**Example trigger:** \"Mach einen vollständigen Vault-Audit\" or \"Was stimmt in meinem Vault nicht?\"\n**Output:** Audit report with actionable items\n\n### `suggest` — Recommendation without changes\nGive a PARA recommendation with full reasoning, but make no changes to any file.\n\n**Example trigger:** \"Was würdest Du mit dieser Notiz machen?\" or \"Vorschlag für diese Datei\"\n**Output:** Recommendation + reasoning (read-only)\n\n---\n\n## Safety Rules\n\nThese rules are non-negotiable regardless of mode:\n\n1. **No mass moves without explicit user authorization** — always ask first\n2. **No deletion** — archive means move, never delete\n3. **No overwriting non-PARA frontmatter fields** — only add\u002Fupdate defined PARA fields\n4. **Low confidence → needs_review** — never force a classification when unsure\n5. **Dry-run by default** — show what would happen before doing it\n6. **Preserve wikilinks** — never rename files in ways that break `[[links]]`\n7. **Log every structural change** — use the change log format below\n8. **No reclassification from a single weak signal** — require 2+ supporting indicators\n\n### Change Log Format\n\nWhen making structural changes, append to a `PARA-Changelog.md` in the vault root:\n\n```markdown\n## 2026-03-14\n- Classified `Meeting Notes Team Alpha` → project (confidence: medium)\n- Suggested move to `1_Projects\u002Fteam-alpha\u002F` (not yet applied, needs_review: true)\n- Normalized frontmatter in `2_Areas\u002FWeiterbildung\u002FKI-Kurs.md`\n```\n\n---\n\n## Frontmatter Schema\n\nRead `references\u002Ffrontmatter-schema.md` for the full field definitions.\n\nQuick reference — only write these fields:\n```yaml\npara_type: project        # project | area | resource | archive\nstatus: active            # active | on-hold | done | archived | reference | needs_review\nreview_date: 2026-03-21\nconfidence: high          # high | medium | low\nneeds_review: false\narchived: false\narchive_date:             # only when archiving\nsource: manual            # manual | meeting | import | daily-note | web\n```\n\nNever touch: titles, body content, existing tags not prefixed with `para\u002F`, wikilinks, non-PARA frontmatter fields.\n\n---\n\n## Cooperation with Other Skills\n\nThis skill handles: **classification logic, routing decisions, PARA frontmatter, review reports**\n\nLeave to obsidian-markdown \u002F obsidian-cli: **file creation, markdown syntax, wikilink formatting, template application, dataview queries**\n\nWhen creating a new note as part of `capture` or `route`, delegate file creation to the obsidian-markdown or obsidian-cli skill if available. Only use direct file writes as fallback.\n\nRead `references\u002Fcompatibility-notes.md` for conflict avoidance rules.\n\n---\n\n## Response Format\n\nAlways communicate:\n1. **What** you classified\u002Ffound (with `para_type` and `confidence`)\n2. **Why** — at least 2 supporting signals\n3. **What you propose to change** (as a clear list)\n4. **What you're uncertain about** (if anything)\n5. **What you'll do next** — or ask for permission before acting\n\nFor reviews and audits, use the structured report format in `references\u002Freview-playbook.md`.\n","# PARA Obsidian Skill\n\n## What this skill does\n\nThis skill provides PARA-method decision logic for Obsidian vaults. It decides **where** notes belong, **when** to archive, and **how** to keep the vault healthy — while leaving file creation, markdown formatting, and Obsidian syntax to the installed base skills.\n\nPARA is an organizational framework by Tiago Forte that structures information by **action relevance**, not topic:\n- **Projects** — concrete initiatives with a goal and an endpoint\n- **Areas** — ongoing responsibilities with no fixed end date\n- **Resources** — reference knowledge for potential future use\n- **Archive** — completed, paused, or inactive content\n\nRead `references\u002Fclassification-rules.md` for detailed classification heuristics.\n\n---\n\n## Vault Configuration\n\nDefault paths for this vault (override in conversation if different):\n\n```yaml\npaths:\n  inbox: \"0_Inbox\"          # created on demand if missing\n  projects: \"1_Projects\"\n  areas: \"2_Areas\"\n  resources: \"3_Resources\"\n  archive: \"4_Archives\"\n```\n\nDefault mode: **cautious** — suggest first, act only when confident or explicitly asked.\n\n---\n\n## Core Workflow\n\nFor every PARA-related task, follow this sequence:\n\n1. **Read** the note content, title, existing frontmatter, tags, and current file path\n2. **Collect signals** — look for project indicators (deadlines, tasks, goals), area indicators (ongoing, recurring), resource indicators (reference, no action pressure), archive indicators (done, cancelled, historical)\n3. **Check conventions** — respect existing `para_type` frontmatter; existing folder placement is a strong signal\n4. **Classify** with a confidence level: `high`, `medium`, or `low`\n5. **Plan frontmatter** additions — only add fields from the schema, never overwrite non-PARA fields\n6. **Propose routing** — suggest the target path\n7. **Assess risk** — only act directly when confidence is high AND the user has given explicit permission or the mode is `balanced`\u002F`aggressive`\n8. **Log changes** when writing anything\n\nWhen in doubt: set `needs_review: true`, place in Inbox, and explain why.\n\nSee `references\u002Fclassification-rules.md` for the full decision tree.\n\n---\n\n## Available Actions\n\n### `capture` — Process new content\nAccept raw text, meeting notes, ideas, or document descriptions. Classify them, propose or create a note in the right location, and set frontmatter.\n\n**Example trigger:** \"Capture this: Vorbereitung Workshop Führungsteam April\"\n**Output:** PARA classification + proposed path + frontmatter draft\n\n### `classify` — Classify an existing note\nRead a note and determine its PARA type. Return classification, confidence level, and reasoning.\n\n**Example trigger:** \"Welcher PARA-Typ ist diese Notiz?\" or \"Klassifiziere 2_Areas\u002FWeiterbildung\u002F...\"\n**Output:** `para_type`, `confidence`, explanation, suggested changes\n\n### `route` — Determine or apply target location\nCalculate the correct target folder for a note. In cautious mode: suggest only. With explicit permission: move the file.\n\n**Example trigger:** \"Wo gehört diese Notiz hin?\" or \"Route diese Notiz korrekt ein\"\n**Output:** Current path → suggested path, reasoning, conflict check\n\n### `normalize` — Fix frontmatter\nAdd missing PARA frontmatter fields to a note without touching non-PARA fields. Never remove existing fields.\n\n**Example trigger:** \"Normalisiere das Frontmatter dieser Notiz\" or \"Füge PARA-Metadaten hinzu\"\n**Output:** Updated frontmatter block (show diff before applying)\n\n### `review` — PARA hygiene report\nScan a folder or the whole vault for hygiene issues. See `references\u002Freview-playbook.md` for what to check.\n\n**Example trigger:** \"Mach einen PARA-Review\" or \"Zeig mir, was im Vault aufgeräumt werden sollte\"\n**Output:** Structured report (projects without next steps, stale areas, inbox backlog, archiving candidates)\n\n### `archive` — Archive a note defensively\nMove a note to the Archive folder with `archived: true`, `archive_date`, and updated `status`. Never delete. Preserve all wikilinks.\n\n**Example trigger:** \"Archiviere dieses Projekt\" or \"Das Projekt ist abgeschlossen\"\n**Output:** Confirmation of move + frontmatter changes (dry-run by default)\n\n### `audit` — Full vault consistency audit\nScan all notes for PARA inconsistencies: missing frontmatter, wrong folder placement, orphaned notes, stale reviews. Produces a prioritized action list.\n\n**Example trigger:** \"Mach einen vollständigen Vault-Audit\" or \"Was stimmt in meinem Vault nicht?\"\n**Output:** Audit report with actionable items\n\n### `suggest` — Recommendation without changes\nGive a PARA recommendation with full reasoning, but make no changes to any file.\n\n**Example trigger:** \"Was würdest Du mit dieser Notiz machen?\" or \"Vorschlag für diese Datei\"\n**Output:** Recommendation + reasoning (read-only)\n\n---\n\n## Safety Rules\n\nThese rules are non-negotiable regardless of mode:\n\n1. **No mass moves without explicit user authorization** — always ask first\n2. **No deletion** — archive means move, never delete\n3. **No overwriting non-PARA frontmatter fields** — only add\u002Fupdate defined PARA fields\n4. **Low confidence → needs_review** — never force a classification when unsure\n5. **Dry-run by default** — show what would happen before doing it\n6. **Preserve wikilinks** — never rename files in ways that break `[[links]]`\n7. **Log every structural change** — use the change log format below\n8. **No reclassification from a single weak signal** — require 2+ supporting indicators\n\n### Change Log Format\n\nWhen making structural changes, append to a `PARA-Changelog.md` in the vault root:\n\n```markdown\n## 2026-03-14\n- Classified `Meeting Notes Team Alpha` → project (confidence: medium)\n- Suggested move to `1_Projects\u002Fteam-alpha\u002F` (not yet applied, needs_review: true)\n- Normalized frontmatter in `2_Areas\u002FWeiterbildung\u002FKI-Kurs.md`\n```\n\n---\n\n## Frontmatter Schema\n\nRead `references\u002Ffrontmatter-schema.md` for the full field definitions.\n\nQuick reference — only write these fields:\n```yaml\npara_type: project        # project | area | resource | archive\nstatus: active            # active | on-hold | done | archived | reference | needs_review\nreview_date: 2026-03-21\nconfidence: high          # high | medium | low\nneeds_review: false\narchived: false\narchive_date:             # only when archiving\nsource: manual            # manual | meeting | import | daily-note | web\n```\n\nNever touch: titles, body content, existing tags not prefixed with `para\u002F`, wikilinks, non-PARA frontmatter fields.\n\n---\n\n## Cooperation with Other Skills\n\nThis skill handles: **classification logic, routing decisions, PARA frontmatter, review reports**\n\nLeave to obsidian-markdown \u002F obsidian-cli: **file creation, markdown syntax, wikilink formatting, template application, dataview queries**\n\nWhen creating a new note as part of `capture` or `route`, delegate file creation to the obsidian-markdown or obsidian-cli skill if available. Only use direct file writes as fallback.\n\nRead `references\u002Fcompatibility-notes.md` for conflict avoidance rules.\n\n---\n\n## Response Format\n\nAlways communicate:\n1. **What** you classified\u002Ffound (with `para_type` and `confidence`)\n2. **Why** — at least 2 supporting signals\n3. **What you propose to change** (as a clear list)\n4. **What you're uncertain about** (if anything)\n5. **What you'll do next** — or ask for permission before acting\n\nFor reviews and audits, use the structured report format in `references\u002Freview-playbook.md`.\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill para-skill",{"tool":64,"command":65},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill para-skill",{"tool":67,"command":68},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill para-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002FSKILL.md",true,[72,78,83,87,91,95,99,103],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"CHANGELOG.md","REFERENCE","参考文档",1347,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002FCHANGELOG.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"LICENSE","许可证",1069,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002FLICENSE",{"path":84,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":85,"sourceHtmlUrl":86},"README.md",5759,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002FREADME.md",{"path":88,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fclassification-rules.md",4997,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002Freferences\u002Fclassification-rules.md",{"path":92,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fcompatibility-notes.md",3427,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002Freferences\u002Fcompatibility-notes.md",{"path":96,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Ffrontmatter-schema.md",2746,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002Freferences\u002Ffrontmatter-schema.md",{"path":100,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Freview-playbook.md",3896,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002Freferences\u002Freview-playbook.md",{"path":104,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":105,"sourceHtmlUrl":106},"skill-report.json",38421,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fscifishelf\u002Fpara-skill\u002Fskill-report.json",[108,118,128,137,143,150],{"skillNo":109,"name":110,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":44},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[113],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[115,116,117],"model","model hierarchy","model hierarchy skill",{"skillNo":119,"name":120,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":44},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,127],"MCP","zoom","zoom mcp",{"skillNo":129,"name":130,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":44},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[134,135,136,126],"sdk","zoom apps sdk","apps",{"skillNo":138,"name":139,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":44},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[139],{"skillNo":144,"name":145,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":44},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[145],{"skillNo":151,"name":152,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":44},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[152]]