[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVFR5S5DHA7PFM4NXYDVPD":3,"skill-same:01M7EVFR5S5DHA7PFM4NXYDVPD":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},"01M7EVFR5S5DHA7PFM4NXYDVPD","postgres-pro",null,"Deep PostgreSQL know-how — indexing, tuning, JSONB, and administration — use when working with or troubleshooting Postgres.","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-postgres-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: postgres-pro\ndescription: Deep PostgreSQL know-how — indexing, tuning, JSONB, and administration — use when working with or troubleshooting Postgres.\ncategory: database\n---\n\n## Overview\n\nPostgreSQL is a production workhorse: ACID-compliant, extensible, and generous with\nfeatures (JSONB, full-text search, arrays, PostGIS). This skill covers the\noperational knowledge that separates a working Postgres setup from a reliable one:\nchoosing indexes, reading plans, tuning configuration, and safe administration.\n\n## When to use\n\n- Choosing between B-tree, GIN, GiST, BRIN, or hash indexes\n- Investigating slow queries with `EXPLAIN (ANALYZE, BUFFERS)`\n- Tuning `shared_buffers`, `work_mem`, `maintenance_work_mem`, autovacuum\n- Designing schemas with JSONB, arrays, or full-text search\n- Managing backups, replication, connections, and upgrades\n\n## Core concepts\n\n**Index types matter.** B-tree is the default and right for most lookups and range\nqueries. GIN powers JSONB containment (`@>`) and full-text search; GiST handles\ngeometric and range types; BRIN shines for very large, naturally ordered tables\n(time-series). A GIN index on a JSONB column can turn a 10-second scan into a\n10-millisecond lookup — but adds write overhead.\n\n**MVCC and bloat.** Postgres never overwrites rows in place; updates create new\nrow versions and dead tuples are reclaimed by VACUUM. Long-running transactions\nblock cleanup and cause bloat. Monitor `pg_stat_user_tables` for tables where\n`n_dead_tup` grows faster than autovacuum cleans.\n\n**`EXPLAIN (ANALYZE, BUFFERS)` is ground truth.** It shows actual row counts,\ntiming per node, and buffer hits vs disk reads. Compare estimated vs actual rows:\na 100x misestimate usually means stale statistics (`ANALYZE`) or a bad plan forced\nby them.\n\n**Connection discipline.** Postgres uses a process per connection; thousands of\nidle connections waste memory. Use a pooler (PgBouncer in transaction mode) in\nfront of the database and keep `max_connections` modest.\n\n**JSONB done right.** Store flexible documents in `jsonb`, query with `->` \u002F `->>`,\nindex hot paths with GIN or expression indexes. Don't use JSONB as an excuse to\nskip schema design — frequently queried fields often deserve real columns.\n\n## Practical workflow\n\n1. **Diagnose with data:** `EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)` on the slow\n   query; find the node consuming most time.\n2. **Check the usual suspects:** missing index (Seq Scan on a large filtered\n   table), stale stats (`ANALYZE table_name`), bloat (`pgstattuple`), lock waits\n   (`pg_stat_activity`).\n3. **Create indexes deliberately:** one composite index on `(filtered_col,\n   ordered_col)` often beats two single-column indexes; use `CONCURRENTLY` in\n   production to avoid locking the table:\n   ```sql\n   CREATE INDEX CONCURRENTLY idx_orders_customer_date\n     ON orders (customer_id, order_date DESC);\n   ```\n4. **Tune conservatively:** start with `shared_buffers` ≈ 25% of RAM,\n   `effective_cache_size` ≈ 75% of RAM, `work_mem` small (4–64MB) — raise only\n   with evidence of sorts spilling to disk (`EXPLAIN` shows \"Disk:\" sorts).\n5. **Backups before changes:** verify `pg_dump`\u002F`pg_basebackup` restores actually\n   work — an untested backup is not a backup. Test restores on a schedule.\n6. **Safe migrations:** add columns as nullable (or with defaults via metadata-only\n   changes in modern versions), backfill in batches, then add `NOT NULL` with\n   `VALIDATE CONSTRAINT` to avoid long locks.\n\n## Common pitfalls\n\n- **Killing autovacuum or disabling it** — leads to bloat, transaction-ID wraparound\n  risk, and eventually downtime. Tune it, don't disable it.\n- **Creating indexes without `CONCURRENTLY`** on live tables — takes an\n  `ACCESS EXCLUSIVE` lock and blocks writes.\n- **Wrapping indexed columns in functions** in `WHERE` (e.g.\n  `WHERE lower(email) = ...`) — defeats the index unless you create an expression\n  index on `lower(email)`.\n- **`SELECT ... FOR UPDATE` without ordering** — invites deadlocks under\n  concurrency; lock rows in a consistent order.\n- **Timezone bugs:** `timestamp without time zone` silently shifts meaning.\n  Prefer `timestamptz` and convert at the presentation layer.\n- **Running out of connections** under load — add pooling before raising\n  `max_connections`; each connection costs real memory.\n","## Overview\n\nPostgreSQL is a production workhorse: ACID-compliant, extensible, and generous with\nfeatures (JSONB, full-text search, arrays, PostGIS). This skill covers the\noperational knowledge that separates a working Postgres setup from a reliable one:\nchoosing indexes, reading plans, tuning configuration, and safe administration.\n\n## When to use\n\n- Choosing between B-tree, GIN, GiST, BRIN, or hash indexes\n- Investigating slow queries with `EXPLAIN (ANALYZE, BUFFERS)`\n- Tuning `shared_buffers`, `work_mem`, `maintenance_work_mem`, autovacuum\n- Designing schemas with JSONB, arrays, or full-text search\n- Managing backups, replication, connections, and upgrades\n\n## Core concepts\n\n**Index types matter.** B-tree is the default and right for most lookups and range\nqueries. GIN powers JSONB containment (`@>`) and full-text search; GiST handles\ngeometric and range types; BRIN shines for very large, naturally ordered tables\n(time-series). A GIN index on a JSONB column can turn a 10-second scan into a\n10-millisecond lookup — but adds write overhead.\n\n**MVCC and bloat.** Postgres never overwrites rows in place; updates create new\nrow versions and dead tuples are reclaimed by VACUUM. Long-running transactions\nblock cleanup and cause bloat. Monitor `pg_stat_user_tables` for tables where\n`n_dead_tup` grows faster than autovacuum cleans.\n\n**`EXPLAIN (ANALYZE, BUFFERS)` is ground truth.** It shows actual row counts,\ntiming per node, and buffer hits vs disk reads. Compare estimated vs actual rows:\na 100x misestimate usually means stale statistics (`ANALYZE`) or a bad plan forced\nby them.\n\n**Connection discipline.** Postgres uses a process per connection; thousands of\nidle connections waste memory. Use a pooler (PgBouncer in transaction mode) in\nfront of the database and keep `max_connections` modest.\n\n**JSONB done right.** Store flexible documents in `jsonb`, query with `->` \u002F `->>`,\nindex hot paths with GIN or expression indexes. Don't use JSONB as an excuse to\nskip schema design — frequently queried fields often deserve real columns.\n\n## Practical workflow\n\n1. **Diagnose with data:** `EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)` on the slow\n   query; find the node consuming most time.\n2. **Check the usual suspects:** missing index (Seq Scan on a large filtered\n   table), stale stats (`ANALYZE table_name`), bloat (`pgstattuple`), lock waits\n   (`pg_stat_activity`).\n3. **Create indexes deliberately:** one composite index on `(filtered_col,\n   ordered_col)` often beats two single-column indexes; use `CONCURRENTLY` in\n   production to avoid locking the table:\n   ```sql\n   CREATE INDEX CONCURRENTLY idx_orders_customer_date\n     ON orders (customer_id, order_date DESC);\n   ```\n4. **Tune conservatively:** start with `shared_buffers` ≈ 25% of RAM,\n   `effective_cache_size` ≈ 75% of RAM, `work_mem` small (4–64MB) — raise only\n   with evidence of sorts spilling to disk (`EXPLAIN` shows \"Disk:\" sorts).\n5. **Backups before changes:** verify `pg_dump`\u002F`pg_basebackup` restores actually\n   work — an untested backup is not a backup. Test restores on a schedule.\n6. **Safe migrations:** add columns as nullable (or with defaults via metadata-only\n   changes in modern versions), backfill in batches, then add `NOT NULL` with\n   `VALIDATE CONSTRAINT` to avoid long locks.\n\n## Common pitfalls\n\n- **Killing autovacuum or disabling it** — leads to bloat, transaction-ID wraparound\n  risk, and eventually downtime. Tune it, don't disable it.\n- **Creating indexes without `CONCURRENTLY`** on live tables — takes an\n  `ACCESS EXCLUSIVE` lock and blocks writes.\n- **Wrapping indexed columns in functions** in `WHERE` (e.g.\n  `WHERE lower(email) = ...`) — defeats the index unless you create an expression\n  index on `lower(email)`.\n- **`SELECT ... FOR UPDATE` without ordering** — invites deadlocks under\n  concurrency; lock rows in a consistent order.\n- **Timezone bugs:** `timestamp without time zone` silently shifts meaning.\n  Prefer `timestamptz` and convert at the presentation layer.\n- **Running out of connections** under load — add pooling before raising\n  `max_connections`; each connection costs real memory.\n",{"name":5,"category":24,"description":7},"database","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-postgres-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 postgres-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill postgres-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill postgres-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-postgres-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",[],[]]