[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVH2GS6RXKP1ME2X0NH1W7":3,"skill-same:01M7EVH2GS6RXKP1ME2X0NH1W7":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},"01M7EVH2GS6RXKP1ME2X0NH1W7","promotion-case-builder",null,"Assemble a promotion packet with scope evidence, stakeholder support, and level-criteria mapping.","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-promotion-case-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: promotion-case-builder\ndescription: Assemble a promotion packet with scope evidence, stakeholder support, and level-criteria mapping.\ncategory: career\n---\n\n## Overview\n\nPromotions are not rewards for tenure — they are decisions that you are already\noperating at the\nnext level. Most promotion cases fail because they argue \"I deserve it\" instead\nof proving \"I'm\nalready doing it.\" This skill builds a packet that maps your work to the next\nlevel's expectations,\nwith evidence a promotion committee can verify.\n\n## When to use\n\n- Preparing for a promotion cycle (6-12 months out or imminent)\n\n- Writing a promotion packet or self-nomination document\n\n- Deciding whether you're ready to go up for promotion\n\n- Recovering from a denied promotion and planning the next attempt\n\n- Helping a direct report build their case\n\n## Core concepts\n\n- - - **The level rubric is the exam paper.** Get the written expectations for\n  the target level. Your\n  packet is an answer key: every criterion gets 1-2 pieces of evidence. No\nrubric, no case.\n- - - **Scope is the currency.** Promotions hinge on expanded scope: larger\n  projects, broader\n  influence, mentoring others, driving decisions beyond your team. Show the\ndelta from your current\n  level, not just good performance at it.\n- - - **Sustained, not spiky.** One heroic quarter rarely suffices. Committees\n  look for 2-3 quarters\n  of consistent next-level performance. Start building the case early.\n- - - **Sponsors, not just supporters.** You need people with influence in the\n  room saying your name.\n  Identify 2-3 senior stakeholders whose work you materially improved, and make\nsure they know your\n  promotion is on the table.\n- - - **The \"already operating\" test.** For each next-level expectation, ask:\n  \"if I were already at\n  this level, what would I be doing differently?\" The gap between that answer\nand your current work\n  is your project list.\n- - - **Denial is data.** If denied, get the specific gaps in writing within a\n  week. Vague feedback\n  (\"need more visibility\") is unactionable — push for the concrete behaviors\nexpected.\n\n## Practical workflow\n\n1. 1. 1. **Read the rubric.** Obtain the level definitions for current and\n   target level. Highlight the\n   4-6 differentiators — these are your packet's section headers.\n2. 2. 2. **Run the gap analysis.** For each differentiator: evidence you have,\n   evidence you lack, and a\n   plan to close the gap in the next 1-2 quarters. Be brutally honest;\ncommittees will be.\n3. 3. 3. **Build the evidence file.** For each criterion: project name, your\n   role, scope indicators\n   (team size, users, revenue, cross-team reach), outcomes with metrics, and\nstakeholder quotes. Aim\n   for 2+ evidence items per criterion.\n4. 4. 4. **Draft the packet narrative.** Executive summary (why now, in 5\n   lines), then\n   criterion-by-criterion evidence, then growth areas with mitigation. Keep it\nscannable —\n   committees read dozens.\n5. 5. 5. **Line up sponsors.** Share the packet with your manager first, then\n   brief 2-3 senior\n   stakeholders. Ask specifically: \"would you be comfortable speaking to my\nscope on X in the\n   calibration?\" Make it easy with a one-pager.\n6. 6. 6. **Pre-mortem with your manager.** Ask: \"what would make this case\n   fail?\" Address every\n   objection before the packet is submitted, not after.\n7. 7. 7. **Plan the timeline.** Work backwards from the promotion cycle: packet\n   draft, sponsor\n   briefings, manager sign-off, submission. Build in 2-3 weeks of buffer for\nrevisions.\n\n## Common pitfalls\n\n- - - **Arguing tenure.** \"I've been here 3 years\" is not a criterion at any\n  level. Committees promote\n  on demonstrated scope, not patience.\n- - - **Confusing performance with level.** Exceeding expectations at your\n  current level proves you're\n  great at your level — not that you're operating at the next one. The packet\nmust show next-level\n  behaviors.\n- - - **No sponsor in the room.** The best packet in the world dies if nobody\n  advocates for it in\n  calibration. Politics is part of the process; engage with it deliberately.\n- - - **Surprising your manager.** If your manager first hears about your\n  promotion ambitions when the\n  packet lands, you've already lost. Align 2+ quarters ahead.\n- - - **Thin evidence on influence.** Individual output is table stakes. Next\n  levels require evidence\n  you moved others: mentored, unblocked, aligned, decided.\n- - - **Giving up after one denial.** Most promotions take 2 cycles. Treat\n  denial as a detailed\n  requirements doc for the next attempt — get the gaps in writing and execute.\n","## Overview\n\nPromotions are not rewards for tenure — they are decisions that you are already\noperating at the\nnext level. Most promotion cases fail because they argue \"I deserve it\" instead\nof proving \"I'm\nalready doing it.\" This skill builds a packet that maps your work to the next\nlevel's expectations,\nwith evidence a promotion committee can verify.\n\n## When to use\n\n- Preparing for a promotion cycle (6-12 months out or imminent)\n\n- Writing a promotion packet or self-nomination document\n\n- Deciding whether you're ready to go up for promotion\n\n- Recovering from a denied promotion and planning the next attempt\n\n- Helping a direct report build their case\n\n## Core concepts\n\n- - - **The level rubric is the exam paper.** Get the written expectations for\n  the target level. Your\n  packet is an answer key: every criterion gets 1-2 pieces of evidence. No\nrubric, no case.\n- - - **Scope is the currency.** Promotions hinge on expanded scope: larger\n  projects, broader\n  influence, mentoring others, driving decisions beyond your team. Show the\ndelta from your current\n  level, not just good performance at it.\n- - - **Sustained, not spiky.** One heroic quarter rarely suffices. Committees\n  look for 2-3 quarters\n  of consistent next-level performance. Start building the case early.\n- - - **Sponsors, not just supporters.** You need people with influence in the\n  room saying your name.\n  Identify 2-3 senior stakeholders whose work you materially improved, and make\nsure they know your\n  promotion is on the table.\n- - - **The \"already operating\" test.** For each next-level expectation, ask:\n  \"if I were already at\n  this level, what would I be doing differently?\" The gap between that answer\nand your current work\n  is your project list.\n- - - **Denial is data.** If denied, get the specific gaps in writing within a\n  week. Vague feedback\n  (\"need more visibility\") is unactionable — push for the concrete behaviors\nexpected.\n\n## Practical workflow\n\n1. 1. 1. **Read the rubric.** Obtain the level definitions for current and\n   target level. Highlight the\n   4-6 differentiators — these are your packet's section headers.\n2. 2. 2. **Run the gap analysis.** For each differentiator: evidence you have,\n   evidence you lack, and a\n   plan to close the gap in the next 1-2 quarters. Be brutally honest;\ncommittees will be.\n3. 3. 3. **Build the evidence file.** For each criterion: project name, your\n   role, scope indicators\n   (team size, users, revenue, cross-team reach), outcomes with metrics, and\nstakeholder quotes. Aim\n   for 2+ evidence items per criterion.\n4. 4. 4. **Draft the packet narrative.** Executive summary (why now, in 5\n   lines), then\n   criterion-by-criterion evidence, then growth areas with mitigation. Keep it\nscannable —\n   committees read dozens.\n5. 5. 5. **Line up sponsors.** Share the packet with your manager first, then\n   brief 2-3 senior\n   stakeholders. Ask specifically: \"would you be comfortable speaking to my\nscope on X in the\n   calibration?\" Make it easy with a one-pager.\n6. 6. 6. **Pre-mortem with your manager.** Ask: \"what would make this case\n   fail?\" Address every\n   objection before the packet is submitted, not after.\n7. 7. 7. **Plan the timeline.** Work backwards from the promotion cycle: packet\n   draft, sponsor\n   briefings, manager sign-off, submission. Build in 2-3 weeks of buffer for\nrevisions.\n\n## Common pitfalls\n\n- - - **Arguing tenure.** \"I've been here 3 years\" is not a criterion at any\n  level. Committees promote\n  on demonstrated scope, not patience.\n- - - **Confusing performance with level.** Exceeding expectations at your\n  current level proves you're\n  great at your level — not that you're operating at the next one. The packet\nmust show next-level\n  behaviors.\n- - - **No sponsor in the room.** The best packet in the world dies if nobody\n  advocates for it in\n  calibration. Politics is part of the process; engage with it deliberately.\n- - - **Surprising your manager.** If your manager first hears about your\n  promotion ambitions when the\n  packet lands, you've already lost. Align 2+ quarters ahead.\n- - - **Thin evidence on influence.** Individual output is table stakes. Next\n  levels require evidence\n  you moved others: mentored, unblocked, aligned, decided.\n- - - **Giving up after one denial.** Most promotions take 2 cycles. Treat\n  denial as a detailed\n  requirements doc for the next attempt — get the gaps in writing and execute.\n",{"name":5,"category":24,"description":7},"career","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-promotion-case-builder",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 promotion-case-builder",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill promotion-case-builder",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill promotion-case-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-promotion-case-builder\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",[],[]]