CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

incident

Triage recurring PsychSift canary, CI, runtime, scheduled-task, and provider failures into reproducible causes, impact, containment, and next actions. Use for regressions, outages, flaky jobs, alerts, or repeated nightly or weekly failures.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Incident

  1. Build a timeline from local logs, saved artifacts, workflow definitions, and known-good comparisons.
  2. Classify the failure as deterministic code, fixture/data drift, schedule, concurrency, environment, quota, provider, or observability.
  3. Reproduce offline with the smallest fixture, parser test, or triage artifact before editing.
  4. Implement only safe local containment or correction and verify the exact failure path.
  5. Do not query GitHub, hosted CI, Supabase, OpenAI, production logs, or providers without approval.
  6. Report impact, cause confidence, fix, proof, remaining uncertainty, and gated live confirmation.
Repository

BigSimmo/PsychSift

Path

.agents/skills/incident/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.