[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVY49Z4P7CGHVT31EMH0PR":3,"skill-same:01M7EVY49Z4P7CGHVT31EMH0PR":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVY49Z4P7CGHVT31EMH0PR","ams-shell-pro",null,"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-shell-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: shell-pro\ndescription: Professional shell scripting: safe Bash patterns, quoting, error handling, and maintainable CLI tools. Use when writing or reviewing shell scripts.\ncategory: development\n---\n\n# Shell Pro\n\n## Overview\n\nShell scripts are **the glue of operations** — and the source of legendary 3am failures when\nwritten casually. Professional shell scripting means defensive defaults (`set -euo pipefail`),\nobsessive quoting, explicit error handling, and knowing when the script has outgrown shell\n(rewrite in Python\u002FGo at ~200 lines or when you need real data structures).\n\nThe through-line: assume every command can fail, every variable can be empty, and every filename\ncan contain spaces.\n\n## When to use\n\n- Writing or reviewing Bash\u002FPOSIX shell scripts.\n- Building CLI wrappers, deploy scripts, or CI helpers.\n- Debugging scripts that \"work on my machine\" but fail in CI.\n- Deciding between shell and a \"real\" language.\n- Hardening existing scripts (quoting, error handling, idempotency).\n\n## Core concepts\n\n- **Strict mode first.** `set -euo pipefail` — exit on error, error on undefined variables, and\n  fail pipelines when any stage fails. Add `IFS=$'\\n\\t'` deliberately when word-splitting behavior\n  matters. This one line prevents entire bug classes.\n- **Quote everything.** `\"$var\"`, `\"$(cmd)\"`, `\"$@\"` — always. Unquoted expansions split on\n  whitespace and glob — the source of \"works until a filename has a space.\" The only unquoted\n  things should be intentionally-split lists.\n- **Errors are explicit.** Check exit codes where they matter; `cmd || die \"context\"` patterns;\n  `trap` for cleanup (temp files, locks) on exit. A script that fails silently is worse than one\n  that crashes loudly.\n- **Functions for structure.** Small named functions with `local` variables; `main \"$@\"` at the\n  bottom; usage\u002Fhelp text. A 300-line flat script is unmaintainable — structure it like code,\n  because it is.\n- **Idempotency and safety.** Scripts that run twice shouldn't break things; destructive operations\n  get `--dry-run` modes and confirmation prompts; `rm -rf \"$dir\u002F\"` with an empty `$dir` is how\n  legends are born — guard it (`: \"${dir:?dir must be set}\"`).\n- **Know when to stop.** Complex JSON parsing (use `jq`, or switch languages), data structures\n  beyond arrays\u002Fassociative arrays, heavy logic — these are signs to rewrite in Python. Shell is\n  for orchestration, not computation.\n\n## Practical workflow\n\n1. **Start every script with the template:**\n   ```bash\n   #!\u002Fusr\u002Fbin\u002Fenv bash\n   set -euo pipefail\n   die() { echo \"ERROR: $*\" >&2; exit 1; }\n   usage() { echo \"Usage: $(basename \"$0\") [options] \u003Carg>\"; }\n   ```\n2. **Parse arguments properly.** `getopts` for short flags; explicit `--long` handling or a tiny\n   parser for long options. Validate required args and fail with usage on misuse.\n3. **Write functions, keep main thin.** Each function does one thing; `local` all function\n   variables; return codes meaningful (0 = ok).\n4. **Handle temp files and cleanup.** `tmpdir=$(mktemp -d)` + `trap 'rm -rf \"$tmpdir\"' EXIT` —\n   always. Lock files for scripts that must not run concurrently (`flock`).\n5. **Test the failure modes.** Run with `bash -x` to trace; test with empty vars, missing files,\n   spaces in names, and non-zero exits from dependencies. ShellCheck in CI — non-negotiable.\n6. **Document the contract.** Header comment: purpose, usage, required tools\u002Fenv vars, exit codes.\n   The next person running this at 3am thanks you.\n\nRobust script skeleton:\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\ndie() { echo \"ERROR: $*\" >&2; exit 1; }\nlog() { echo \"[$(date -u +%FT%TZ)] $*\"; }\n\nmain() {\n  local src=\"${1:?Usage: $0 \u003Csrc-dir>}\"\n  [[ -d \"$src\" ]] || die \"not a directory: $src\"\n  local tmp; tmp=$(mktemp -d)\n  trap 'rm -rf \"$tmp\"' EXIT\n  log \"processing $src ...\"\n  # ... work, quoting everything ...\n  log \"done\"\n}\n\nmain \"$@\"\n```\n\n## Common pitfalls\n\n- **Unquoted variables.** The #1 shell bug. `rm -rf $dir` with empty `$dir` tries to delete\n  everything. Quote. Everything.\n- **No `set -euo pipefail`.** Scripts that barrel past failures, then report success. Or the\n  subtler: pipelines masking failures (`false | true` succeeds without pipefail).\n- **`set -e` surprises.** It doesn't trigger in all contexts (conditions, `&&`\u002F`||` chains).\n  Know its semantics or check critical commands explicitly.\n- **Parsing `ls` output.** Filenames with newlines\u002Fspaces break it. Use globs or `find -print0 |\n  while IFS= read -r -d ''`.\n- **curl\u002Fwget without failure flags.** `curl -o file url` succeeding with an error page saved as\n  \"success.\" Use `curl -fsSL` (fail, silent, show errors, follow redirects).\n- **Assuming GNU tools.** BSD vs GNU `sed`\u002F`date`\u002F`grep` differences break scripts across macOS\n  and Linux. Test on both or document the requirement.\n- **Scripts that grow forever.** The 800-line Bash deployment script nobody dares touch. Refactor\n  into functions early; rewrite in a real language when structure demands it.\n","# Shell Pro\n\n## Overview\n\nShell scripts are **the glue of operations** — and the source of legendary 3am failures when\nwritten casually. Professional shell scripting means defensive defaults (`set -euo pipefail`),\nobsessive quoting, explicit error handling, and knowing when the script has outgrown shell\n(rewrite in Python\u002FGo at ~200 lines or when you need real data structures).\n\nThe through-line: assume every command can fail, every variable can be empty, and every filename\ncan contain spaces.\n\n## When to use\n\n- Writing or reviewing Bash\u002FPOSIX shell scripts.\n- Building CLI wrappers, deploy scripts, or CI helpers.\n- Debugging scripts that \"work on my machine\" but fail in CI.\n- Deciding between shell and a \"real\" language.\n- Hardening existing scripts (quoting, error handling, idempotency).\n\n## Core concepts\n\n- **Strict mode first.** `set -euo pipefail` — exit on error, error on undefined variables, and\n  fail pipelines when any stage fails. Add `IFS=$'\\n\\t'` deliberately when word-splitting behavior\n  matters. This one line prevents entire bug classes.\n- **Quote everything.** `\"$var\"`, `\"$(cmd)\"`, `\"$@\"` — always. Unquoted expansions split on\n  whitespace and glob — the source of \"works until a filename has a space.\" The only unquoted\n  things should be intentionally-split lists.\n- **Errors are explicit.** Check exit codes where they matter; `cmd || die \"context\"` patterns;\n  `trap` for cleanup (temp files, locks) on exit. A script that fails silently is worse than one\n  that crashes loudly.\n- **Functions for structure.** Small named functions with `local` variables; `main \"$@\"` at the\n  bottom; usage\u002Fhelp text. A 300-line flat script is unmaintainable — structure it like code,\n  because it is.\n- **Idempotency and safety.** Scripts that run twice shouldn't break things; destructive operations\n  get `--dry-run` modes and confirmation prompts; `rm -rf \"$dir\u002F\"` with an empty `$dir` is how\n  legends are born — guard it (`: \"${dir:?dir must be set}\"`).\n- **Know when to stop.** Complex JSON parsing (use `jq`, or switch languages), data structures\n  beyond arrays\u002Fassociative arrays, heavy logic — these are signs to rewrite in Python. Shell is\n  for orchestration, not computation.\n\n## Practical workflow\n\n1. **Start every script with the template:**\n   ```bash\n   #!\u002Fusr\u002Fbin\u002Fenv bash\n   set -euo pipefail\n   die() { echo \"ERROR: $*\" >&2; exit 1; }\n   usage() { echo \"Usage: $(basename \"$0\") [options] \u003Carg>\"; }\n   ```\n2. **Parse arguments properly.** `getopts` for short flags; explicit `--long` handling or a tiny\n   parser for long options. Validate required args and fail with usage on misuse.\n3. **Write functions, keep main thin.** Each function does one thing; `local` all function\n   variables; return codes meaningful (0 = ok).\n4. **Handle temp files and cleanup.** `tmpdir=$(mktemp -d)` + `trap 'rm -rf \"$tmpdir\"' EXIT` —\n   always. Lock files for scripts that must not run concurrently (`flock`).\n5. **Test the failure modes.** Run with `bash -x` to trace; test with empty vars, missing files,\n   spaces in names, and non-zero exits from dependencies. ShellCheck in CI — non-negotiable.\n6. **Document the contract.** Header comment: purpose, usage, required tools\u002Fenv vars, exit codes.\n   The next person running this at 3am thanks you.\n\nRobust script skeleton:\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\ndie() { echo \"ERROR: $*\" >&2; exit 1; }\nlog() { echo \"[$(date -u +%FT%TZ)] $*\"; }\n\nmain() {\n  local src=\"${1:?Usage: $0 \u003Csrc-dir>}\"\n  [[ -d \"$src\" ]] || die \"not a directory: $src\"\n  local tmp; tmp=$(mktemp -d)\n  trap 'rm -rf \"$tmp\"' EXIT\n  log \"processing $src ...\"\n  # ... work, quoting everything ...\n  log \"done\"\n}\n\nmain \"$@\"\n```\n\n## Common pitfalls\n\n- **Unquoted variables.** The #1 shell bug. `rm -rf $dir` with empty `$dir` tries to delete\n  everything. Quote. Everything.\n- **No `set -euo pipefail`.** Scripts that barrel past failures, then report success. Or the\n  subtler: pipelines masking failures (`false | true` succeeds without pipefail).\n- **`set -e` surprises.** It doesn't trigger in all contexts (conditions, `&&`\u002F`||` chains).\n  Know its semantics or check critical commands explicitly.\n- **Parsing `ls` output.** Filenames with newlines\u002Fspaces break it. Use globs or `find -print0 |\n  while IFS= read -r -d ''`.\n- **curl\u002Fwget without failure flags.** `curl -o file url` succeeding with an error page saved as\n  \"success.\" Use `curl -fsSL` (fail, silent, show errors, follow redirects).\n- **Assuming GNU tools.** BSD vs GNU `sed`\u002F`date`\u002F`grep` differences break scripts across macOS\n  and Linux. Test on both or document the requirement.\n- **Scripts that grow forever.** The 800-line Bash deployment script nobody dares touch. Refactor\n  into functions early; rewrite in a real language when structure demands it.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-shell-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":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-shell-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-shell-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-shell-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-shell-pro\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"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",[],[]]