[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBFX5WGSYCV4027DF73FWM":3,"skill-same:01M7FBFX5WGSYCV4027DF73FWM":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},"01M7FBFX5WGSYCV4027DF73FWM","service-level-management",null,"Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.","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\u002Fservice-level-management\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: service-level-management\ndescription: Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.\n---\n\n# Service level management\n\nA service level is a promise with a number attached. The number is the easy part; choosing what to\nmeasure is where these go wrong.\n\n## Measure what the customer feels\n\nThe characteristic failure is a service meeting every target while customers are angry. It happens\nwhen the measure is chosen for availability of data rather than relevance:\n\n- **Uptime that excludes degraded operation.** Technically up and unusably slow is down.\n- **Response time instead of resolution time.** An instant acknowledgment that resolves nothing\n  measures the autoresponder.\n- **Averages instead of percentiles.** A mean hides the tail, and the tail is who complains. Commit\n  at p95 or p99, not the mean.\n- **Measurement from inside your own perimeter**, which excludes the part of the path the customer\n  actually traverses.\n\n## Set targets you would fund\n\nA target is a spending decision. Each added nine costs disproportionately more than the last, so the\nquestion is never \"what would be good?\" but \"what is the gap worth to the customer, and does it\nexceed what closing it costs?\"\n\nSet the internal objective tighter than the external commitment. The gap between them is your\nwarning margin; without it, the first thing you learn about a breach is the breach.\n\n## Write them so both sides can tell\n\nAn unmeasurable clause is a future dispute. Every service level needs: what is measured, where it is\nmeasured from, how it is calculated, what is excluded, over what window, and what happens when it is\nmissed.\n\nExclusions are the substance — planned maintenance, force majeure, customer-caused failures,\ndependencies outside your control. Vague exclusions get read narrowly when it matters. For anything\nwith contractual teeth, `legal-risk:contract-review` owns the remedy language; this skill owns\nwhether the number is achievable.\n\n## When you breach\n\nSay so before the customer does. A breach reported by the provider with a cause and a fix costs far\nless trust than one the customer discovers and raises.\n\nThen separate the incident from the pattern. One breach is an incident, handled by\n`customer-experience:escalation-management`. Repeated breaches of the same target mean the target was\nnever fundable — renegotiate it honestly rather than continuing to miss it.\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## Never\n\n- Commit to a level you have not measured yourself achieving for a sustained period.\n- Report availability on a mean when the customer experiences the tail.\n- Agree an SLA whose exclusions are undefined.\n- Let a target stand that you have missed repeatedly without either funding it or renegotiating it.\n","# Service level management\n\nA service level is a promise with a number attached. The number is the easy part; choosing what to\nmeasure is where these go wrong.\n\n## Measure what the customer feels\n\nThe characteristic failure is a service meeting every target while customers are angry. It happens\nwhen the measure is chosen for availability of data rather than relevance:\n\n- **Uptime that excludes degraded operation.** Technically up and unusably slow is down.\n- **Response time instead of resolution time.** An instant acknowledgment that resolves nothing\n  measures the autoresponder.\n- **Averages instead of percentiles.** A mean hides the tail, and the tail is who complains. Commit\n  at p95 or p99, not the mean.\n- **Measurement from inside your own perimeter**, which excludes the part of the path the customer\n  actually traverses.\n\n## Set targets you would fund\n\nA target is a spending decision. Each added nine costs disproportionately more than the last, so the\nquestion is never \"what would be good?\" but \"what is the gap worth to the customer, and does it\nexceed what closing it costs?\"\n\nSet the internal objective tighter than the external commitment. The gap between them is your\nwarning margin; without it, the first thing you learn about a breach is the breach.\n\n## Write them so both sides can tell\n\nAn unmeasurable clause is a future dispute. Every service level needs: what is measured, where it is\nmeasured from, how it is calculated, what is excluded, over what window, and what happens when it is\nmissed.\n\nExclusions are the substance — planned maintenance, force majeure, customer-caused failures,\ndependencies outside your control. Vague exclusions get read narrowly when it matters. For anything\nwith contractual teeth, `legal-risk:contract-review` owns the remedy language; this skill owns\nwhether the number is achievable.\n\n## When you breach\n\nSay so before the customer does. A breach reported by the provider with a cause and a fix costs far\nless trust than one the customer discovers and raises.\n\nThen separate the incident from the pattern. One breach is an incident, handled by\n`customer-experience:escalation-management`. Repeated breaches of the same target mean the target was\nnever fundable — renegotiate it honestly rather than continuing to miss it.\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## Never\n\n- Commit to a level you have not measured yourself achieving for a sustained period.\n- Report availability on a mean when the customer experiences the tail.\n- Agree an SLA whose exclusions are undefined.\n- Let a target stand that you have missed repeatedly without either funding it or renegotiating it.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fservice-level-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 service-level-management",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill service-level-management",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill service-level-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fservice-level-management\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",992,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fservice-level-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",[],[]]