[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWF8NB728A3CDCQYGDKSA3":3,"skill-same:01M7EWF8NB728A3CDCQYGDKSA3":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},"01M7EWF8NB728A3CDCQYGDKSA3","yaml-pro",null,"YAML authoring and processing — gotchas, validation, and safe loading — use when writing configs or parsing YAML.","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-yaml-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: yaml-pro\ndescription: YAML authoring and processing — gotchas, validation, and safe loading — use when writing configs or parsing YAML.\ncategory: document-processing\n---\n\n## Overview\n\nYAML is the config language of the DevOps world — readable, but full of\nfootguns (the infamous `no` → `false`, octal surprises, billion-laughs\nattacks). This skill covers writing safe, predictable YAML and parsing it\ndefensively in code.\n\n## When to use\n\n- Authoring configs (CI pipelines, Kubernetes manifests, app settings)\n- Designing YAML-based file formats or DSLs\n- Parsing YAML safely in applications (avoiding deserialization attacks)\n- Templating YAML (anchors, merge keys, and when to avoid them)\n- Validating YAML configs with schemas in CI\n\n## Core concepts\n\n**Quote defensively.** YAML's implicit typing converts unquoted `yes\u002Fno\u002Fon\u002Foff`,\n`0o17`-style numbers, and version-like strings (`3.10` → `3.1`). Quote strings\nthat could be misinterpreted — especially versions, identifiers with leading\nzeros (`\"007\"`), and anything resembling a boolean. Explicit is better than\nclever.\n\n**Safe loading only.** Never use a full YAML loader on untrusted input — it can\ninstantiate arbitrary objects (the classic deserialization attack). Always use\nthe safe loader, which handles only plain scalars, lists, and maps. This is\nnon-negotiable for any YAML from users or networks.\n\n**Anchors and merge keys: use sparingly.** `&anchor` \u002F `*alias` \u002F `\u003C\u003C: *merge`\nreduce duplication in hand-written configs, but they complicate programmatic\nprocessing and confuse newcomers. Fine for small DRY wins; for heavy reuse,\nprefer a templating layer or config generation in code.\n\n**Schema-validate configs.** JSON Schema validates YAML too (YAML is a superset\nof JSON). Validate CI configs, app settings, and manifests against a schema in\nCI — catching a typo'd key at commit time beats debugging a silent misconfig\nin production.\n\n**Multi-document files.** `---` separates documents in one stream; some tools\nread only the first. Know whether your consumer handles multi-doc files before\nrelying on them.\n\n## Practical workflow\n\n1. **Start from a known-good example** for the target system; adapt minimally\n   rather than writing from memory.\n2. **Quote aggressively:** versions, booleans-as-strings, leading-zero numbers,\n   and any value where the type matters downstream.\n3. **Keep nesting shallow** (3–4 levels max); deep nesting is hard to read and\n   easy to mis-indent — refactor into flatter structures or multiple files.\n4. **Validate in CI:** schema check + a dry-run\u002Fparse of the consuming tool\n   (e.g. `kubectl --dry-run`, CI config linter) on every change.\n5. **In code, always safe-load;** convert to typed config objects with defaults\n   and validation immediately after parsing — don't pass raw dicts around.\n6. **Document the config:** a commented example file or schema with\n   descriptions is worth more than a wiki page nobody updates.\n\n## Common pitfalls\n\n- **The Norway problem:** `no`\u002F`yes`\u002F`on`\u002F`off` becoming booleans — quote\n  country codes and string flags.\n- **Tabs for indentation** — forbidden in YAML; use spaces, consistently (2 is\n  the convention).\n- **Version `3.10` parsed as float `3.1`** — quote versions, always.\n- **Merge-key surprises:** `\u003C\u003C: *base` silently overrides in non-obvious order\n  with multiple merges; prefer explicit keys for critical settings.\n- **Giant YAML files** generated by tools — split into multiple files with\n  clear naming; 2000-line YAML is unreviewable.\n- **Secrets in YAML committed to git** — configs get committed; secrets don't\n  belong in them. Reference secret stores via placeholders resolved at deploy\n  time.\n","## Overview\n\nYAML is the config language of the DevOps world — readable, but full of\nfootguns (the infamous `no` → `false`, octal surprises, billion-laughs\nattacks). This skill covers writing safe, predictable YAML and parsing it\ndefensively in code.\n\n## When to use\n\n- Authoring configs (CI pipelines, Kubernetes manifests, app settings)\n- Designing YAML-based file formats or DSLs\n- Parsing YAML safely in applications (avoiding deserialization attacks)\n- Templating YAML (anchors, merge keys, and when to avoid them)\n- Validating YAML configs with schemas in CI\n\n## Core concepts\n\n**Quote defensively.** YAML's implicit typing converts unquoted `yes\u002Fno\u002Fon\u002Foff`,\n`0o17`-style numbers, and version-like strings (`3.10` → `3.1`). Quote strings\nthat could be misinterpreted — especially versions, identifiers with leading\nzeros (`\"007\"`), and anything resembling a boolean. Explicit is better than\nclever.\n\n**Safe loading only.** Never use a full YAML loader on untrusted input — it can\ninstantiate arbitrary objects (the classic deserialization attack). Always use\nthe safe loader, which handles only plain scalars, lists, and maps. This is\nnon-negotiable for any YAML from users or networks.\n\n**Anchors and merge keys: use sparingly.** `&anchor` \u002F `*alias` \u002F `\u003C\u003C: *merge`\nreduce duplication in hand-written configs, but they complicate programmatic\nprocessing and confuse newcomers. Fine for small DRY wins; for heavy reuse,\nprefer a templating layer or config generation in code.\n\n**Schema-validate configs.** JSON Schema validates YAML too (YAML is a superset\nof JSON). Validate CI configs, app settings, and manifests against a schema in\nCI — catching a typo'd key at commit time beats debugging a silent misconfig\nin production.\n\n**Multi-document files.** `---` separates documents in one stream; some tools\nread only the first. Know whether your consumer handles multi-doc files before\nrelying on them.\n\n## Practical workflow\n\n1. **Start from a known-good example** for the target system; adapt minimally\n   rather than writing from memory.\n2. **Quote aggressively:** versions, booleans-as-strings, leading-zero numbers,\n   and any value where the type matters downstream.\n3. **Keep nesting shallow** (3–4 levels max); deep nesting is hard to read and\n   easy to mis-indent — refactor into flatter structures or multiple files.\n4. **Validate in CI:** schema check + a dry-run\u002Fparse of the consuming tool\n   (e.g. `kubectl --dry-run`, CI config linter) on every change.\n5. **In code, always safe-load;** convert to typed config objects with defaults\n   and validation immediately after parsing — don't pass raw dicts around.\n6. **Document the config:** a commented example file or schema with\n   descriptions is worth more than a wiki page nobody updates.\n\n## Common pitfalls\n\n- **The Norway problem:** `no`\u002F`yes`\u002F`on`\u002F`off` becoming booleans — quote\n  country codes and string flags.\n- **Tabs for indentation** — forbidden in YAML; use spaces, consistently (2 is\n  the convention).\n- **Version `3.10` parsed as float `3.1`** — quote versions, always.\n- **Merge-key surprises:** `\u003C\u003C: *base` silently overrides in non-obvious order\n  with multiple merges; prefer explicit keys for critical settings.\n- **Giant YAML files** generated by tools — split into multiple files with\n  clear naming; 2000-line YAML is unreviewable.\n- **Secrets in YAML committed to git** — configs get committed; secrets don't\n  belong in them. Reference secret stores via placeholders resolved at deploy\n  time.\n",{"name":5,"category":24,"description":7},"document-processing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-yaml-pro",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 yaml-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill yaml-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill yaml-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-yaml-pro\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",[],[]]