[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBAE1P80YN9J6A3YZNF2RF":3,"skill-same:01M7FBAE1P80YN9J6A3YZNF2RF":53},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FBAE1P80YN9J6A3YZNF2RF","performance-management",null,"Headcount HR and management policy for employee performance management systems, review cycles, feedback calibration, and performance improvement plans.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fperformance-management\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: performance-management\ndescription: \"Headcount HR and management policy for employee performance management systems, review cycles, feedback calibration, and performance improvement plans.\"\n---\n\n# Performance management\n\nMost review systems are an expensive annual ritual that surprises nobody and improves nothing. The\nwork happens in the ordinary week; the cycle should record it, not discover it.\n\n**Performance documentation carries legal weight, particularly around termination, discrimination and\naccommodation. Employment law varies by jurisdiction — involve qualified counsel before acting on\nsustained underperformance.**\n\n## Expectations before assessment\n\nNobody can be fairly assessed against a standard they were not given. Expectations need to be\nspecific to the level, written down, and shared before the period rather than produced during review\nas justification.\n\nSeparate two axes deliberately, because conflating them is the most common structural flaw:\n\n- **Outcomes** — what was delivered, which is partly situational.\n- **Behaviors** — how it was done, which is more within the person's control.\n\nSomeone who delivered through a collapsing market and someone who delivered by scorching the earth\naround them are different cases. A single blended rating hides both.\n\n## Feedback in the week, not the quarter\n\nFeedback is useful proportional to its proximity to the event. Specific, immediate, and about the\nwork: what happened, what the effect was, what to do differently.\n\nThe annual cycle should contain nothing new. A review that surprises someone is a reporting failure\nby their manager, and the surprise is the finding.\n\n## Calibration\n\nManagers rate differently — some systematically generously, some harshly — and the differences are\ninvisible until ratings sit side by side. Calibration exists to make comparison possible, not to fit\na distribution.\n\nForced distributions are the failure mode here. On small teams they are statistically meaningless,\nand they reliably destroy exactly the collaboration the values section claims to reward.\n\nCalibrate on evidence: what was delivered, at what level, against what expectation. A rating that\ncannot be defended with an example is a preference.\n\n## Sustained underperformance\n\nAddress it early and directly. Late intervention is worse for everyone, most of all the person, who\nhas been allowed to believe they were fine.\n\nEstablish which it is first, because the remedies do not overlap: unclear expectations, missing\ncapability, a role mismatch, or something outside work. Treating a role mismatch as a capability\nproblem produces a performance plan that fails for reasons nobody named.\n\nWhere a formal plan is warranted it needs specific outcomes, a real timeframe, defined support, and a\nstated consequence. A plan that is only a paper trail for a decision already taken is recognized as\nsuch and does damage well beyond the individual.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\nReview and feedback: Lattice, Culture Amp, 15Five, Leapsome, Workday Talent, and similar.\n\nEngagement measurement usually ships in the same platforms, which is convenient and creates a\ntemptation worth resisting: engagement data and performance data should not be joined at the\nindividual level, because people answer honestly only while that is true.\n\nThe tool cannot fix a process problem. If reviews are late, unspecific, or a surprise to the person\nreceiving them, changing platforms will produce the same reviews on a nicer form.\n\n## Never\n\n- Assess against expectations that were not set in advance.\n- Deliver news in a review that should have been given weeks earlier.\n- Force a distribution on a small team.\n- Start a performance plan without deciding whether the problem is capability or fit.\n","# Performance management\n\nMost review systems are an expensive annual ritual that surprises nobody and improves nothing. The\nwork happens in the ordinary week; the cycle should record it, not discover it.\n\n**Performance documentation carries legal weight, particularly around termination, discrimination and\naccommodation. Employment law varies by jurisdiction — involve qualified counsel before acting on\nsustained underperformance.**\n\n## Expectations before assessment\n\nNobody can be fairly assessed against a standard they were not given. Expectations need to be\nspecific to the level, written down, and shared before the period rather than produced during review\nas justification.\n\nSeparate two axes deliberately, because conflating them is the most common structural flaw:\n\n- **Outcomes** — what was delivered, which is partly situational.\n- **Behaviors** — how it was done, which is more within the person's control.\n\nSomeone who delivered through a collapsing market and someone who delivered by scorching the earth\naround them are different cases. A single blended rating hides both.\n\n## Feedback in the week, not the quarter\n\nFeedback is useful proportional to its proximity to the event. Specific, immediate, and about the\nwork: what happened, what the effect was, what to do differently.\n\nThe annual cycle should contain nothing new. A review that surprises someone is a reporting failure\nby their manager, and the surprise is the finding.\n\n## Calibration\n\nManagers rate differently — some systematically generously, some harshly — and the differences are\ninvisible until ratings sit side by side. Calibration exists to make comparison possible, not to fit\na distribution.\n\nForced distributions are the failure mode here. On small teams they are statistically meaningless,\nand they reliably destroy exactly the collaboration the values section claims to reward.\n\nCalibrate on evidence: what was delivered, at what level, against what expectation. A rating that\ncannot be defended with an example is a preference.\n\n## Sustained underperformance\n\nAddress it early and directly. Late intervention is worse for everyone, most of all the person, who\nhas been allowed to believe they were fine.\n\nEstablish which it is first, because the remedies do not overlap: unclear expectations, missing\ncapability, a role mismatch, or something outside work. Treating a role mismatch as a capability\nproblem produces a performance plan that fails for reasons nobody named.\n\nWhere a formal plan is warranted it needs specific outcomes, a real timeframe, defined support, and a\nstated consequence. A plan that is only a paper trail for a decision already taken is recognized as\nsuch and does damage well beyond the individual.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\nReview and feedback: Lattice, Culture Amp, 15Five, Leapsome, Workday Talent, and similar.\n\nEngagement measurement usually ships in the same platforms, which is convenient and creates a\ntemptation worth resisting: engagement data and performance data should not be joined at the\nindividual level, because people answer honestly only while that is true.\n\nThe tool cannot fix a process problem. If reviews are late, unspecific, or a surprise to the person\nreceiving them, changing platforms will produce the same reviews on a nicer form.\n\n## Never\n\n- Assess against expectations that were not set in advance.\n- Deliver news in a review that should have been given weeks earlier.\n- Force a distribution on a small team.\n- Start a performance plan without deciding whether the problem is capability or fit.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fperformance-management",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill performance-management",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill performance-management",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill performance-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fperformance-management\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",1048,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fperformance-management\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]