[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVA1FJC0DDS3PZ68VJQSEC":3,"skill-same:01M7EVA1FJC0DDS3PZ68VJQSEC":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},"01M7EVA1FJC0DDS3PZ68VJQSEC","ams-perl-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-perl-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: perl-pro\ndescription: Idiomatic modern Perl: strict\u002Fwarnings, CPAN, references, regex mastery, and maintainable scripting. Use when writing, reviewing, or maintaining Perl code.\ncategory: development\n---\n\n# Perl Pro\n\n## Overview\n\nPerl's reputation for write-only code is earned by *bad* Perl — modern, disciplined Perl\n(**`strict`, `warnings`, signatures, CPAN modules, and testing**) is a superb text-processing and\nglue language. Professional Perl means using the modern toolchain (perl 5.36+, `use v5.36` enabling\nstrict\u002Fwarnings\u002Fsignatures), writing readable rather than golfed code, and leaning on CPAN instead\nof reinventing.\n\nThe through-line: Perl rewards the disciplined — strictures on, warnings heeded, golf left on the course.\n\n## When to use\n\n- Writing or reviewing Perl scripts and modules.\n- Modernizing legacy Perl (adding strict, tests, structure).\n- Text processing, log analysis, and system glue tasks.\n- Choosing CPAN modules or structuring distributions.\n- Debugging regex, reference, or context issues.\n\n## Core concepts\n\n- **`use v5.36;` (or strict + warnings + signatures).** Modern version bundles enable strict,\n  warnings, and subroutine signatures — the three features that prevent most Perl footguns.\n  `use warnings FATAL => 'all'` in new code turns warnings into loud failures during development.\n- **Context is the language.** Scalar vs list context changes what expressions *mean*\n  (`my $n = @arr` gives count; `my @c = @arr` copies). Master `wantarray`, and be deliberate —\n  context bugs are Perl's unique sharp edge.\n- **References for complex data.** Arrays of hashes via references (`$orders->[0]{total}`);\n  dereference deliberately (`@{ $ref }`, `%{ $ref }`); autovivification is convenient until it\n  silently creates deep structures from typos — check existence with `exists` before deep access\n  in critical code.\n- **Regex as a precision tool.** Perl regexes are the best in the business — use `\u002Fx` for readable\n  multiline patterns with comments, named captures (`(?\u003Cyear>\\d{4})`), and non-greedy quantifiers\n  deliberately. Compile once (`qr\u002F\u002F`) for repeated use; never build regexes from untrusted input\n  without `\\Q...\\E` quoting.\n- **CPAN, not NIH.** `cpanm` for installation; prefer well-maintained modules (Mojolicious for web,\n  DBI for databases, Path::Tiny for files, Try::Tiny or builtin `try` for exceptions). Check\n  maintenance status — abandoned CPAN modules are a liability.\n- **Testing with Test::More\u002FTest2.** `prove` runs the suite; test modules, not just scripts;\n  `Test::Exception`\u002F`Test::Warn` for failure modes. Perl's testing culture is one of its best\n  features — use it.\n\n## Practical workflow\n\n1. **Start every file:** `use v5.36; use warnings;` — non-negotiable. Add `use utf8;` and\n   `use open ':std', ':encoding(UTF-8)';` for text work.\n2. **Structure:** scripts for one-offs (`script\u002F`), modules in `lib\u002F` with proper packages\n   (`package Orders::Processor;`), distributions via `Dist::Zilla` or `Minilla` for anything shared.\n3. **Write readable Perl.** Named variables over `$_` in complex code, signatures over `@_`\n   shifting, early returns, small subs. Golf is for fun, not production.\n4. **Handle errors explicitly.** `die` with context for programmer errors; `Try::Tiny`\u002F`try`-`catch`\n   or eval-blocks for recoverable failures; check system call returns (`open … or die \"…: $!\"` —\n   always include `$!`).\n5. **Test as you go.** `t\u002F*.t` with Test2; run with `prove -l`. Mock external systems at the\n   boundary; test the parsing\u002Ftransform logic heavily — that's where Perl earns its keep.\n6. **Mind the encoding.** Perl's Unicode handling is powerful but opt-in: decode inputs, encode\n   outputs, and test with non-ASCII data early. Mojibake discovered in production is a rite of\n   passage nobody needs.\n\nIdiomatic snippets:\n\n```perl\nuse v5.36;\n\n# Signatures + named captures + \u002Fx readability\nsub parse_log_line ($line) {\n    return unless $line =~ m{\n        ^(?\u003Cts>\\d{4}-\\d{2}-\\d{2}\\s+\\d{2}:\\d{2}:\\d{2})\n        \\s+ \\[(?\u003Clevel>\\w+)\\]\n        \\s+ (?\u003Cmsg>.*)\n    }x;\n    return { ts => $+{ts}, level => $+{level}, msg => $+{msg} };\n}\n\n# Safe file handling with Path::Tiny\nuse Path::Tiny;\nmy $content = path($file)->slurp_utf8;\n```\n\n## Common pitfalls\n\n- **No strict\u002Fwarnings.** The original sin — typos become new variables, and warnings that would\n  have caught bugs scroll by unheeded.\n- **Golf in production.** `$_`, `$a`, nested map\u002Fgrep one-liners that take ten minutes to parse.\n  Write for the maintainer, not the leaderboard.\n- **Context bugs.** A sub returning a list assigned to scalar (or vice versa) — silent wrong\n  behavior. Be explicit: document return context, or return references.\n- **Autovivification surprises.** `$config->{db}{host}` creating intermediate hashes from a typo'd\n  key. Use `exists`\u002Fdefined checks or `no autovivification` in strict code paths.\n- **Bareword and indirect-object pitfalls.** `new Class` vs `Class->new` — indirect object syntax\n  has parsing gotchas; always use `->`.\n- **Regex injection.** Interpolating user input into regexes without `\\Q...\\E`. And catastrophic\n  backtracking in nested quantifiers — test regexes against adversarial input.\n- **Ignoring CPAN maintenance.** Depending on a module untouched since 2009. Check reverse\n  dependencies, recent releases, and open issues before committing.\n","# Perl Pro\n\n## Overview\n\nPerl's reputation for write-only code is earned by *bad* Perl — modern, disciplined Perl\n(**`strict`, `warnings`, signatures, CPAN modules, and testing**) is a superb text-processing and\nglue language. Professional Perl means using the modern toolchain (perl 5.36+, `use v5.36` enabling\nstrict\u002Fwarnings\u002Fsignatures), writing readable rather than golfed code, and leaning on CPAN instead\nof reinventing.\n\nThe through-line: Perl rewards the disciplined — strictures on, warnings heeded, golf left on the course.\n\n## When to use\n\n- Writing or reviewing Perl scripts and modules.\n- Modernizing legacy Perl (adding strict, tests, structure).\n- Text processing, log analysis, and system glue tasks.\n- Choosing CPAN modules or structuring distributions.\n- Debugging regex, reference, or context issues.\n\n## Core concepts\n\n- **`use v5.36;` (or strict + warnings + signatures).** Modern version bundles enable strict,\n  warnings, and subroutine signatures — the three features that prevent most Perl footguns.\n  `use warnings FATAL => 'all'` in new code turns warnings into loud failures during development.\n- **Context is the language.** Scalar vs list context changes what expressions *mean*\n  (`my $n = @arr` gives count; `my @c = @arr` copies). Master `wantarray`, and be deliberate —\n  context bugs are Perl's unique sharp edge.\n- **References for complex data.** Arrays of hashes via references (`$orders->[0]{total}`);\n  dereference deliberately (`@{ $ref }`, `%{ $ref }`); autovivification is convenient until it\n  silently creates deep structures from typos — check existence with `exists` before deep access\n  in critical code.\n- **Regex as a precision tool.** Perl regexes are the best in the business — use `\u002Fx` for readable\n  multiline patterns with comments, named captures (`(?\u003Cyear>\\d{4})`), and non-greedy quantifiers\n  deliberately. Compile once (`qr\u002F\u002F`) for repeated use; never build regexes from untrusted input\n  without `\\Q...\\E` quoting.\n- **CPAN, not NIH.** `cpanm` for installation; prefer well-maintained modules (Mojolicious for web,\n  DBI for databases, Path::Tiny for files, Try::Tiny or builtin `try` for exceptions). Check\n  maintenance status — abandoned CPAN modules are a liability.\n- **Testing with Test::More\u002FTest2.** `prove` runs the suite; test modules, not just scripts;\n  `Test::Exception`\u002F`Test::Warn` for failure modes. Perl's testing culture is one of its best\n  features — use it.\n\n## Practical workflow\n\n1. **Start every file:** `use v5.36; use warnings;` — non-negotiable. Add `use utf8;` and\n   `use open ':std', ':encoding(UTF-8)';` for text work.\n2. **Structure:** scripts for one-offs (`script\u002F`), modules in `lib\u002F` with proper packages\n   (`package Orders::Processor;`), distributions via `Dist::Zilla` or `Minilla` for anything shared.\n3. **Write readable Perl.** Named variables over `$_` in complex code, signatures over `@_`\n   shifting, early returns, small subs. Golf is for fun, not production.\n4. **Handle errors explicitly.** `die` with context for programmer errors; `Try::Tiny`\u002F`try`-`catch`\n   or eval-blocks for recoverable failures; check system call returns (`open … or die \"…: $!\"` —\n   always include `$!`).\n5. **Test as you go.** `t\u002F*.t` with Test2; run with `prove -l`. Mock external systems at the\n   boundary; test the parsing\u002Ftransform logic heavily — that's where Perl earns its keep.\n6. **Mind the encoding.** Perl's Unicode handling is powerful but opt-in: decode inputs, encode\n   outputs, and test with non-ASCII data early. Mojibake discovered in production is a rite of\n   passage nobody needs.\n\nIdiomatic snippets:\n\n```perl\nuse v5.36;\n\n# Signatures + named captures + \u002Fx readability\nsub parse_log_line ($line) {\n    return unless $line =~ m{\n        ^(?\u003Cts>\\d{4}-\\d{2}-\\d{2}\\s+\\d{2}:\\d{2}:\\d{2})\n        \\s+ \\[(?\u003Clevel>\\w+)\\]\n        \\s+ (?\u003Cmsg>.*)\n    }x;\n    return { ts => $+{ts}, level => $+{level}, msg => $+{msg} };\n}\n\n# Safe file handling with Path::Tiny\nuse Path::Tiny;\nmy $content = path($file)->slurp_utf8;\n```\n\n## Common pitfalls\n\n- **No strict\u002Fwarnings.** The original sin — typos become new variables, and warnings that would\n  have caught bugs scroll by unheeded.\n- **Golf in production.** `$_`, `$a`, nested map\u002Fgrep one-liners that take ten minutes to parse.\n  Write for the maintainer, not the leaderboard.\n- **Context bugs.** A sub returning a list assigned to scalar (or vice versa) — silent wrong\n  behavior. Be explicit: document return context, or return references.\n- **Autovivification surprises.** `$config->{db}{host}` creating intermediate hashes from a typo'd\n  key. Use `exists`\u002Fdefined checks or `no autovivification` in strict code paths.\n- **Bareword and indirect-object pitfalls.** `new Class` vs `Class->new` — indirect object syntax\n  has parsing gotchas; always use `->`.\n- **Regex injection.** Interpolating user input into regexes without `\\Q...\\E`. And catastrophic\n  backtracking in nested quantifiers — test regexes against adversarial input.\n- **Ignoring CPAN maintenance.** Depending on a module untouched since 2009. Check reverse\n  dependencies, recent releases, and open issues before committing.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-perl-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-perl-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-perl-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-perl-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-perl-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",[],[]]