[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMXHGSDRGEZ1Z4GEBJM992":3,"skill-same:01M7EMXHGSDRGEZ1Z4GEBJM992":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},"01M7EMXHGSDRGEZ1Z4GEBJM992","elasticsearch-pro",null,"Elasticsearch search and analytics — mappings, queries, and cluster health — use when building search or log analytics.","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-elasticsearch-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: elasticsearch-pro\ndescription: Elasticsearch search and analytics — mappings, queries, and cluster health — use when building search or log analytics.\ncategory: database\n---\n\n## Overview\n\nElasticsearch is a distributed search and analytics engine built on Lucene. Good\nresults come from three things: mappings designed before indexing, queries that\nuse the right clause for the job, and a cluster sized for the workload. This\nskill covers all three plus operational hygiene.\n\n## When to use\n\n- Designing index mappings and analyzers for full-text search\n- Writing `bool`, `match`, `term`, aggregation, and nested queries\n- Debugging relevance (\"why doesn't this document match?\")\n- Sizing shards, managing index lifecycle (ILM), and handling cluster health\n- Ingesting logs\u002Fmetrics and building Kibana-style dashboards\n\n## Core concepts\n\n**Mappings decide everything.** `text` fields are analyzed (tokenized, lowercased,\nstemmed) for full-text search; `keyword` fields are exact-match for filtering,\nsorting, and aggregations. Multi-fields (`\"fields\": {\"keyword\": {...}}`) give you\nboth. Dynamic mapping guesses types — often wrong (a date-like string becomes\n`text`) — so define explicit mappings for production indices.\n\n**Analyzers shape relevance.** The standard analyzer lowercases and tokenizes;\nlanguage analyzers stem (\"running\" → \"run\"). Custom analyzers (edge n-grams for\nautocomplete, keyword + lowercase for exact-ish match) solve specific UX needs.\nUse the `_analyze` API to see exactly how text is tokenized before debugging\nrelevance.\n\n**Query DSL: filter vs must.** `filter` clauses are cached and don't affect\nscoring — use them for yes\u002Fno constraints (status, tenant, date range). `must` \u002F\n`should` affect scoring for relevance-ranked parts. Mixing them correctly is the\ndifference between fast faceted search and slow scoring over everything.\n\n**Shards are the scaling unit — and the overhead unit.** Too few shards limits\nthroughput; too many (hundreds of tiny shards) wastes heap and slows the\ncluster. Aim for shards in the tens of GB, use ILM rollover to keep them sized\nright, and avoid the default \"one shard per tiny index\" sprawl.\n\n**Aggregations are analytics.** `terms`, `date_histogram`, `range`, and nested\naggs power faceted navigation and dashboards. They're computed across shards and\nmerged — `terms` on high-cardinality fields is approximate by design\n(`shard_size` tunes accuracy).\n\n## Practical workflow\n\n1. **Define the search UX first:** what fields are searched, filtered, sorted,\n   faceted? This drives the mapping (text vs keyword, which analyzers).\n2. **Create the index with explicit mappings and settings** (shards, replicas,\n   refresh interval); use index templates\u002Faliases so mappings evolve without\n   downtime (reindex into a new index, flip the alias).\n3. **Test relevance deliberately:** build a small judgment set of queries →\n   expected top results; iterate analyzers and boosts (`^2`) against it.\n4. **Write queries filter-first:** `bool` with `filter` for constraints, `must`\n   only for scored text; add `track_total_hits` consciously for deep pagination\n   (or use `search_after` instead of large `from`).\n5. **Manage lifecycle:** ILM policies (hot → warm → cold → delete) or\n   data streams for time-series; monitor shard counts, heap usage, and GC.\n6. **Operate:** keep replicas ≥ 1 in production, snapshot to durable storage on\n   a schedule, watch cluster health (green\u002Fyellow\u002Fred) and unassigned shards.\n\n## Common pitfalls\n\n- **Relying on dynamic mapping in production** — one bad document sets the field\n  type forever (until reindex). Explicit mappings or strict dynamic templates.\n- **Scoring everything:** putting filters in `must` instead of `filter` —\n  slower and noisier relevance. Filters don't score; use them.\n- **Deep pagination with `from: 100000`** — each shard sorts and discards;\n  use `search_after` with a tiebreaker sort for infinite scroll.\n- **Oversharding:** thousands of 50MB shards crush the master and heap. Fewer,\n  bigger shards; ILM rollover by size.\n- **`refresh_interval` left at 1s for bulk loads** — heavy indexing with\n  near-real-time refresh is slow; raise the interval (or -1) during bulk loads,\n  restore after.\n- **No snapshots** — a red cluster without snapshots is data loss waiting to\n  happen. Snapshot early, snapshot often, test restores.\n","## Overview\n\nElasticsearch is a distributed search and analytics engine built on Lucene. Good\nresults come from three things: mappings designed before indexing, queries that\nuse the right clause for the job, and a cluster sized for the workload. This\nskill covers all three plus operational hygiene.\n\n## When to use\n\n- Designing index mappings and analyzers for full-text search\n- Writing `bool`, `match`, `term`, aggregation, and nested queries\n- Debugging relevance (\"why doesn't this document match?\")\n- Sizing shards, managing index lifecycle (ILM), and handling cluster health\n- Ingesting logs\u002Fmetrics and building Kibana-style dashboards\n\n## Core concepts\n\n**Mappings decide everything.** `text` fields are analyzed (tokenized, lowercased,\nstemmed) for full-text search; `keyword` fields are exact-match for filtering,\nsorting, and aggregations. Multi-fields (`\"fields\": {\"keyword\": {...}}`) give you\nboth. Dynamic mapping guesses types — often wrong (a date-like string becomes\n`text`) — so define explicit mappings for production indices.\n\n**Analyzers shape relevance.** The standard analyzer lowercases and tokenizes;\nlanguage analyzers stem (\"running\" → \"run\"). Custom analyzers (edge n-grams for\nautocomplete, keyword + lowercase for exact-ish match) solve specific UX needs.\nUse the `_analyze` API to see exactly how text is tokenized before debugging\nrelevance.\n\n**Query DSL: filter vs must.** `filter` clauses are cached and don't affect\nscoring — use them for yes\u002Fno constraints (status, tenant, date range). `must` \u002F\n`should` affect scoring for relevance-ranked parts. Mixing them correctly is the\ndifference between fast faceted search and slow scoring over everything.\n\n**Shards are the scaling unit — and the overhead unit.** Too few shards limits\nthroughput; too many (hundreds of tiny shards) wastes heap and slows the\ncluster. Aim for shards in the tens of GB, use ILM rollover to keep them sized\nright, and avoid the default \"one shard per tiny index\" sprawl.\n\n**Aggregations are analytics.** `terms`, `date_histogram`, `range`, and nested\naggs power faceted navigation and dashboards. They're computed across shards and\nmerged — `terms` on high-cardinality fields is approximate by design\n(`shard_size` tunes accuracy).\n\n## Practical workflow\n\n1. **Define the search UX first:** what fields are searched, filtered, sorted,\n   faceted? This drives the mapping (text vs keyword, which analyzers).\n2. **Create the index with explicit mappings and settings** (shards, replicas,\n   refresh interval); use index templates\u002Faliases so mappings evolve without\n   downtime (reindex into a new index, flip the alias).\n3. **Test relevance deliberately:** build a small judgment set of queries →\n   expected top results; iterate analyzers and boosts (`^2`) against it.\n4. **Write queries filter-first:** `bool` with `filter` for constraints, `must`\n   only for scored text; add `track_total_hits` consciously for deep pagination\n   (or use `search_after` instead of large `from`).\n5. **Manage lifecycle:** ILM policies (hot → warm → cold → delete) or\n   data streams for time-series; monitor shard counts, heap usage, and GC.\n6. **Operate:** keep replicas ≥ 1 in production, snapshot to durable storage on\n   a schedule, watch cluster health (green\u002Fyellow\u002Fred) and unassigned shards.\n\n## Common pitfalls\n\n- **Relying on dynamic mapping in production** — one bad document sets the field\n  type forever (until reindex). Explicit mappings or strict dynamic templates.\n- **Scoring everything:** putting filters in `must` instead of `filter` —\n  slower and noisier relevance. Filters don't score; use them.\n- **Deep pagination with `from: 100000`** — each shard sorts and discards;\n  use `search_after` with a tiebreaker sort for infinite scroll.\n- **Oversharding:** thousands of 50MB shards crush the master and heap. Fewer,\n  bigger shards; ILM rollover by size.\n- **`refresh_interval` left at 1s for bulk loads** — heavy indexing with\n  near-real-time refresh is slow; raise the interval (or -1) during bulk loads,\n  restore after.\n- **No snapshots** — a red cluster without snapshots is data loss waiting to\n  happen. Snapshot early, snapshot often, test restores.\n",{"name":5,"category":24,"description":7},"database","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-elasticsearch-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 elasticsearch-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill elasticsearch-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill elasticsearch-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-elasticsearch-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",[],[]]