[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWBV37375ZCWHN3ER2KZAC":3,"skill-same:01M7EWBV37375ZCWHN3ER2KZAC":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},"01M7EWBV37375ZCWHN3ER2KZAC","waf-pro",null,"Deploy and operate web application firewalls — policy tuning, bot management, and virtual patching done right.","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-waf-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: waf-pro\ndescription: Deploy and operate web application firewalls — policy tuning, bot management, and virtual patching done right.\ncategory: security\n---\n\n## Overview\n\nA WAF sits in front of web applications filtering malicious HTTP traffic: injection attempts, protocol abuse, and automated attacks. It is a valuable compensating control — especially for virtual patching when code fixes take time — but it is not a substitute for secure code. Professional WAF practice is tuning: a well-tuned WAF blocks real attacks with minimal false positives; a default WAF mostly generates tickets.\n\nThis skill covers WAF deployment modes, rule tuning, bot management, and the honest accounting of what a WAF can and cannot do.\n\nA WAF is a compensating control with an expiration date on every rule — it buys time for real fixes and filters the internet's background radiation of automated attacks. Respect both halves of that: it genuinely reduces noise and buys patching windows, and it genuinely cannot fix your application's broken authorization. Report its value honestly and retire its rules deliberately.\n\n## When to use\n\n- Protecting internet-facing web apps and APIs, especially legacy apps that are hard to patch.\n- Virtual patching: blocking exploitation of a known vulnerability while the code fix is developed.\n- Reducing automated abuse: credential stuffing, scraping, vulnerability scanning.\n- Meeting compliance expectations for application-layer protection.\n\n## Core concepts\n\n- **Deployment modes:** reverse-proxy\u002Finline (sees and can block everything; adds latency\u002Ffailure domain), CDN\u002Fcloud WAF (easy, scales, less control), host-based\u002Fagent (close to the app). Choose by architecture and risk.\n- **Positive vs negative security models:** negative (blocklist known-bad) is the default and needs constant updates; positive (allowlist expected behavior) is stronger but harder to maintain — best for stable, well-understood APIs.\n- **Virtual patching:** writing a WAF rule to block a specific CVE's exploitation pattern buys time for the real fix. It is a bandage with an expiry date: track it and remove when patched.\n- **Tuning lifecycle:** log\u002Fmonitor mode → analyze false positives → tune → enforce → continuous review. Enforcing an untuned ruleset breaks legitimate users.\n- **Bot management:** distinguishing good bots (search, monitoring) from bad (stuffing, scraping, scalping) via behavioral signals and challenge layers — separate from but adjacent to WAF.\n- **What a WAF cannot do:** fix broken access control, business-logic flaws, or insecure design. It sees HTTP, not application semantics. Pair with secure code and testing.\n\n- **API schema enforcement.** For well-defined APIs, positive-security validation against the OpenAPI schema blocks malformed and unexpected requests more reliably than generic attack signatures.\n- **Layered rate limiting.** WAF-level, application-level, and account-level rate limits together handle volumetric abuse, targeted stuffing, and business-logic abuse respectively.\n- **Geographic and reputation policy.** Geo-blocking and IP-reputation feeds are blunt instruments — use them as risk signals in layered policy, not as sole controls.\n\n## Practical workflow\n\n1. **Inventory and prioritize:** which apps\u002FAPIs get WAF protection first (internet-facing, sensitive data, known-vulnerable). Define success: block rate on attack traffic, FP rate near zero on legitimate traffic.\n2. **Deploy in monitor mode:** full ruleset logging, no blocking, for 1–2 weeks of real traffic. Baseline legitimate patterns, especially for APIs (unusual but valid clients break naive rules).\n3. **Tune:** disable rules that fire on legitimate traffic (document why); tighten rules for your actual threat profile; build custom rules for app-specific abuse patterns.\n4. **Enforce gradually:** switch to block mode per application, watching error rates and support tickets like a hawk for the first 48 hours. Keep a fast rollback\u002Fdisable path.\n5. **Operate:** virtual-patch critical CVEs with tracked expiry; review blocked-traffic samples weekly for new attack patterns; tune quarterly or after app changes.\n6. **Measure honestly:** report blocked attacks *and* false-positive rate *and* coverage gaps (what the WAF cannot see). Feed bypass patterns back to developers as code-fix tickets.\n\n### WAF checklist\n\n- [ ] Deployment mode chosen; failure\u002Flatency impact assessed\n- [ ] Monitor-mode baseline completed before enforcement\n- [ ] Rules tuned to app traffic; FP rate measured and acceptable\n- [ ] Fast disable\u002Frollback path tested\n- [ ] Virtual patches tracked with expiry tied to code-fix dates\n- [ ] Bot policy defined (allowlist good bots, challenge bad)\n- [ ] Logging to SIEM; blocked-traffic review cadence set\n\n### Sustaining the practice\n\n- Review blocked-traffic samples weekly for emerging attack patterns\n- Re-tune after every application release that changes request shapes\n- Track virtual-patch age; escalate code fixes past their committed dates\n- Benchmark false-positive rate per application monthly\n\n### Metrics that prove it works\n\n- Block rate on confirmed malicious traffic samples\n- False-positive rate on legitimate traffic (per application)\n- Age of oldest virtual patch without a code fix (should shrink)\n- Bypass reports received and converted to code fixes\n\n## Common pitfalls\n\n- **Enforcing on day one.** Untuned blocking breaks legitimate traffic and gets the WAF blamed and bypassed. Monitor first.\n- **Treating WAF as the fix.** Virtual patches without code-fix tickets are permanent bandages. Every virtual patch needs a real fix date.\n- **Ignoring APIs.** API traffic patterns differ from browser traffic; generic rulesets cause false positives on valid API clients. Tune per API.\n- **Set-and-forget.** Apps change, attacks change. Untended WAFs drift into irrelevance or false-positive hell.\n- **No rollback plan.** When the WAF breaks checkout on Black Friday, you need a tested 60-second disable path, not a change ticket.\n- **Overclaiming.** \"WAF protected\" does not mean \"secure.\" Be honest about the control's limits in risk reporting.\n- **WAF in front of the CDN but not the origin.** Attackers who discover the origin IP bypass the WAF entirely. Restrict origin access to the WAF\u002FCDN only.\n- **Rate limiting left to the WAF alone.** Credential stuffing and scraping need layered controls — rate limiting, bot management, and account-level defenses together.\n- **WAF logs nobody reads.** Block events are threat intelligence about who is probing you and how. Feed them to the SOC and review trends.\n- **SSL\u002FTLS termination gaps.** If the WAF cannot see decrypted traffic properly, it is filtering blind. Ensure correct certificate deployment and cipher support.\n","## Overview\n\nA WAF sits in front of web applications filtering malicious HTTP traffic: injection attempts, protocol abuse, and automated attacks. It is a valuable compensating control — especially for virtual patching when code fixes take time — but it is not a substitute for secure code. Professional WAF practice is tuning: a well-tuned WAF blocks real attacks with minimal false positives; a default WAF mostly generates tickets.\n\nThis skill covers WAF deployment modes, rule tuning, bot management, and the honest accounting of what a WAF can and cannot do.\n\nA WAF is a compensating control with an expiration date on every rule — it buys time for real fixes and filters the internet's background radiation of automated attacks. Respect both halves of that: it genuinely reduces noise and buys patching windows, and it genuinely cannot fix your application's broken authorization. Report its value honestly and retire its rules deliberately.\n\n## When to use\n\n- Protecting internet-facing web apps and APIs, especially legacy apps that are hard to patch.\n- Virtual patching: blocking exploitation of a known vulnerability while the code fix is developed.\n- Reducing automated abuse: credential stuffing, scraping, vulnerability scanning.\n- Meeting compliance expectations for application-layer protection.\n\n## Core concepts\n\n- **Deployment modes:** reverse-proxy\u002Finline (sees and can block everything; adds latency\u002Ffailure domain), CDN\u002Fcloud WAF (easy, scales, less control), host-based\u002Fagent (close to the app). Choose by architecture and risk.\n- **Positive vs negative security models:** negative (blocklist known-bad) is the default and needs constant updates; positive (allowlist expected behavior) is stronger but harder to maintain — best for stable, well-understood APIs.\n- **Virtual patching:** writing a WAF rule to block a specific CVE's exploitation pattern buys time for the real fix. It is a bandage with an expiry date: track it and remove when patched.\n- **Tuning lifecycle:** log\u002Fmonitor mode → analyze false positives → tune → enforce → continuous review. Enforcing an untuned ruleset breaks legitimate users.\n- **Bot management:** distinguishing good bots (search, monitoring) from bad (stuffing, scraping, scalping) via behavioral signals and challenge layers — separate from but adjacent to WAF.\n- **What a WAF cannot do:** fix broken access control, business-logic flaws, or insecure design. It sees HTTP, not application semantics. Pair with secure code and testing.\n\n- **API schema enforcement.** For well-defined APIs, positive-security validation against the OpenAPI schema blocks malformed and unexpected requests more reliably than generic attack signatures.\n- **Layered rate limiting.** WAF-level, application-level, and account-level rate limits together handle volumetric abuse, targeted stuffing, and business-logic abuse respectively.\n- **Geographic and reputation policy.** Geo-blocking and IP-reputation feeds are blunt instruments — use them as risk signals in layered policy, not as sole controls.\n\n## Practical workflow\n\n1. **Inventory and prioritize:** which apps\u002FAPIs get WAF protection first (internet-facing, sensitive data, known-vulnerable). Define success: block rate on attack traffic, FP rate near zero on legitimate traffic.\n2. **Deploy in monitor mode:** full ruleset logging, no blocking, for 1–2 weeks of real traffic. Baseline legitimate patterns, especially for APIs (unusual but valid clients break naive rules).\n3. **Tune:** disable rules that fire on legitimate traffic (document why); tighten rules for your actual threat profile; build custom rules for app-specific abuse patterns.\n4. **Enforce gradually:** switch to block mode per application, watching error rates and support tickets like a hawk for the first 48 hours. Keep a fast rollback\u002Fdisable path.\n5. **Operate:** virtual-patch critical CVEs with tracked expiry; review blocked-traffic samples weekly for new attack patterns; tune quarterly or after app changes.\n6. **Measure honestly:** report blocked attacks *and* false-positive rate *and* coverage gaps (what the WAF cannot see). Feed bypass patterns back to developers as code-fix tickets.\n\n### WAF checklist\n\n- [ ] Deployment mode chosen; failure\u002Flatency impact assessed\n- [ ] Monitor-mode baseline completed before enforcement\n- [ ] Rules tuned to app traffic; FP rate measured and acceptable\n- [ ] Fast disable\u002Frollback path tested\n- [ ] Virtual patches tracked with expiry tied to code-fix dates\n- [ ] Bot policy defined (allowlist good bots, challenge bad)\n- [ ] Logging to SIEM; blocked-traffic review cadence set\n\n### Sustaining the practice\n\n- Review blocked-traffic samples weekly for emerging attack patterns\n- Re-tune after every application release that changes request shapes\n- Track virtual-patch age; escalate code fixes past their committed dates\n- Benchmark false-positive rate per application monthly\n\n### Metrics that prove it works\n\n- Block rate on confirmed malicious traffic samples\n- False-positive rate on legitimate traffic (per application)\n- Age of oldest virtual patch without a code fix (should shrink)\n- Bypass reports received and converted to code fixes\n\n## Common pitfalls\n\n- **Enforcing on day one.** Untuned blocking breaks legitimate traffic and gets the WAF blamed and bypassed. Monitor first.\n- **Treating WAF as the fix.** Virtual patches without code-fix tickets are permanent bandages. Every virtual patch needs a real fix date.\n- **Ignoring APIs.** API traffic patterns differ from browser traffic; generic rulesets cause false positives on valid API clients. Tune per API.\n- **Set-and-forget.** Apps change, attacks change. Untended WAFs drift into irrelevance or false-positive hell.\n- **No rollback plan.** When the WAF breaks checkout on Black Friday, you need a tested 60-second disable path, not a change ticket.\n- **Overclaiming.** \"WAF protected\" does not mean \"secure.\" Be honest about the control's limits in risk reporting.\n- **WAF in front of the CDN but not the origin.** Attackers who discover the origin IP bypass the WAF entirely. Restrict origin access to the WAF\u002FCDN only.\n- **Rate limiting left to the WAF alone.** Credential stuffing and scraping need layered controls — rate limiting, bot management, and account-level defenses together.\n- **WAF logs nobody reads.** Block events are threat intelligence about who is probing you and how. Feed them to the SOC and review trends.\n- **SSL\u002FTLS termination gaps.** If the WAF cannot see decrypted traffic properly, it is filtering blind. Ensure correct certificate deployment and cipher support.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-waf-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 waf-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill waf-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill waf-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-waf-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",[],[]]