[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMCHB2WVVNBJSJ9QY9N2T7":3,"skill-same:01M7EMCHB2WVVNBJSJ9QY9N2T7":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},"01M7EMCHB2WVVNBJSJ9QY9N2T7","baichuan-guide",null,"Build with Baichuan's open models — bilingual Chinese-English models for general and specialized tasks.","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-baichuan-guide\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: baichuan-guide\ndescription: Build with Baichuan's open models — bilingual Chinese-English models for general and specialized tasks.\ncategory: ai-research\n---\n\n## Overview\n\nBaichuan is a Chinese AI company releasing bilingual Chinese-English open\nmodels across sizes, from general-purpose base models to specialized variants.\nThe family has been a consistent presence in the Chinese open-model ecosystem,\nwith releases spanning chat, base models for fine-tuning, and domain-focused\nversions.\n\nFor builders, Baichuan is another candidate in the bilingual open-model set —\nrelevant when your application serves Chinese-speaking users and you want\nbreadth in your evaluation. Like all bilingual families, the evaluation must\nbe per-language on your real tasks.\n\nThe practical stance: include Baichuan in bilingual benchmarks; don't assume\n— measure. In a crowded Chinese open-model field, the only way to know where\na family stands for your workload is head-to-head testing on your data.\n\n## When to use\n\n- Bilingual Chinese-English applications.\n- Open-model evaluations for Chinese-language quality.\n- Fine-tuning bilingual base models.\n- Applications needing Chinese open-model diversity in the candidate set.\n- Research comparing Chinese open-model families.\n\n## Core concepts\n\n- **Bilingual models**: Chinese-English training focus. Evaluate each language\n  separately on your tasks.\n- **Size range**: multiple sizes across releases. Ladder-test for right-sizing.\n- **Base and chat variants**: base models for fine-tuning; chat-tuned for\n  assistants. Choose correctly.\n- **Specialized versions**: domain or task-focused releases. Match to your\n  task where applicable.\n- **Open weights**: downloadable, self-hostable. Verify license per release.\n- **Standard deployment**: common inference stacks and provider APIs.\n- **Chinese ecosystem**: documentation and community resources may be\n  Chinese-primary — factor into team accessibility.\n- **Release tracking**: the family evolves; evaluate current releases.\n\n## Practical workflow\n\n1. **Build a bilingual eval set.** Reflecting your real Chinese\u002FEnglish task\n   mix.\n2. **Benchmark against bilingual peers.** Baichuan vs. Qwen, Yi, DeepSeek,\n   InternLM — per-language scores.\n3. **Test the right variant.** Chat for assistants; base for fine-tuning;\n   specialized versions for their domains.\n4. **Right-size.** Smallest adequate model via ladder testing.\n5. **Verify licensing.** Per-release terms for your use case.\n6. **Assess ecosystem fit.** Documentation language, community support,\n   provider hosting availability for your team.\n7. **Pin versions.** Production stability; deliberate upgrade cadence.\n\nChecklist for Baichuan in production:\n- Bilingual evals with per-language scoring.\n- Peer comparison completed.\n- Correct variant (base\u002Fchat\u002Fspecialized) selected.\n- License verified; version pinned.\n- Team can work with the ecosystem (docs, support).\n\n## Common pitfalls\n\n- **Single-language evals.** Testing English only for a bilingual deployment.\n- **No peer comparison.** Choosing without benchmarking alternatives.\n- **Variant mismatch.** Chat model for fine-tuning base, or vice versa.\n- **Ecosystem friction.** Team can't read the primary documentation language\n  — operational drag.\n- **License unchecked.** Assuming terms.\n- **Stale releases.** Evaluating old versions; the current release is what\n  matters.\n- **Size by default.** Not ladder-testing.\n- **Version drift.** Unpinned references in production.\n","## Overview\n\nBaichuan is a Chinese AI company releasing bilingual Chinese-English open\nmodels across sizes, from general-purpose base models to specialized variants.\nThe family has been a consistent presence in the Chinese open-model ecosystem,\nwith releases spanning chat, base models for fine-tuning, and domain-focused\nversions.\n\nFor builders, Baichuan is another candidate in the bilingual open-model set —\nrelevant when your application serves Chinese-speaking users and you want\nbreadth in your evaluation. Like all bilingual families, the evaluation must\nbe per-language on your real tasks.\n\nThe practical stance: include Baichuan in bilingual benchmarks; don't assume\n— measure. In a crowded Chinese open-model field, the only way to know where\na family stands for your workload is head-to-head testing on your data.\n\n## When to use\n\n- Bilingual Chinese-English applications.\n- Open-model evaluations for Chinese-language quality.\n- Fine-tuning bilingual base models.\n- Applications needing Chinese open-model diversity in the candidate set.\n- Research comparing Chinese open-model families.\n\n## Core concepts\n\n- **Bilingual models**: Chinese-English training focus. Evaluate each language\n  separately on your tasks.\n- **Size range**: multiple sizes across releases. Ladder-test for right-sizing.\n- **Base and chat variants**: base models for fine-tuning; chat-tuned for\n  assistants. Choose correctly.\n- **Specialized versions**: domain or task-focused releases. Match to your\n  task where applicable.\n- **Open weights**: downloadable, self-hostable. Verify license per release.\n- **Standard deployment**: common inference stacks and provider APIs.\n- **Chinese ecosystem**: documentation and community resources may be\n  Chinese-primary — factor into team accessibility.\n- **Release tracking**: the family evolves; evaluate current releases.\n\n## Practical workflow\n\n1. **Build a bilingual eval set.** Reflecting your real Chinese\u002FEnglish task\n   mix.\n2. **Benchmark against bilingual peers.** Baichuan vs. Qwen, Yi, DeepSeek,\n   InternLM — per-language scores.\n3. **Test the right variant.** Chat for assistants; base for fine-tuning;\n   specialized versions for their domains.\n4. **Right-size.** Smallest adequate model via ladder testing.\n5. **Verify licensing.** Per-release terms for your use case.\n6. **Assess ecosystem fit.** Documentation language, community support,\n   provider hosting availability for your team.\n7. **Pin versions.** Production stability; deliberate upgrade cadence.\n\nChecklist for Baichuan in production:\n- Bilingual evals with per-language scoring.\n- Peer comparison completed.\n- Correct variant (base\u002Fchat\u002Fspecialized) selected.\n- License verified; version pinned.\n- Team can work with the ecosystem (docs, support).\n\n## Common pitfalls\n\n- **Single-language evals.** Testing English only for a bilingual deployment.\n- **No peer comparison.** Choosing without benchmarking alternatives.\n- **Variant mismatch.** Chat model for fine-tuning base, or vice versa.\n- **Ecosystem friction.** Team can't read the primary documentation language\n  — operational drag.\n- **License unchecked.** Assuming terms.\n- **Stale releases.** Evaluating old versions; the current release is what\n  matters.\n- **Size by default.** Not ladder-testing.\n- **Version drift.** Unpinned references in production.\n",{"name":5,"category":24,"description":7},"ai-research","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-baichuan-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 baichuan-guide",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill baichuan-guide",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill baichuan-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-baichuan-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",[],[]]