[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C11XBRCQ4K2S1390H2YPQT":3,"skill-same:01M6C11XBRCQ4K2S1390H2YPQT":48},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M6C11XBRCQ4K2S1390H2YPQT","dependency-management",null,"Procedures and requirements for adding new external dependencies.","vorburger\u002Faifiles","vorburger","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298598?v=4","01M6C11R5X69DM3ZRH19WVATJ5","Michael Vorburger","01M6C11RAG3NAQQZ7S3QNG7ER4",0,"CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fdependency-management\u002FSKILL.md",[],[19,20],"management","dependency management","2026-11-10 10:12:30",false,"---\nname: dependency-management\ndescription: Procedures and requirements for adding new external dependencies.\n---\n\n# Dependency Management\n\nWhen adding any new external dependencies to the project — whether Maven\u002FGradle dependencies or plugins, or NPM\u002FBun packages — you MUST:\n\n1. Find and visit the originating Git repository for the project\n2. Check the maintenance status:\n   - Last commit date (should be recent, ideally within the last 6 months)\n   - Issue response time and activity\n   - Number of open issues and PRs\n3. **Find and use the latest available version** of the dependency:\n   - Check Maven Central, npm registry, or the GitHub releases page for the newest release\n   - Always prefer recent versions over older ones (unless there's a specific reason to pin to an older version)\n4. If the project appears abandoned or minimally maintained:\n   - **DO NOT** add it without explicit approval\n   - Inform the user about the maintenance concerns\n   - Search for and suggest a more actively maintained alternative\n\nThis prevents the project from accumulating stale, unmaintained dependencies that could become security risks or cause compatibility issues, and keeps us on recent stable versions with bug fixes and security patches.\n\n## Handling Failing Dependency Update PRs\n\nWhen automated dependency update PRs (e.g. from Dependabot or Renovate) fail due to upstream compatibility issues or ecosystem lag (for example, a new major language\u002Fcompiler version not yet supported by linters or plugins):\n\n1. **Investigate the Root Cause**: Determine if the failure is due to a temporary ecosystem incompatibility (such as an upstream tool waiting on a stable API or upcoming release).\n2. **Find the Upstream Tracking Issue**: Search the relevant upstream project's issue tracker (e.g., GitHub Issues) to find the tracking issue or milestone for supporting the new version.\n3. **Do NOT Hardcode Workarounds**: Avoid adding temporary ignores or exclusions to configuration files (e.g., `.github\u002Fdependabot.yaml` or `package.json` overrides) to suppress PRs, as this creates technical debt and obscures when upstream support arrives.\n4. **Document on the PR**: Leave a comment linking the upstream tracking issue (e.g., `Pending \u003Cupstream-issue-url>`) so the PR status is clearly understood and can be merged or updated once the upstream fix lands.\n","# Dependency Management\n\nWhen adding any new external dependencies to the project — whether Maven\u002FGradle dependencies or plugins, or NPM\u002FBun packages — you MUST:\n\n1. Find and visit the originating Git repository for the project\n2. Check the maintenance status:\n   - Last commit date (should be recent, ideally within the last 6 months)\n   - Issue response time and activity\n   - Number of open issues and PRs\n3. **Find and use the latest available version** of the dependency:\n   - Check Maven Central, npm registry, or the GitHub releases page for the newest release\n   - Always prefer recent versions over older ones (unless there's a specific reason to pin to an older version)\n4. If the project appears abandoned or minimally maintained:\n   - **DO NOT** add it without explicit approval\n   - Inform the user about the maintenance concerns\n   - Search for and suggest a more actively maintained alternative\n\nThis prevents the project from accumulating stale, unmaintained dependencies that could become security risks or cause compatibility issues, and keeps us on recent stable versions with bug fixes and security patches.\n\n## Handling Failing Dependency Update PRs\n\nWhen automated dependency update PRs (e.g. from Dependabot or Renovate) fail due to upstream compatibility issues or ecosystem lag (for example, a new major language\u002Fcompiler version not yet supported by linters or plugins):\n\n1. **Investigate the Root Cause**: Determine if the failure is due to a temporary ecosystem incompatibility (such as an upstream tool waiting on a stable API or upcoming release).\n2. **Find the Upstream Tracking Issue**: Search the relevant upstream project's issue tracker (e.g., GitHub Issues) to find the tracking issue or milestone for supporting the new version.\n3. **Do NOT Hardcode Workarounds**: Avoid adding temporary ignores or exclusions to configuration files (e.g., `.github\u002Fdependabot.yaml` or `package.json` overrides) to suppress PRs, as this creates technical debt and obscures when upstream support arrives.\n4. **Document on the PR**: Leave a comment linking the upstream tracking issue (e.g., `Pending \u003Cupstream-issue-url>`) so the PR status is clearly understood and can be merged or updated once the upstream fix lands.\n",{"name":5,"description":7},"main","6cfcb4ea30a31850a900583021f7ef2b5159538f","skills\u002Fdependency-management","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles","https:\u002F\u002Fgithub.com\u002Fvorburger","http:\u002F\u002Fwww.vorburger.ch"," 🇺🇦 #KyivNotKiev. Geek Father. EPFL alumni. Speaks Esperanto, Java, no Klingon, but a few other langs. Works at Google. Formerly at Red Hat. Repos personal.","2026-10-18 19:44:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vorburger\u002Faifiles --skill dependency-management",{"tool":40,"command":41},"bunx","bunx skills add vorburger\u002Faifiles --skill dependency-management",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vorburger\u002Faifiles --skill dependency-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fdependency-management\u002FSKILL.md",true,[],[49,59,72,87,95,104],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":21},"01M6C12QVGQB262AXE96P898W5","vorburger-profile","Provides personal and professional information about Michael Vorburger.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fvorburger-profile\u002FSKILL.md",[],[56,57,58],"vorburger profile","profile","personal",{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":21},"01M6C12NWCGZ83F0WCSQR8TBC0","typescript-conventions","Enforces TypeScript and project-specific coding standards, including Bun usage and the zero-warning policy. Use this skill when creating or modifying any TypeScript or configuration files.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-conventions\u002FSKILL.md",[],[66,67,68,69,70,71],"typescript conventions","typescript","policy","coding standards","ZeRO","coding",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":21},"01M6C12KVA8A1HDX56XKJQF93K","testing","Guidelines for determining how to test a project based on its contents.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[74,84,85,86],"test","guidelines","how",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":21},"01M6C12JK1GP5KP4AMKDY5AQJR","skills","Rules for Agent Skills files.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fskills\u002FSKILL.md",[],[94],"Rules",{"skillNo":96,"name":97,"nameZh":6,"description":98,"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":21},"01M6C12GTNMWM6NAB1ZAEJ20NE","scripting","Conventions for writing and executing scripts (TS, Bash, etc.).","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fscripting\u002FSKILL.md",[],[97,102,103],"Bash","writing",{"skillNo":105,"name":106,"nameZh":6,"description":107,"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":21},"01M6C12F45S1D29YM5HMEAE10S","preferred-tools","Preferred tools for common tasks like linting and link checking.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fpreferred-tools\u002FSKILL.md",[],[111,112,113,114],"Tools","preferred tools","common","tasks"]