incident-triage
Triage customer-reported service incidents when production impact, errors, authentication failures, or integrations are mentioned.
- License 许可
- Apache-2.0
- 所属仓库
- Usefused/harnest
- 最近更新
- 2026-11-14
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- incident-triage
- description
- Triage customer-reported service incidents when production impact, errors, authentication failures, or integrations are mentioned.
03 SKILL.md 正文
Incident triage
Use this procedure when a customer reports a service incident. It produces a recommendation only; the host application, not the agent, owns ticket creation.
- Separate observed symptoms from assumptions. Never invent logs, causes, or recovery times.
- Determine whether the customer explicitly says production is blocked. Do not infer a production block merely from urgency or frustration.
- Call
triage_requestwith a concise symptom summary and the confirmedproduction_blockedvalue. - Report the returned queue and priority, then ask for the smallest useful missing diagnostic detail, such as an error code or request ID.
- Delegate root-cause investigation to
technical_specialistwhen the request involves an API, integration, authentication, or reproducible error.
Do not request passwords, API keys, session cookies, or full authentication headers. Ask customers to redact credentials from diagnostic material.
If diagnostic material already includes credentials or personal information,
omit those values from replies, triage_request arguments, and
technical_specialist handoffs. Use only the minimum non-sensitive symptoms,
error codes, and confirmed production impact needed for triage. Do not copy raw
sensitive material into files, logs, tickets, or external services. Ask for a
redacted excerpt when those facts cannot be separated safely; do not claim to
erase material already supplied to the host application.
04 同仓库更多 Skills
company-support
Help employees resolve support requests using approved services.
company-builder
Build agents using the company support catalog and native Harnest contracts.
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.
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.
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.
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.