[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75X13FAS75J6EN3SB551RYP":3,"skill-same:01M75X13FAS75J6EN3SB551RYP":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M75X13FAS75J6EN3SB551RYP","conventional-commits",null,"Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.","aAAaqwq\u002Fopenclaw-team","aAAaqwq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163369189?v=4","01M75WCZBK64XMP4RKNQB2ZV08","Daniel Li","01M75WCZCCEHPJV69BNPNXJY9E",2,"MIT","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fconventional-commits\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: conventional-commits\ndescription: Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.\nlicense: MIT\nmetadata:\n  author: github.com\u002Fbastos\n  version: \"2.0\"\n---\n\n# Conventional Commits\n\nFormat all commit messages according to the [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002Fen\u002Fv1.0.0\u002F) specification. This enables automated changelog generation, semantic versioning, and better commit history.\n\n## Format Structure\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Commit Types\n\n### Required Types\n\n- **`feat:`** - A new feature (correlates with MINOR in Semantic Versioning)\n- **`fix:`** - A bug fix (correlates with PATCH in Semantic Versioning)\n\n### Common Additional Types\n\n- **`docs:`** - Documentation only changes\n- **`style:`** - Code style changes (formatting, missing semicolons, etc.)\n- **`refactor:`** - Code refactoring without bug fixes or new features\n- **`perf:`** - Performance improvements\n- **`test:`** - Adding or updating tests\n- **`build:`** - Build system or external dependencies changes\n- **`ci:`** - CI\u002FCD configuration changes\n- **`chore:`** - Other changes that don't modify src or test files\n- **`revert:`** - Reverts a previous commit\n\n## Scope\n\nAn optional scope provides additional contextual information about the section of the codebase:\n\n```\nfeat(parser): add ability to parse arrays\nfix(auth): resolve token expiration issue\ndocs(readme): update installation instructions\n```\n\n## Description\n\n- Must immediately follow the colon and space after the type\u002Fscope\n- Use imperative mood (\"add feature\" not \"added feature\" or \"adds feature\")\n- Don't capitalize the first letter\n- No period at the end\n- Keep it concise (typically 50-72 characters)\n\n## Body\n\n- Optional longer description providing additional context\n- Must begin one blank line after the description\n- Can consist of multiple paragraphs\n- Explain the \"what\" and \"why\" of the change, not the \"how\"\n\n## Breaking Changes\n\nBreaking changes can be indicated in two ways:\n\n### 1. Using `!` in the type\u002Fscope\n\n```\nfeat!: send an email to the customer when a product is shipped\nfeat(api)!: send an email to the customer when a product is shipped\n```\n\n### 2. Using BREAKING CHANGE footer\n\n```\nfeat: allow provided config object to extend other configs\n\nBREAKING CHANGE: `extends` key in config file is now used for extending other config files\n```\n\n### 3. Both methods\n\n```\nchore!: drop support for Node 6\n\nBREAKING CHANGE: use JavaScript features not available in Node 6.\n```\n\n## Examples\n\n### Simple feature\n\n```\nfeat: add user authentication\n```\n\n### Feature with scope\n\n```\nfeat(auth): add OAuth2 support\n```\n\n### Bug fix with body\n\n```\nfix: prevent racing of requests\n\nIntroduce a request id and a reference to latest request. Dismiss\nincoming responses other than from latest request.\n\nRemove timeouts which were used to mitigate the racing issue but are\nobsolete now.\n```\n\n### Breaking change\n\n```\nfeat!: migrate to new API client\n\nBREAKING CHANGE: The API client interface has changed. All methods now\nreturn Promises instead of using callbacks.\n```\n\n### Documentation update\n\n```\ndocs: correct spelling of CHANGELOG\n```\n\n### Multi-paragraph body with footers\n\n```\nfix: prevent racing of requests\n\nIntroduce a request id and a reference to latest request. Dismiss\nincoming responses other than from latest request.\n\nRemove timeouts which were used to mitigate the racing issue but are\nobsolete now.\n\nReviewed-by: Z\nRefs: #123\n```\n\n## Guidelines\n\n1. **Always use a type** - Every commit must start with a type followed by a colon and space\n2. **Use imperative mood** - Write as if completing the sentence \"If applied, this commit will...\"\n3. **Be specific** - The description should clearly communicate what changed\n4. **Keep it focused** - One logical change per commit\n5. **Use scopes when helpful** - Scopes help categorize changes within a codebase\n6. **Document breaking changes** - Always indicate breaking changes clearly\n\n## Semantic Versioning Correlation\n\n- **`fix:`** → PATCH version bump (1.0.0 → 1.0.1)\n- **`feat:`** → MINOR version bump (1.0.0 → 1.1.0)\n- **BREAKING CHANGE** → MAJOR version bump (1.0.0 → 2.0.0)\n\n## When to Use\n\nUse this format for:\n- All git commits\n- Commit message generation\n- Pull request merge commits\n- When the user asks about commit messages or git commits\n\n## Common Mistakes to Avoid\n\n❌ `Added new feature` (past tense, capitalized)\n✅ `feat: add new feature` (imperative, lowercase)\n\n❌ `fix: bug` (too vague)\n✅ `fix: resolve null pointer exception in user service`\n\n❌ `feat: add feature` (redundant)\n✅ `feat: add user profile page`\n\n❌ `feat: Added OAuth support.` (past tense, period)\n✅ `feat: add OAuth support`\n","# Conventional Commits\n\nFormat all commit messages according to the [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002Fen\u002Fv1.0.0\u002F) specification. This enables automated changelog generation, semantic versioning, and better commit history.\n\n## Format Structure\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Commit Types\n\n### Required Types\n\n- **`feat:`** - A new feature (correlates with MINOR in Semantic Versioning)\n- **`fix:`** - A bug fix (correlates with PATCH in Semantic Versioning)\n\n### Common Additional Types\n\n- **`docs:`** - Documentation only changes\n- **`style:`** - Code style changes (formatting, missing semicolons, etc.)\n- **`refactor:`** - Code refactoring without bug fixes or new features\n- **`perf:`** - Performance improvements\n- **`test:`** - Adding or updating tests\n- **`build:`** - Build system or external dependencies changes\n- **`ci:`** - CI\u002FCD configuration changes\n- **`chore:`** - Other changes that don't modify src or test files\n- **`revert:`** - Reverts a previous commit\n\n## Scope\n\nAn optional scope provides additional contextual information about the section of the codebase:\n\n```\nfeat(parser): add ability to parse arrays\nfix(auth): resolve token expiration issue\ndocs(readme): update installation instructions\n```\n\n## Description\n\n- Must immediately follow the colon and space after the type\u002Fscope\n- Use imperative mood (\"add feature\" not \"added feature\" or \"adds feature\")\n- Don't capitalize the first letter\n- No period at the end\n- Keep it concise (typically 50-72 characters)\n\n## Body\n\n- Optional longer description providing additional context\n- Must begin one blank line after the description\n- Can consist of multiple paragraphs\n- Explain the \"what\" and \"why\" of the change, not the \"how\"\n\n## Breaking Changes\n\nBreaking changes can be indicated in two ways:\n\n### 1. Using `!` in the type\u002Fscope\n\n```\nfeat!: send an email to the customer when a product is shipped\nfeat(api)!: send an email to the customer when a product is shipped\n```\n\n### 2. Using BREAKING CHANGE footer\n\n```\nfeat: allow provided config object to extend other configs\n\nBREAKING CHANGE: `extends` key in config file is now used for extending other config files\n```\n\n### 3. Both methods\n\n```\nchore!: drop support for Node 6\n\nBREAKING CHANGE: use JavaScript features not available in Node 6.\n```\n\n## Examples\n\n### Simple feature\n\n```\nfeat: add user authentication\n```\n\n### Feature with scope\n\n```\nfeat(auth): add OAuth2 support\n```\n\n### Bug fix with body\n\n```\nfix: prevent racing of requests\n\nIntroduce a request id and a reference to latest request. Dismiss\nincoming responses other than from latest request.\n\nRemove timeouts which were used to mitigate the racing issue but are\nobsolete now.\n```\n\n### Breaking change\n\n```\nfeat!: migrate to new API client\n\nBREAKING CHANGE: The API client interface has changed. All methods now\nreturn Promises instead of using callbacks.\n```\n\n### Documentation update\n\n```\ndocs: correct spelling of CHANGELOG\n```\n\n### Multi-paragraph body with footers\n\n```\nfix: prevent racing of requests\n\nIntroduce a request id and a reference to latest request. Dismiss\nincoming responses other than from latest request.\n\nRemove timeouts which were used to mitigate the racing issue but are\nobsolete now.\n\nReviewed-by: Z\nRefs: #123\n```\n\n## Guidelines\n\n1. **Always use a type** - Every commit must start with a type followed by a colon and space\n2. **Use imperative mood** - Write as if completing the sentence \"If applied, this commit will...\"\n3. **Be specific** - The description should clearly communicate what changed\n4. **Keep it focused** - One logical change per commit\n5. **Use scopes when helpful** - Scopes help categorize changes within a codebase\n6. **Document breaking changes** - Always indicate breaking changes clearly\n\n## Semantic Versioning Correlation\n\n- **`fix:`** → PATCH version bump (1.0.0 → 1.0.1)\n- **`feat:`** → MINOR version bump (1.0.0 → 1.1.0)\n- **BREAKING CHANGE** → MAJOR version bump (1.0.0 → 2.0.0)\n\n## When to Use\n\nUse this format for:\n- All git commits\n- Commit message generation\n- Pull request merge commits\n- When the user asks about commit messages or git commits\n\n## Common Mistakes to Avoid\n\n❌ `Added new feature` (past tense, capitalized)\n✅ `feat: add new feature` (imperative, lowercase)\n\n❌ `fix: bug` (too vague)\n✅ `fix: resolve null pointer exception in user service`\n\n❌ `feat: add feature` (redundant)\n✅ `feat: add user profile page`\n\n❌ `feat: Added OAuth support.` (past tense, period)\n✅ `feat: add OAuth support`\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"github.com\u002Fbastos","2.0","main","f3f3769d02e636b7fc3aa4bb845009943b252e8f","workspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fconventional-commits",0,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team","https:\u002F\u002Fgithub.com\u002FaAAaqwq","https:\u002F\u002Fdaniel-li-portfolio.pages.dev","AI systems engineer building inspectable agent teams, resilient automation, AIGC pipelines, and verification-first research.","2026-06-18 10:28:29",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add aAAaqwq\u002Fopenclaw-team --skill conventional-commits",{"tool":42,"command":43},"bunx","bunx skills add aAAaqwq\u002Fopenclaw-team --skill conventional-commits",{"tool":45,"command":46},"pnpm","pnpm dlx skills add aAAaqwq\u002Fopenclaw-team --skill conventional-commits","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fconventional-commits\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"_meta.json","REFERENCE","参考文档",139,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fconventional-commits\u002F_meta.json",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},".clawhub\u002Forigin.json",152,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fconventional-commits\u002F.clawhub\u002Forigin.json",[61,68,75,83,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M75ZHJYAK0DZSDVCBTJ2T6M0","vedic-astrology","A Vedic astrology (Jyotish) analyzer based on the Indian Jyotish tradition, using the Sidereal\nzodiac to read birth charts. Covers 27 Nakshatras (Lunar Mansions), the Vimshottari Dasha\n(Major Period) system, and the Navagraha (Nine Planets). Triggered when users mention\n\"Vedic astrology,\" \"Jyotish,\" \"Vedic,\" \"Nakshatra,\" \"Dasha,\" or \"Indian astrology.\"\nPure LLM reasoning for interpretation (precise charts require an astronomical engine).\nNo external API required.\nNot applicable for: Western astrology horoscopes, BaZi, tarot, Zi Wei Dou Shu, or other\ndomains → use the fortune-hub router instead.","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fvedic-astrology\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M75ZGWAPH5ZXQXE9EVW13DYD","tracking-crypto-prices","Track real-time cryptocurrency prices across exchanges with historical data and alerts.\nProvides price data infrastructure for dependent skills (portfolio, tax, DeFi, arbitrage).\nUse when checking crypto prices, monitoring markets, or fetching historical price data.\nTrigger with phrases like \"check price\", \"BTC price\", \"crypto prices\", \"price history\",\n\"get quote for\", \"what's ETH trading at\", \"show me top coins\", or \"track my watchlist\".","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Ftracking-crypto-prices\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75ZCSEPN43PZCMJF3QG5940","risk-assessment","Framework-directable information security risk assessment. Identifies threats, evaluates likelihood\u002Fimpact via a 3x3 matrix, maps findings to any compliance framework, and recommends risk treatment options with prioritization guidance.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75ZC27KCZMJHQ25ZWC0YRE2","qimen-dunjia","奇门遁甲排盘分析器，基于洛书九宫四层盘面体系（天盘九星、地盘三奇六仪、人盘八门、神盘八神），\n支持时家奇门排盘，用于择时决策和事项预测。当用户提及「奇门遁甲」「奇门」「遁甲」「择时」\n「奇门排盘」「奇门预测」时触发。排盘为确定性计算 + LLM 综合解读，无外部 API 依赖。\n不适用于：梅花易数、六爻易经、风水分析、八字命理、塔罗占卜等其他领域 → 建议使用 fortune-hub 路由。","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fqimen-dunjia-oracle\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M75Z9ERP9C8N1E446MDXRMZN","negotiation","Tactical negotiation framework based on Chris Voss's \"Never Split the Difference.\" Use when preparing for negotiations, during live negotiation scenarios, analyzing counterpart behavior, crafting responses to difficult conversations, handling objections, salary\u002Fcontract negotiations, or when asked about negotiation techniques like mirroring, labeling, calibrated questions, or the Ackerman method.","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fnegotiation\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M75Z8S064PEAZACP8QPAXKQ4","meihua-yishu","梅花易数占卜工具，属于 fortune-telling-skills 运势测算套件。基于邵雍《梅花易数》体系，\n支持时间起卦、数字起卦、文字起卦等多种起卦方式，通过体用五行生克关系判断吉凶。\n起卦为确定性计算 + LLM 断卦解读，无外部 API 依赖。\n触发词：梅花易数、起卦、占卜、卦象、体用、八卦占卜、帮我起一卦、算一卦。\n不适用于：星座运势、塔罗占卜、八字命理 → 建议使用 fortune-hub。","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fmeihua-yishu-divination\u002FSKILL.md",[],[]]