[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ENF6D79NXTZ9955TATHX3C":3,"skill-same:01M6ENF6D79NXTZ9955TATHX3C":75},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6ENF6D79NXTZ9955TATHX3C","git-workflow",null,"Git worktree workflow, conventional commits, commit trailers, and PR guidelines. Activated during git operations and commits.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fcain96\u002Fgit-workflow\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],"workflow","git workflow","git","commit","pr","guidelines","worktree","commits","Bash","git worktree","read","operations","conventional commits","pr guidelines","git operations","2026-11-10 10:12:30",false,"---\nname: git-workflow\ndescription: Git worktree workflow, conventional commits, commit trailers, and PR guidelines. Activated during git operations and commits.\nallowed-tools: ['Bash', 'Read']\n---\n\n# Git Workflow Expert\n\nThis skill provides guidance on Git worktree workflow, commit standards, and PR best practices.\n\n## ? Git Worktree Workflow\n\n### Why Git Worktree?\n\nGit worktree allows working on multiple branches simultaneously without stashing or switching contexts. Each worktree is an independent working directory with its own branch.\n\n**Benefits**:\n- No context switching between branches\n- No stashing required\n- Parallel development on different features\n- Independent builds and tests per branch\n\n### Setting Up Worktrees\n\n```bash\n# Create worktree for feature development\ngit worktree add ..\u002Fproject-feature-auth feature\u002Fuser-authentication\n\n# Create worktree for bug fixes\ngit worktree add ..\u002Fproject-bugfix-api hotfix\u002Fapi-validation\n\n# Create worktree for experiments\ngit worktree add ..\u002Fproject-experiment-new-ui experiment\u002Freact-19-upgrade\n```\n\n### Worktree Naming Convention\n\n```\n..\u002Fproject-\u003Ctype>-\u003Cdescription>\n```\n\n**Types**:\n- `feature` - New feature development\n- `bugfix` - Bug fixes\n- `hotfix` - Urgent production fixes\n- `experiment` - Experimental changes\n- `refactor` - Code refactoring\n\n**Examples**:\n- `..\u002Fmyapp-feature-user-auth`\n- `..\u002Fmyapp-bugfix-login-error`\n- `..\u002Fmyapp-hotfix-security-patch`\n\n### Managing Worktrees\n\n```bash\n# List all worktrees\ngit worktree list\n\n# Show details in long format\ngit worktree list --porcelain\n\n# Remove worktree after merging\ngit worktree remove ..\u002Fproject-feature-auth\n\n# Remove worktree (force if dirty)\ngit worktree remove --force ..\u002Fproject-experiment\n\n# Prune stale worktree information\ngit worktree prune\n```\n\n### Worktree Best Practices\n\n1. **Clean up after merging** - Remove worktrees after feature completion\n2. **Use descriptive names** - Follow naming convention\n3. **Keep main worktree clean** - Use for stable work only\n4. **Regular pruning** - Run `git worktree prune` periodically\n\n## ? Commit Standards\n\n### Conventional Commits\n\nFollow the [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) specification:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n[optional body]\n\n[optional footer]\n```\n\n### Commit Types\n\n```bash\n# New feature\ngit commit -m \"feat(auth): add JWT token refresh mechanism\"\n\n# Bug fix\ngit commit -m \"fix(api): handle null response appropriately\"\n\n# Documentation\ngit commit -m \"docs(readme): update installation instructions\"\n\n# Performance improvement\ngit commit -m \"perf(db): optimize query performance\"\n\n# Code refactoring\ngit commit -m \"refactor(core): extract validation logic\"\n\n# Testing\ngit commit -m \"test(auth): add unit tests for login flow\"\n\n# Build\u002Ftooling\ngit commit -m \"build(deps): upgrade react to v18\"\n\n# CI\u002FCD\ngit commit -m \"ci(github): add automated deployment workflow\"\n\n# Chores\ngit commit -m \"chore(deps): update development dependencies\"\n\n# Style changes (formatting, etc.)\ngit commit -m \"style(components): format with prettier\"\n```\n\n### Commit Type Reference\n\n| Type | Description | Example |\n|------|-------------|---------|\n| `feat` | New feature | Adding user authentication |\n| `fix` | Bug fix | Fixing null pointer error |\n| `docs` | Documentation only | Update README |\n| `style` | Formatting changes | Code formatting, no logic change |\n| `refactor` | Code refactoring | Restructure without behavior change |\n| `perf` | Performance improvement | Optimize algorithm |\n| `test` | Adding\u002Fupdating tests | Add unit tests |\n| `build` | Build system changes | Update webpack config |\n| `ci` | CI\u002FCD changes | Update GitHub Actions |\n| `chore` | Maintenance tasks | Update dependencies |\n| `revert` | Revert previous commit | Revert \"feat: add feature\" |\n\n### Commit Message Guidelines\n\n**Subject line**:\n- Use imperative mood (\"add\" not \"added\" or \"adds\")\n- Don't capitalize first letter\n- No period at the end\n- Maximum 50 characters\n\n**Body**:\n- Wrap at 72 characters\n- Explain what and why, not how\n- Use bullet points for multiple changes\n\n**Example**:\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nfeat(api): add user profile endpoint\n\n- Add GET \u002Fapi\u002Fusers\u002F:id endpoint\n- Include avatar URL in response\n- Add rate limiting (100 req\u002Fmin)\n\nThis allows frontend to fetch user details\nwithout additional API calls.\n\nCloses #123\nEOF\n)\"\n```\n\n### Commit Trailers\n\nAdd metadata to commits using trailers:\n\n```bash\n# Reference GitHub issue\ngit commit --trailer \"Github-Issue: #123\"\n\n# Credit bug reporter\ngit commit --trailer \"Reported-by: John Doe \u003Cjohn@example.com>\"\n\n# Reference related commits\ngit commit --trailer \"See-also: abc123\"\n\n# Co-author\ngit commit --trailer \"Co-authored-by: Jane Smith \u003Cjane@example.com>\"\n```\n\n**Example with multiple trailers**:\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nfix(auth): resolve token expiration issue\n\nFixed bug where expired tokens weren't properly\nrefreshed, causing users to be logged out unexpectedly.\n\nGithub-Issue: #456\nReported-by: John Doe \u003Cjohn@example.com>\nReviewed-by: Jane Smith \u003Cjane@example.com>\nEOF\n)\"\n```\n\n## ? Pull Request Guidelines\n\n### PR Title\n\nFollow the same format as commit messages:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n```\n\n**Examples**:\n- `feat(auth): add OAuth2 authentication`\n- `fix(api): resolve race condition in data sync`\n- `docs(contributing): update contributor guidelines`\n\n### PR Description Template\n\n```markdown\n## Summary\nBrief description of changes (1-3 sentences)\n\n## Changes\n- Bullet point list of main changes\n- Focus on what and why, not implementation details\n- Keep it high-level\n\n## Test Plan\n- [ ] Unit tests pass\n- [ ] Integration tests pass\n- [ ] Manual testing performed\n- [ ] Edge cases covered\n\n## Breaking Changes\nList any breaking changes (if applicable)\n\n## Related Issues\nCloses #123\nRelated to #456\n\n## Screenshots\u002FVideos\n(if applicable)\n```\n\n### PR Best Practices\n\n1. **Keep PRs small** - Easier to review, faster to merge\n2. **One feature per PR** - Don't mix unrelated changes\n3. **Update documentation** - Keep docs in sync with code\n4. **Add tests** - Don't merge without test coverage\n5. **Respond to reviews** - Address feedback promptly\n6. **Squash commits** - Clean up commit history before merge\n7. **Delete branch** - Clean up after merge\n\n### PR Review Checklist\n\n**Before requesting review**:\n- [ ] All tests pass\n- [ ] Code is formatted (linter passes)\n- [ ] Documentation updated\n- [ ] No console.log or debug code\n- [ ] Type safety verified (TypeScript)\n- [ ] Breaking changes documented\n\n**For reviewers**:\n- [ ] Code follows project conventions\n- [ ] Logic is clear and maintainable\n- [ ] Edge cases are handled\n- [ ] Tests are adequate\n- [ ] No security vulnerabilities\n- [ ] Performance considerations addressed\n\n## ? Git Workflow Checklist\n\nDaily workflow checklist:\n\n- [ ] Pull latest changes: `git pull`\n- [ ] Create feature branch or worktree\n- [ ] Make atomic commits with conventional format\n- [ ] Write meaningful commit messages\n- [ ] Push regularly: `git push`\n- [ ] Create PR with proper description\n- [ ] Address review feedback\n- [ ] Squash commits if needed\n- [ ] Merge and delete branch\u002Fworktree\n\n## ? Advanced Git Tips\n\n### Interactive Rebase\n\n```bash\n# Clean up last 3 commits\ngit rebase -i HEAD~3\n\n# Rebase onto main\ngit rebase -i main\n```\n\n### Cherry-pick Commits\n\n```bash\n# Apply specific commit to current branch\ngit cherry-pick abc123\n\n# Cherry-pick without committing\ngit cherry-pick --no-commit abc123\n```\n\n### Stash Management\n\n```bash\n# Stash with message\ngit stash push -m \"WIP: feature in progress\"\n\n# List stashes\ngit stash list\n\n# Apply and drop stash\ngit stash pop\n\n# Apply specific stash\ngit stash apply stash@{0}\n```\n\n### Bisect for Bug Hunting\n\n```bash\n# Start bisect\ngit bisect start\n\n# Mark current as bad\ngit bisect bad\n\n# Mark known good commit\ngit bisect good abc123\n\n# Let git find the culprit\n# Test each commit and mark good\u002Fbad\ngit bisect good  # or bad\n\n# End bisect\ngit bisect reset\n```\n\n## ? Common Mistakes to Avoid\n\n❌ **Don't**:\n- Commit directly to main\u002Fmaster\n- Use vague commit messages (\"fix bug\", \"update\")\n- Mix unrelated changes in one commit\n- Forget to pull before pushing\n- Leave WIP commits in PR\n- Skip commit message body for complex changes\n\n✅ **Do**:\n- Use feature branches or worktrees\n- Write descriptive conventional commits\n- Make atomic commits (one logical change)\n- Pull regularly and before pushing\n- Squash\u002Freword commits before merging\n- Provide context in commit body\n","# Git Workflow Expert\n\nThis skill provides guidance on Git worktree workflow, commit standards, and PR best practices.\n\n## ? Git Worktree Workflow\n\n### Why Git Worktree?\n\nGit worktree allows working on multiple branches simultaneously without stashing or switching contexts. Each worktree is an independent working directory with its own branch.\n\n**Benefits**:\n- No context switching between branches\n- No stashing required\n- Parallel development on different features\n- Independent builds and tests per branch\n\n### Setting Up Worktrees\n\n```bash\n# Create worktree for feature development\ngit worktree add ..\u002Fproject-feature-auth feature\u002Fuser-authentication\n\n# Create worktree for bug fixes\ngit worktree add ..\u002Fproject-bugfix-api hotfix\u002Fapi-validation\n\n# Create worktree for experiments\ngit worktree add ..\u002Fproject-experiment-new-ui experiment\u002Freact-19-upgrade\n```\n\n### Worktree Naming Convention\n\n```\n..\u002Fproject-\u003Ctype>-\u003Cdescription>\n```\n\n**Types**:\n- `feature` - New feature development\n- `bugfix` - Bug fixes\n- `hotfix` - Urgent production fixes\n- `experiment` - Experimental changes\n- `refactor` - Code refactoring\n\n**Examples**:\n- `..\u002Fmyapp-feature-user-auth`\n- `..\u002Fmyapp-bugfix-login-error`\n- `..\u002Fmyapp-hotfix-security-patch`\n\n### Managing Worktrees\n\n```bash\n# List all worktrees\ngit worktree list\n\n# Show details in long format\ngit worktree list --porcelain\n\n# Remove worktree after merging\ngit worktree remove ..\u002Fproject-feature-auth\n\n# Remove worktree (force if dirty)\ngit worktree remove --force ..\u002Fproject-experiment\n\n# Prune stale worktree information\ngit worktree prune\n```\n\n### Worktree Best Practices\n\n1. **Clean up after merging** - Remove worktrees after feature completion\n2. **Use descriptive names** - Follow naming convention\n3. **Keep main worktree clean** - Use for stable work only\n4. **Regular pruning** - Run `git worktree prune` periodically\n\n## ? Commit Standards\n\n### Conventional Commits\n\nFollow the [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) specification:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n[optional body]\n\n[optional footer]\n```\n\n### Commit Types\n\n```bash\n# New feature\ngit commit -m \"feat(auth): add JWT token refresh mechanism\"\n\n# Bug fix\ngit commit -m \"fix(api): handle null response appropriately\"\n\n# Documentation\ngit commit -m \"docs(readme): update installation instructions\"\n\n# Performance improvement\ngit commit -m \"perf(db): optimize query performance\"\n\n# Code refactoring\ngit commit -m \"refactor(core): extract validation logic\"\n\n# Testing\ngit commit -m \"test(auth): add unit tests for login flow\"\n\n# Build\u002Ftooling\ngit commit -m \"build(deps): upgrade react to v18\"\n\n# CI\u002FCD\ngit commit -m \"ci(github): add automated deployment workflow\"\n\n# Chores\ngit commit -m \"chore(deps): update development dependencies\"\n\n# Style changes (formatting, etc.)\ngit commit -m \"style(components): format with prettier\"\n```\n\n### Commit Type Reference\n\n| Type | Description | Example |\n|------|-------------|---------|\n| `feat` | New feature | Adding user authentication |\n| `fix` | Bug fix | Fixing null pointer error |\n| `docs` | Documentation only | Update README |\n| `style` | Formatting changes | Code formatting, no logic change |\n| `refactor` | Code refactoring | Restructure without behavior change |\n| `perf` | Performance improvement | Optimize algorithm |\n| `test` | Adding\u002Fupdating tests | Add unit tests |\n| `build` | Build system changes | Update webpack config |\n| `ci` | CI\u002FCD changes | Update GitHub Actions |\n| `chore` | Maintenance tasks | Update dependencies |\n| `revert` | Revert previous commit | Revert \"feat: add feature\" |\n\n### Commit Message Guidelines\n\n**Subject line**:\n- Use imperative mood (\"add\" not \"added\" or \"adds\")\n- Don't capitalize first letter\n- No period at the end\n- Maximum 50 characters\n\n**Body**:\n- Wrap at 72 characters\n- Explain what and why, not how\n- Use bullet points for multiple changes\n\n**Example**:\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nfeat(api): add user profile endpoint\n\n- Add GET \u002Fapi\u002Fusers\u002F:id endpoint\n- Include avatar URL in response\n- Add rate limiting (100 req\u002Fmin)\n\nThis allows frontend to fetch user details\nwithout additional API calls.\n\nCloses #123\nEOF\n)\"\n```\n\n### Commit Trailers\n\nAdd metadata to commits using trailers:\n\n```bash\n# Reference GitHub issue\ngit commit --trailer \"Github-Issue: #123\"\n\n# Credit bug reporter\ngit commit --trailer \"Reported-by: John Doe \u003Cjohn@example.com>\"\n\n# Reference related commits\ngit commit --trailer \"See-also: abc123\"\n\n# Co-author\ngit commit --trailer \"Co-authored-by: Jane Smith \u003Cjane@example.com>\"\n```\n\n**Example with multiple trailers**:\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nfix(auth): resolve token expiration issue\n\nFixed bug where expired tokens weren't properly\nrefreshed, causing users to be logged out unexpectedly.\n\nGithub-Issue: #456\nReported-by: John Doe \u003Cjohn@example.com>\nReviewed-by: Jane Smith \u003Cjane@example.com>\nEOF\n)\"\n```\n\n## ? Pull Request Guidelines\n\n### PR Title\n\nFollow the same format as commit messages:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n```\n\n**Examples**:\n- `feat(auth): add OAuth2 authentication`\n- `fix(api): resolve race condition in data sync`\n- `docs(contributing): update contributor guidelines`\n\n### PR Description Template\n\n```markdown\n## Summary\nBrief description of changes (1-3 sentences)\n\n## Changes\n- Bullet point list of main changes\n- Focus on what and why, not implementation details\n- Keep it high-level\n\n## Test Plan\n- [ ] Unit tests pass\n- [ ] Integration tests pass\n- [ ] Manual testing performed\n- [ ] Edge cases covered\n\n## Breaking Changes\nList any breaking changes (if applicable)\n\n## Related Issues\nCloses #123\nRelated to #456\n\n## Screenshots\u002FVideos\n(if applicable)\n```\n\n### PR Best Practices\n\n1. **Keep PRs small** - Easier to review, faster to merge\n2. **One feature per PR** - Don't mix unrelated changes\n3. **Update documentation** - Keep docs in sync with code\n4. **Add tests** - Don't merge without test coverage\n5. **Respond to reviews** - Address feedback promptly\n6. **Squash commits** - Clean up commit history before merge\n7. **Delete branch** - Clean up after merge\n\n### PR Review Checklist\n\n**Before requesting review**:\n- [ ] All tests pass\n- [ ] Code is formatted (linter passes)\n- [ ] Documentation updated\n- [ ] No console.log or debug code\n- [ ] Type safety verified (TypeScript)\n- [ ] Breaking changes documented\n\n**For reviewers**:\n- [ ] Code follows project conventions\n- [ ] Logic is clear and maintainable\n- [ ] Edge cases are handled\n- [ ] Tests are adequate\n- [ ] No security vulnerabilities\n- [ ] Performance considerations addressed\n\n## ? Git Workflow Checklist\n\nDaily workflow checklist:\n\n- [ ] Pull latest changes: `git pull`\n- [ ] Create feature branch or worktree\n- [ ] Make atomic commits with conventional format\n- [ ] Write meaningful commit messages\n- [ ] Push regularly: `git push`\n- [ ] Create PR with proper description\n- [ ] Address review feedback\n- [ ] Squash commits if needed\n- [ ] Merge and delete branch\u002Fworktree\n\n## ? Advanced Git Tips\n\n### Interactive Rebase\n\n```bash\n# Clean up last 3 commits\ngit rebase -i HEAD~3\n\n# Rebase onto main\ngit rebase -i main\n```\n\n### Cherry-pick Commits\n\n```bash\n# Apply specific commit to current branch\ngit cherry-pick abc123\n\n# Cherry-pick without committing\ngit cherry-pick --no-commit abc123\n```\n\n### Stash Management\n\n```bash\n# Stash with message\ngit stash push -m \"WIP: feature in progress\"\n\n# List stashes\ngit stash list\n\n# Apply and drop stash\ngit stash pop\n\n# Apply specific stash\ngit stash apply stash@{0}\n```\n\n### Bisect for Bug Hunting\n\n```bash\n# Start bisect\ngit bisect start\n\n# Mark current as bad\ngit bisect bad\n\n# Mark known good commit\ngit bisect good abc123\n\n# Let git find the culprit\n# Test each commit and mark good\u002Fbad\ngit bisect good  # or bad\n\n# End bisect\ngit bisect reset\n```\n\n## ? Common Mistakes to Avoid\n\n❌ **Don't**:\n- Commit directly to main\u002Fmaster\n- Use vague commit messages (\"fix bug\", \"update\")\n- Mix unrelated changes in one commit\n- Forget to pull before pushing\n- Leave WIP commits in PR\n- Skip commit message body for complex changes\n\n✅ **Do**:\n- Use feature branches or worktrees\n- Write descriptive conventional commits\n- Make atomic commits (one logical change)\n- Pull regularly and before pushing\n- Squash\u002Freword commits before merging\n- Provide context in commit body\n",{"name":5,"description":7,"allowed-tools":44},[32,45],"Read","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fcain96\u002Fgit-workflow",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill git-workflow",{"tool":61,"command":62},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill git-workflow",{"tool":64,"command":65},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill git-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fcain96\u002Fgit-workflow\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"skill-report.json","REFERENCE","参考文档",16292,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fcain96\u002Fgit-workflow\u002Fskill-report.json",[76,86,96,105,111,118],{"skillNo":77,"name":78,"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":79,"categories":80,"keywords":82,"publishedAt":39},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[81],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[83,84,85],"model","model hierarchy","model hierarchy skill",{"skillNo":87,"name":88,"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":89,"categories":90,"keywords":92,"publishedAt":39},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95],"MCP","zoom","zoom mcp",{"skillNo":97,"name":98,"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":99,"categories":100,"keywords":101,"publishedAt":39},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[102,103,104,94],"sdk","zoom apps sdk","apps",{"skillNo":106,"name":107,"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":108,"categories":109,"keywords":110,"publishedAt":39},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[107],{"skillNo":112,"name":113,"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":114,"categories":115,"keywords":117,"publishedAt":39},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[116],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[113],{"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":123,"publishedAt":39},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[120]]