[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN6EY6CEVXE3P04610SSH3":3,"skill-same:01M7EN6EY6CEVXE3P04610SSH3":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EN6EY6CEVXE3P04610SSH3","granite-guide",null,"Build with IBM's Granite models — enterprise open models for code, language, and business applications.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-granite-guide\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: granite-guide\ndescription: Build with IBM's Granite models — enterprise open models for code, language, and business applications.\ncategory: ai-research\n---\n\n## Overview\n\nGranite (IBM) is an enterprise-oriented open model family spanning code,\nlanguage, and specialized business models (including time-series and\nvision variants) — built with IBM's enterprise focus: training-data\ntransparency, indemnification offerings, and watsonx platform integration.\nThe positioning is \"open models safe for enterprise\" — Apache 2.0 licensing\non key releases plus IBM's enterprise assurances.\n\nFor builders in IBM-centric enterprises, Granite is the natural open-model\nchoice: watsonx integration, enterprise support, and licensing clarity. For\nothers, Granite deserves evaluation as a solid open family — particularly\nwhere licensing simplicity (Apache 2.0) and enterprise assurances matter.\n\nThe distinctive note: IBM's indemnification and transparency commitments\naddress enterprise legal concerns directly. Evaluate whether that assurance\nhas value for your organization's risk posture.\n\n## When to use\n\n- IBM\u002Fwatsonx-centric enterprises building on open models.\n- Applications needing Apache 2.0 licensed open models.\n- Enterprise deployments valuing vendor indemnification.\n- Code and language tasks on open models with enterprise support.\n- Regulated industries needing documented, assured AI components.\n- Time-series and specialized enterprise tasks (Granite's specialized\n  variants).\n\n## Core concepts\n\n- **Enterprise open models**: open weights with enterprise assurances —\n  the combination is the differentiator.\n- **Apache 2.0 licensing**: permissive licensing on key releases. Verify per\n  release; the simplicity vs. community licenses is real.\n- **Indemnification**: IBM's IP indemnification offerings for enterprise\n  deployments. Understand the scope — what it covers and what it doesn't.\n- **Code and language families**: Granite code models and language models\n  for respective tasks. Benchmark each on your tasks.\n- **Specialized variants**: time-series (Chronos-style), vision, and other\n  enterprise-task models. Match variant to task.\n- **watsonx integration**: native platform integration for IBM-stack teams —\n  deployment, governance, and tooling.\n- **Training transparency**: documented training approaches supporting\n  enterprise risk assessment.\n- **Enterprise support**: vendor support for open models — unusual and\n  valuable for risk-averse organizations.\n\n## Practical workflow\n\n1. **Clarify assurance requirements.** What does your organization need:\n   licensing simplicity, indemnification, support, transparency? Get specific.\n2. **Benchmark model quality.** Granite code and language models vs.\n   alternatives (Llama, Qwen, DeepSeek) on your tasks. Assurances don't\n   replace quality evaluation.\n3. **Verify licensing per release.** Confirm Apache 2.0 (or other) terms for\n   your chosen models and use case.\n4. **Understand indemnification scope.** Read the actual terms — coverage,\n   exclusions, and claim processes.\n5. **Evaluate watsonx fit.** If on IBM stack: test the integrated deployment\n   and governance paths. If not: evaluate Granite as standalone open models.\n6. **Test specialized variants.** For time-series or other specialized tasks:\n   benchmark the Granite specialist against alternatives.\n7. **Pin, monitor, document.** Version pins; quality monitoring; the assurance\n   documentation filed for compliance.\n\nChecklist for Granite in production:\n- Assurance requirements specified and matched to IBM's offerings.\n- Quality benchmarked against open-model alternatives.\n- License verified per release.\n- Indemnification scope understood.\n- Specialized variants tested where relevant.\n\n## Common pitfalls\n\n- **Assurance as quality proxy.** Enterprise assurances address legal risk,\n  not model quality. Benchmark anyway.\n- **Indemnification over-read.** Assuming broader coverage than the terms\n  provide. Read the scope.\n- **No peer benchmarks.** Choosing on enterprise comfort without testing\n  against Llama\u002FQwen\u002FDeepSeek on your tasks.\n- **watsonx assumed.** Committing to the platform without evaluating whether\n  the integration benefits your team.\n- **License per-release unchecked.** Assuming all Granite releases share\n  terms.\n- **Specialized variants ignored.** Missing the time-series and other\n  specialists that may fit enterprise tasks well.\n- **Support expectations vague.** Not clarifying what enterprise support\n  actually covers before depending on it.\n- **Static enterprise choice.** Deciding once on assurance grounds and never\n  re-benchmarking quality as the open field advances.\n","## Overview\n\nGranite (IBM) is an enterprise-oriented open model family spanning code,\nlanguage, and specialized business models (including time-series and\nvision variants) — built with IBM's enterprise focus: training-data\ntransparency, indemnification offerings, and watsonx platform integration.\nThe positioning is \"open models safe for enterprise\" — Apache 2.0 licensing\non key releases plus IBM's enterprise assurances.\n\nFor builders in IBM-centric enterprises, Granite is the natural open-model\nchoice: watsonx integration, enterprise support, and licensing clarity. For\nothers, Granite deserves evaluation as a solid open family — particularly\nwhere licensing simplicity (Apache 2.0) and enterprise assurances matter.\n\nThe distinctive note: IBM's indemnification and transparency commitments\naddress enterprise legal concerns directly. Evaluate whether that assurance\nhas value for your organization's risk posture.\n\n## When to use\n\n- IBM\u002Fwatsonx-centric enterprises building on open models.\n- Applications needing Apache 2.0 licensed open models.\n- Enterprise deployments valuing vendor indemnification.\n- Code and language tasks on open models with enterprise support.\n- Regulated industries needing documented, assured AI components.\n- Time-series and specialized enterprise tasks (Granite's specialized\n  variants).\n\n## Core concepts\n\n- **Enterprise open models**: open weights with enterprise assurances —\n  the combination is the differentiator.\n- **Apache 2.0 licensing**: permissive licensing on key releases. Verify per\n  release; the simplicity vs. community licenses is real.\n- **Indemnification**: IBM's IP indemnification offerings for enterprise\n  deployments. Understand the scope — what it covers and what it doesn't.\n- **Code and language families**: Granite code models and language models\n  for respective tasks. Benchmark each on your tasks.\n- **Specialized variants**: time-series (Chronos-style), vision, and other\n  enterprise-task models. Match variant to task.\n- **watsonx integration**: native platform integration for IBM-stack teams —\n  deployment, governance, and tooling.\n- **Training transparency**: documented training approaches supporting\n  enterprise risk assessment.\n- **Enterprise support**: vendor support for open models — unusual and\n  valuable for risk-averse organizations.\n\n## Practical workflow\n\n1. **Clarify assurance requirements.** What does your organization need:\n   licensing simplicity, indemnification, support, transparency? Get specific.\n2. **Benchmark model quality.** Granite code and language models vs.\n   alternatives (Llama, Qwen, DeepSeek) on your tasks. Assurances don't\n   replace quality evaluation.\n3. **Verify licensing per release.** Confirm Apache 2.0 (or other) terms for\n   your chosen models and use case.\n4. **Understand indemnification scope.** Read the actual terms — coverage,\n   exclusions, and claim processes.\n5. **Evaluate watsonx fit.** If on IBM stack: test the integrated deployment\n   and governance paths. If not: evaluate Granite as standalone open models.\n6. **Test specialized variants.** For time-series or other specialized tasks:\n   benchmark the Granite specialist against alternatives.\n7. **Pin, monitor, document.** Version pins; quality monitoring; the assurance\n   documentation filed for compliance.\n\nChecklist for Granite in production:\n- Assurance requirements specified and matched to IBM's offerings.\n- Quality benchmarked against open-model alternatives.\n- License verified per release.\n- Indemnification scope understood.\n- Specialized variants tested where relevant.\n\n## Common pitfalls\n\n- **Assurance as quality proxy.** Enterprise assurances address legal risk,\n  not model quality. Benchmark anyway.\n- **Indemnification over-read.** Assuming broader coverage than the terms\n  provide. Read the scope.\n- **No peer benchmarks.** Choosing on enterprise comfort without testing\n  against Llama\u002FQwen\u002FDeepSeek on your tasks.\n- **watsonx assumed.** Committing to the platform without evaluating whether\n  the integration benefits your team.\n- **License per-release unchecked.** Assuming all Granite releases share\n  terms.\n- **Specialized variants ignored.** Missing the time-series and other\n  specialists that may fit enterprise tasks well.\n- **Support expectations vague.** Not clarifying what enterprise support\n  actually covers before depending on it.\n- **Static enterprise choice.** Deciding once on assurance grounds and never\n  re-benchmarking quality as the open field advances.\n",{"name":5,"category":24,"description":7},"ai-research","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-granite-guide",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill granite-guide",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill granite-guide",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill granite-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-granite-guide\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]