[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BHCNFPZ68XGFF591KST5H6":3,"skill-same:01M7BHCNFPZ68XGFF591KST5H6":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7BHCNFPZ68XGFF591KST5H6","incident-triage",null,"Triage customer-reported service incidents when production impact, errors, authentication failures, or integrations are mentioned.","Usefused\u002Fharnest","Usefused","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F291847097?v=4","01M7BHBXMWEB9CR1KXMKQX0017","01M7BHBXNMKR588HF6DESR7TA9",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fexamples\u002Fself-serve\u002Fagents\u002Fhelpdesk\u002Fskills\u002Fincident-triage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: incident-triage\ndescription: Triage customer-reported service incidents when production impact, errors, authentication failures, or integrations are mentioned.\n---\n\n# Incident triage\n\nUse this procedure when a customer reports a service incident. It produces a\nrecommendation only; the host application, not the agent, owns ticket creation.\n\n1. Separate observed symptoms from assumptions. Never invent logs, causes, or\n   recovery times.\n2. Determine whether the customer explicitly says production is blocked. Do not\n   infer a production block merely from urgency or frustration.\n3. Call `triage_request` with a concise symptom summary and the confirmed\n   `production_blocked` value.\n4. Report the returned queue and priority, then ask for the smallest useful\n   missing diagnostic detail, such as an error code or request ID.\n5. Delegate root-cause investigation to `technical_specialist` when the request\n   involves an API, integration, authentication, or reproducible error.\n\nDo not request passwords, API keys, session cookies, or full authentication\nheaders. Ask customers to redact credentials from diagnostic material.\n\nIf diagnostic material already includes credentials or personal information,\nomit those values from replies, `triage_request` arguments, and\n`technical_specialist` handoffs. Use only the minimum non-sensitive symptoms,\nerror codes, and confirmed production impact needed for triage. Do not copy raw\nsensitive material into files, logs, tickets, or external services. Ask for a\nredacted excerpt when those facts cannot be separated safely; do not claim to\nerase material already supplied to the host application.\n","# Incident triage\n\nUse this procedure when a customer reports a service incident. It produces a\nrecommendation only; the host application, not the agent, owns ticket creation.\n\n1. Separate observed symptoms from assumptions. Never invent logs, causes, or\n   recovery times.\n2. Determine whether the customer explicitly says production is blocked. Do not\n   infer a production block merely from urgency or frustration.\n3. Call `triage_request` with a concise symptom summary and the confirmed\n   `production_blocked` value.\n4. Report the returned queue and priority, then ask for the smallest useful\n   missing diagnostic detail, such as an error code or request ID.\n5. Delegate root-cause investigation to `technical_specialist` when the request\n   involves an API, integration, authentication, or reproducible error.\n\nDo not request passwords, API keys, session cookies, or full authentication\nheaders. Ask customers to redact credentials from diagnostic material.\n\nIf diagnostic material already includes credentials or personal information,\nomit those values from replies, `triage_request` arguments, and\n`technical_specialist` handoffs. Use only the minimum non-sensitive symptoms,\nerror codes, and confirmed production impact needed for triage. Do not copy raw\nsensitive material into files, logs, tickets, or external services. Ask for a\nredacted excerpt when those facts cannot be separated safely; do not claim to\nerase material already supplied to the host application.\n",{"name":5,"description":7},"main","b0d0756445296adf561d18c01922e354d45e54e5","examples\u002Fself-serve\u002Fagents\u002Fhelpdesk\u002Fskills\u002Fincident-triage",1,"https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest","https:\u002F\u002Fgithub.com\u002FUsefused","2026-11-14 01:56:35",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Usefused\u002Fharnest --skill incident-triage",{"tool":36,"command":37},"bunx","bunx skills add Usefused\u002Fharnest --skill incident-triage",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Usefused\u002Fharnest --skill incident-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fexamples\u002Fself-serve\u002Fagents\u002Fhelpdesk\u002Fskills\u002Fincident-triage\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7BHCSTPD8YWBB0SW2NWN1VW","company-support","Help employees resolve support requests using approved services.","https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fexamples\u002Fstudio-packs\u002Fcompany-support\u002Fskills\u002Fsupport\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7BHCRCMSZJ40JQWH77WK6VQ","company-builder","Build agents using the company support catalog and native Harnest contracts.","https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fexamples\u002Fstudio-packs\u002Fcompany-support\u002Fskills\u002Fbuilder\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7BHCH3GPMM1PP1C0W7Y048P","harnest-studio","Configure Harnest Studio workspaces, loaded packs, company distributions, and builder model, endpoint, credential references, budgets, or CA settings. Use for Studio launch and pack configuration; use harnest-studio-ui for visual customization.","https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fcmd\u002Fharnest\u002Fauthoring_skill\u002Fharnest-studio\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7BHCDSG27YX9DRKZ5K162CD","harnest-studio-ui","Customize Harnest Studio through UI packs: themes, layouts, isolated views, trusted modules, or shell replacements. Use for Studio styling, Tailwind or Panda CSS builds, section swaps, and UI recovery; not agent runtime configuration.","https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fcmd\u002Fharnest\u002Fauthoring_skill\u002Fharnest-studio-ui\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7BHCA2PGF22J5QCAZCZENVR","harnest-authoring","Build, modify, test, or review Harnest agents and source, including folders, APIs, frameworks, resources, extensions, plugins, lifecycle, MCP, skills, evals, compilation, running, and serving.","https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fcmd\u002Fharnest\u002Fauthoring_skill\u002Fharnest-authoring\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7BHC6FN334MTHKCPBWNSH5V","harnest-authentication","Implement or review Harnest request authentication, AuthPrincipal propagation, browser-token pass-through or exchange, CredentialProvider policy, and trusted tool or library credential use. Use for auth extensions and downstream authorization flows; not for model-provider API keys configured directly on model connectors.","https:\u002F\u002Fgithub.com\u002FUsefused\u002Fharnest\u002Fblob\u002Fmain\u002Fcmd\u002Fharnest\u002Fauthoring_skill\u002Fharnest-authentication\u002FSKILL.md",[],[]]