[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVT87YRHV0K4125E1PHTAD":3,"skill-same:01M7EVT87YRHV0K4125E1PHTAD":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},"01M7EVT87YRHV0K4125E1PHTAD","salary-negotiator",null,"Prepare and execute compensation negotiations with market data, scripts, and counter-offer strategy.","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-salary-negotiator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: salary-negotiator\ndescription: Prepare and execute compensation negotiations with market data, scripts, and counter-offer strategy.\ncategory: career\n---\n\n## Overview\n\nAlmost every offer is negotiable, and the first number is rarely the last. Yet\nmost candidates\naccept the first offer because negotiating feels confrontational. This skill\nreframes negotiation as\ncollaborative problem-solving: you and the employer both want you to sign, and\nthe only question is\nthe package. It covers research, anchoring, scripts for every stage, and the\ncounter-offer trap.\n\n## When to use\n\n- Evaluating a written offer and deciding whether\u002Fhow to negotiate\n\n- Answering \"what are your salary expectations?\" early in a process\n\n- Juggling multiple offers for leverage\n\n- Negotiating a raise or promotion internally\n\n- Handling exploding offers and deadlines\n\n## Core concepts\n\n- - - **Never give the first number if you can avoid it.** \"What's your expected\n  salary?\" → \"I'd like\n  to understand the full scope first — what's the budgeted range for this role?\"\nWhoever anchors\n  first sets the frame.\n- - - **Negotiate the total package.** Base, bonus, equity\u002FRSUs, sign-on,\n  relocation, remote\n  flexibility, start date, title, review timeline. A \"no\" on base often becomes\na \"yes\" on sign-on\n  or equity.\n- - - **Market data is your leverage.** Levels.fyi, Glassdoor, Pave, peer\n  conversations — come with a\n  range, not a feeling. \"Based on market data for this role in this market, I'm\ntargeting X-Y.\"\n- - - **Silence is a tactic.** After you state your ask, stop talking. The urge\n  to fill silence with\n  concessions is the most expensive habit in negotiation.\n- - - **Get it in writing.** Verbal promises evaporate. Every agreed term —\n  including start dates and\n  review timelines — goes into the written offer before you sign.\n- - - **The walk-away number.** Decide your minimum acceptable package before\n  negotiating. Without it,\n  you'll rationalize a bad deal in the moment.\n\n## Practical workflow\n\n1. 1. 1. **Research.** Gather 3+ data points for the role, level, and market.\n   Note the full range, not\n   just the median — you negotiate against the top of the band, not the middle.\n2. 2. 2. **Set your numbers.** Three figures: ideal (ask), target (happy to\n   sign), walk-away (decline).\n   Keep the walk-away private; it's your discipline tool.\n3. 3. 3. **Deflect early salary questions.** Use the range-request script. If\n   forced, give a wide,\n   research-backed range with the top at your ideal — never a single number,\nnever your current\n   salary (it's irrelevant and often illegal to ask for).\n4. 4. 4. **Evaluate the written offer.** Score each component against your\n   numbers. Identify the 2-3\n   levers with the most upside (usually base + sign-on + equity).\n5. 5. 5. **Make the counter.** One consolidated ask, framed collaboratively:\n   \"I'm excited about the\n   role and the team. Based on my research and the scope, I'd be able to sign at\n[X base, Y\n   sign-on]. Can we get there?\" Then silence.\n6. 6. 6. **Handle the pushback.** Expect \"this is our best offer\" (often not\n   true), \"the band doesn't\n   allow it\" (ask about sign-on\u002Fequity, which often sit outside bands), or a\nsplit-the-difference.\n   Respond to each calmly, one round at a time — 2-3 rounds is normal.\n7. 7. 7. **Close cleanly.** Once terms are agreed, confirm in writing, thank\n   everyone, and stop\n   negotiating. Post-acceptance renegotiation burns bridges.\n\n## Common pitfalls\n\n- - - **Accepting the first offer.** The first offer is a starting point by\n  design. A polite counter\n  almost never rescinds an offer — that fear is the employer's best negotiating\ntool.\n- - - **Negotiating against yourself.** \"I was thinking maybe around X, but I'm\n  flexible...\" — you've\n  just lowered your own anchor. State the ask and stop.\n- - - **Revealing your current salary.** It anchors you to your past, not your\n  market value. Deflect:\n  \"I'd prefer to focus on the market rate for this role.\"\n- - - **Only negotiating base.** Candidates leave tens of thousands on the table\n  ignoring sign-on\n  bonuses, equity refreshers, and remote stipends.\n- - - **Using a fake competing offer.** Lies get discovered and destroy trust.\n  Real leverage only —\n  even \"I'm in late stages elsewhere\" must be true.\n- - - **Exploding-offer panic.** \"Sign by Friday or it's gone\" is usually\n  negotiable: \"I'm very\n  interested — I need until [date] to make a thoughtful decision.\" Employers who\ntruly want you will\n  wait a few days.\n","## Overview\n\nAlmost every offer is negotiable, and the first number is rarely the last. Yet\nmost candidates\naccept the first offer because negotiating feels confrontational. This skill\nreframes negotiation as\ncollaborative problem-solving: you and the employer both want you to sign, and\nthe only question is\nthe package. It covers research, anchoring, scripts for every stage, and the\ncounter-offer trap.\n\n## When to use\n\n- Evaluating a written offer and deciding whether\u002Fhow to negotiate\n\n- Answering \"what are your salary expectations?\" early in a process\n\n- Juggling multiple offers for leverage\n\n- Negotiating a raise or promotion internally\n\n- Handling exploding offers and deadlines\n\n## Core concepts\n\n- - - **Never give the first number if you can avoid it.** \"What's your expected\n  salary?\" → \"I'd like\n  to understand the full scope first — what's the budgeted range for this role?\"\nWhoever anchors\n  first sets the frame.\n- - - **Negotiate the total package.** Base, bonus, equity\u002FRSUs, sign-on,\n  relocation, remote\n  flexibility, start date, title, review timeline. A \"no\" on base often becomes\na \"yes\" on sign-on\n  or equity.\n- - - **Market data is your leverage.** Levels.fyi, Glassdoor, Pave, peer\n  conversations — come with a\n  range, not a feeling. \"Based on market data for this role in this market, I'm\ntargeting X-Y.\"\n- - - **Silence is a tactic.** After you state your ask, stop talking. The urge\n  to fill silence with\n  concessions is the most expensive habit in negotiation.\n- - - **Get it in writing.** Verbal promises evaporate. Every agreed term —\n  including start dates and\n  review timelines — goes into the written offer before you sign.\n- - - **The walk-away number.** Decide your minimum acceptable package before\n  negotiating. Without it,\n  you'll rationalize a bad deal in the moment.\n\n## Practical workflow\n\n1. 1. 1. **Research.** Gather 3+ data points for the role, level, and market.\n   Note the full range, not\n   just the median — you negotiate against the top of the band, not the middle.\n2. 2. 2. **Set your numbers.** Three figures: ideal (ask), target (happy to\n   sign), walk-away (decline).\n   Keep the walk-away private; it's your discipline tool.\n3. 3. 3. **Deflect early salary questions.** Use the range-request script. If\n   forced, give a wide,\n   research-backed range with the top at your ideal — never a single number,\nnever your current\n   salary (it's irrelevant and often illegal to ask for).\n4. 4. 4. **Evaluate the written offer.** Score each component against your\n   numbers. Identify the 2-3\n   levers with the most upside (usually base + sign-on + equity).\n5. 5. 5. **Make the counter.** One consolidated ask, framed collaboratively:\n   \"I'm excited about the\n   role and the team. Based on my research and the scope, I'd be able to sign at\n[X base, Y\n   sign-on]. Can we get there?\" Then silence.\n6. 6. 6. **Handle the pushback.** Expect \"this is our best offer\" (often not\n   true), \"the band doesn't\n   allow it\" (ask about sign-on\u002Fequity, which often sit outside bands), or a\nsplit-the-difference.\n   Respond to each calmly, one round at a time — 2-3 rounds is normal.\n7. 7. 7. **Close cleanly.** Once terms are agreed, confirm in writing, thank\n   everyone, and stop\n   negotiating. Post-acceptance renegotiation burns bridges.\n\n## Common pitfalls\n\n- - - **Accepting the first offer.** The first offer is a starting point by\n  design. A polite counter\n  almost never rescinds an offer — that fear is the employer's best negotiating\ntool.\n- - - **Negotiating against yourself.** \"I was thinking maybe around X, but I'm\n  flexible...\" — you've\n  just lowered your own anchor. State the ask and stop.\n- - - **Revealing your current salary.** It anchors you to your past, not your\n  market value. Deflect:\n  \"I'd prefer to focus on the market rate for this role.\"\n- - - **Only negotiating base.** Candidates leave tens of thousands on the table\n  ignoring sign-on\n  bonuses, equity refreshers, and remote stipends.\n- - - **Using a fake competing offer.** Lies get discovered and destroy trust.\n  Real leverage only —\n  even \"I'm in late stages elsewhere\" must be true.\n- - - **Exploding-offer panic.** \"Sign by Friday or it's gone\" is usually\n  negotiable: \"I'm very\n  interested — I need until [date] to make a thoughtful decision.\" Employers who\ntruly want you will\n  wait a few days.\n",{"name":5,"category":24,"description":7},"career","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-salary-negotiator",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 salary-negotiator",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill salary-negotiator",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill salary-negotiator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-salary-negotiator\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",[],[]]