auto-experience-trigger

Automated debugging session capture detects when troubleshooting exceeds time thresholds or repeats failure patterns, then converts the successful fix into a reusable SKILL.md artifact with standardized frontmatter and instructions.

Automatic trigger detection activates capture when debugging exceeds a time threshold, repeats too many attempts, or matches a known failure pattern across code errors, service outages, and API issues.

Skill generation compresses the successful resolution path into a concise SKILL.md document containing frontmatter, instructions, and reuse guidance, then immediately synchronizes the artifact to Git.

Yes, it eliminates repeated trial-and-error by recognizing historically familiar failure patterns and automatically turning the winning fix into a reusable Skill for instant future application.

Yes, standardized SKILL.md generation produces a document with required frontmatter, concise instructions, and reuse guidance to ensure future resolutions remain fast and consistent.

Automatic skill generation requires silent threshold monitoring and same-pattern recognition to activate, meaning it only triggers when debugging becomes slow, repetitive, or historically familiar rather than capturing isolated incidents.