[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMEEWZ2YBQCC4SAFFA7RBK":3,"skill-same:01M7EMEEWZ2YBQCC4SAFFA7RBK":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},"01M7EMEEWZ2YBQCC4SAFFA7RBK","bug-bounty-hunter",null,"Run an effective bug bounty program — scope design, triage, researcher relations, and remediation workflows.","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-bug-bounty-hunter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bug-bounty-hunter\ndescription: Run an effective bug bounty program — scope design, triage, researcher relations, and remediation workflows.\ncategory: security\n---\n\n## Overview\n\nA bug bounty program pays independent researchers for responsibly disclosed vulnerabilities in your systems. Done well, it is continuous, adversarial testing at a scale no internal team can match. Done badly, it is a flood of duplicates, out-of-scope reports, and burned researcher goodwill.\n\nThis skill is written for **program owners** (defenders running the program) — scoping, triage, payouts, and turning reports into fixes. It covers only authorized, in-scope testing methodology at the standard published level: recon, testing within the published scope, and quality reporting. No exploit code.\n\nA bounty program is a marketplace: researchers sell attention and skill, you buy findings with money, responsiveness, and respect. Programs that thrive treat researchers as an extension of the security team — fast triage, fair pay, technical feedback, and public credit where wanted. Programs that treat them as ticket-generators get what they pay for.\n\n## When to use\n\n- Launching a private or public bounty program (start private, invite-only).\n- Triaging incoming reports quickly and fairly.\n- Setting bounty tables, safe harbor language, and scope that attracts good researchers.\n- Integrating bounty findings into your SDLC so reports become fixes, not backlog.\n- Deciding whether your org is mature enough for bounty (you need vuln-management first).\n\n## Core concepts\n\n- **Safe harbor:** an explicit commitment not to pursue legal action for good-faith, in-scope research. Without it, good researchers stay away.\n- **Scope is the product:** clear in-scope assets, explicit out-of-scope items, and testing rules. Vague scope produces vague reports and disputes.\n- **Private before public:** start with a small vetted researcher pool, tune triage, then open up. Public launch with broken triage is reputational damage.\n- **Triage SLA:** acknowledge in 1–2 days, first assessment in under a week. Slow triage kills researcher motivation faster than low payouts.\n- **Duplicates are data:** high duplicate rates on an asset mean your vuln-management is behind, not that researchers are sloppy. Fix the root cause.\n- **The report is the deliverable:** severity, reproduction steps, impact in your context, suggested fix. Reward quality reports, not just criticals.\n\n- **Signal over volume.** Ten high-quality researchers outperform a thousand drive-by submitters. Invest in relationships with proven researchers: private scopes, bonuses, early access.\n- **Root-cause bounties.** Consider bonus multipliers for reports that identify systemic issues or come with suggested fixes — it shifts incentives from bugs to classes.\n- **Disclosure policy.** A clear coordinated-disclosure policy with timelines builds researcher trust and turns fixes into positive publicity.\n\n## Practical workflow\n\n1. **Readiness check:** do you have asset inventory, a vuln-management process with SLAs, and someone to own triage? If not, fix that first — bounty amplifies process gaps.\n2. **Design the program:** define scope (start narrow: one app or API), rules of engagement, out-of-scope list, safe harbor text, bounty table by severity, and response SLAs. Publish it all.\n3. **Launch private:** invite 20–50 researchers, run 4–8 weeks, tune scope and triage on real volume.\n4. **Triage pipeline:** intake → deduplicate → validate (reproduce in-house) → severity using your rubric → route to the owning team with a fix SLA → verify the fix → pay → disclose (if policy allows).\n5. **Researcher relations:** communicate decisions with reasons, pay promptly, give feedback on report quality, invite strong researchers to private scopes. Reputation compounds.\n6. **Close the loop:** track bounty findings in the same system as pentest\u002Fscanner findings; measure time-to-fix and recurrence. Feed common bug classes into secure-coding training and SAST rules.\n7. **Go public when ready:** triage holding up, fix SLAs holding up, scope stable. Announce with a clear brief and realistic expectations.\n\n### Bounty brief essentials\n\n- In-scope assets (exact domains, apps, APIs, mobile builds)\n- Out-of-scope (third-party services, DoS, spam, social engineering unless invited)\n- Rules: no data exfiltration beyond proof, no degrading service, stop at PII\n- Safe harbor statement\n- Severity rubric and payout table\n- Response and payout SLAs\n\n### Sustaining the practice\n\n- Review the bounty table annually against market rates and program data\n- Publish anonymized program stats to attract quality researchers\n- Rotate fresh private scopes to retain top researchers\n- Audit triage quality by sampling closed reports quarterly\n\n### Metrics that prove it works\n\n- Median time to first triage response and to severity decision\n- Time from validation to fix, by severity\n- Valid-report rate (signal quality of the program)\n- Researcher retention: % of top researchers still active after 6 months\n\n## Common pitfalls\n\n- **Launching public on day one.** You will drown. Private first, always.\n- **Scope ambiguity.** \"Our main site\" is not scope. Enumerate assets explicitly.\n- **Slow or silent triage.** Researchers talk. A program known for ghosting gets low-effort reports.\n- **Paying late or disputing fairly-earned bounties.** Nothing kills a program faster.\n- **Treating bounty as your vuln-management.** It is a complement to scanning, pentests, and code review — not a replacement.\n- **Ignoring duplicates as signal.** Ten duplicate IDOR reports = your access-control testing is broken. Fix the class.\n- **No fix verification.** Paying without verifying the fix teaches researchers (and your team) that closure does not matter.\n- **Scope that excludes everything interesting.** Researchers invest where scope rewards them. Overly narrow scope gets low-effort reports on the allowed sliver.\n- **Inconsistent severity calls.** Publish your rubric with worked examples. Nothing erodes trust like two identical bugs paid differently.\n- **Scope creep by researcher pressure.** Expanding scope reactively to appease complaints creates inconsistency. Change scope deliberately, announce clearly.\n- **Ignoring the long tail of low-severity reports.** Individually minor, in aggregate they map your attack surface. Mine them for patterns quarterly.\n","## Overview\n\nA bug bounty program pays independent researchers for responsibly disclosed vulnerabilities in your systems. Done well, it is continuous, adversarial testing at a scale no internal team can match. Done badly, it is a flood of duplicates, out-of-scope reports, and burned researcher goodwill.\n\nThis skill is written for **program owners** (defenders running the program) — scoping, triage, payouts, and turning reports into fixes. It covers only authorized, in-scope testing methodology at the standard published level: recon, testing within the published scope, and quality reporting. No exploit code.\n\nA bounty program is a marketplace: researchers sell attention and skill, you buy findings with money, responsiveness, and respect. Programs that thrive treat researchers as an extension of the security team — fast triage, fair pay, technical feedback, and public credit where wanted. Programs that treat them as ticket-generators get what they pay for.\n\n## When to use\n\n- Launching a private or public bounty program (start private, invite-only).\n- Triaging incoming reports quickly and fairly.\n- Setting bounty tables, safe harbor language, and scope that attracts good researchers.\n- Integrating bounty findings into your SDLC so reports become fixes, not backlog.\n- Deciding whether your org is mature enough for bounty (you need vuln-management first).\n\n## Core concepts\n\n- **Safe harbor:** an explicit commitment not to pursue legal action for good-faith, in-scope research. Without it, good researchers stay away.\n- **Scope is the product:** clear in-scope assets, explicit out-of-scope items, and testing rules. Vague scope produces vague reports and disputes.\n- **Private before public:** start with a small vetted researcher pool, tune triage, then open up. Public launch with broken triage is reputational damage.\n- **Triage SLA:** acknowledge in 1–2 days, first assessment in under a week. Slow triage kills researcher motivation faster than low payouts.\n- **Duplicates are data:** high duplicate rates on an asset mean your vuln-management is behind, not that researchers are sloppy. Fix the root cause.\n- **The report is the deliverable:** severity, reproduction steps, impact in your context, suggested fix. Reward quality reports, not just criticals.\n\n- **Signal over volume.** Ten high-quality researchers outperform a thousand drive-by submitters. Invest in relationships with proven researchers: private scopes, bonuses, early access.\n- **Root-cause bounties.** Consider bonus multipliers for reports that identify systemic issues or come with suggested fixes — it shifts incentives from bugs to classes.\n- **Disclosure policy.** A clear coordinated-disclosure policy with timelines builds researcher trust and turns fixes into positive publicity.\n\n## Practical workflow\n\n1. **Readiness check:** do you have asset inventory, a vuln-management process with SLAs, and someone to own triage? If not, fix that first — bounty amplifies process gaps.\n2. **Design the program:** define scope (start narrow: one app or API), rules of engagement, out-of-scope list, safe harbor text, bounty table by severity, and response SLAs. Publish it all.\n3. **Launch private:** invite 20–50 researchers, run 4–8 weeks, tune scope and triage on real volume.\n4. **Triage pipeline:** intake → deduplicate → validate (reproduce in-house) → severity using your rubric → route to the owning team with a fix SLA → verify the fix → pay → disclose (if policy allows).\n5. **Researcher relations:** communicate decisions with reasons, pay promptly, give feedback on report quality, invite strong researchers to private scopes. Reputation compounds.\n6. **Close the loop:** track bounty findings in the same system as pentest\u002Fscanner findings; measure time-to-fix and recurrence. Feed common bug classes into secure-coding training and SAST rules.\n7. **Go public when ready:** triage holding up, fix SLAs holding up, scope stable. Announce with a clear brief and realistic expectations.\n\n### Bounty brief essentials\n\n- In-scope assets (exact domains, apps, APIs, mobile builds)\n- Out-of-scope (third-party services, DoS, spam, social engineering unless invited)\n- Rules: no data exfiltration beyond proof, no degrading service, stop at PII\n- Safe harbor statement\n- Severity rubric and payout table\n- Response and payout SLAs\n\n### Sustaining the practice\n\n- Review the bounty table annually against market rates and program data\n- Publish anonymized program stats to attract quality researchers\n- Rotate fresh private scopes to retain top researchers\n- Audit triage quality by sampling closed reports quarterly\n\n### Metrics that prove it works\n\n- Median time to first triage response and to severity decision\n- Time from validation to fix, by severity\n- Valid-report rate (signal quality of the program)\n- Researcher retention: % of top researchers still active after 6 months\n\n## Common pitfalls\n\n- **Launching public on day one.** You will drown. Private first, always.\n- **Scope ambiguity.** \"Our main site\" is not scope. Enumerate assets explicitly.\n- **Slow or silent triage.** Researchers talk. A program known for ghosting gets low-effort reports.\n- **Paying late or disputing fairly-earned bounties.** Nothing kills a program faster.\n- **Treating bounty as your vuln-management.** It is a complement to scanning, pentests, and code review — not a replacement.\n- **Ignoring duplicates as signal.** Ten duplicate IDOR reports = your access-control testing is broken. Fix the class.\n- **No fix verification.** Paying without verifying the fix teaches researchers (and your team) that closure does not matter.\n- **Scope that excludes everything interesting.** Researchers invest where scope rewards them. Overly narrow scope gets low-effort reports on the allowed sliver.\n- **Inconsistent severity calls.** Publish your rubric with worked examples. Nothing erodes trust like two identical bugs paid differently.\n- **Scope creep by researcher pressure.** Expanding scope reactively to appease complaints creates inconsistency. Change scope deliberately, announce clearly.\n- **Ignoring the long tail of low-severity reports.** Individually minor, in aggregate they map your attack surface. Mine them for patterns quarterly.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-bug-bounty-hunter",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 bug-bounty-hunter",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill bug-bounty-hunter",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill bug-bounty-hunter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-bug-bounty-hunter\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",[],[]]