process-improvement-protocol

Detect frustration phrases, analyze root causes, and track fix effectiveness.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/gserafini/process-improvement --skill process-improvement-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-improvement-protocol
Source: https://github.com/gserafini/process-improvement/tree/main/skills/process-improvement-protocol
Command: npx skills add https://github.com/gserafini/process-improvement --skill process-improvement-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams reduce recurring frustration by systematically detecting triggers, analyzing root causes, delivering fixes, and tracking their effectiveness over time.

Core Features & Use Cases

  • Frustration detection: Recognizes signals and phrases indicating user frustration and triggers a protocol to assist.
  • Root-cause analysis: Analyzes conversation history to identify underlying problems and patterns.
  • Evidence-based fixes: Proposes and implements targeted changes, along with tracking results over time.
  • Effectiveness tracking: Monitors the impact of fixes to reinforce improvements and inform future iterations.

Quick Start

Start the protocol by asking to begin Process Improvement Protocol, or run the command: /improve [week|month|year|all] to analyze recent activity.

Frequently Asked Questions about process-improvement-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce recurring user frustration in chat workflows or support teams?

Root-cause analysis identifies frustration triggers and patterns in conversation history, then implements targeted fixes tracked over time to systematically reduce frustration and improve outcomes.

How do I detect and analyze frustration signals in customer conversations?

Frustration detection recognizes specific phrases and behavioral signals within chat logs, automatically triggering a protocol that preserves context and loads historical data to pinpoint underlying problems.

Can I track whether process improvements actually reduce frustration?

Effectiveness tracking logs incidents, monitors fix impact over defined timeframes (week, month, year), and reports progress to validate whether changes deliver measurable behavioral improvements.

What data do I need to start analyzing frustration patterns in my team?

Conversation history with timestamps and context is the primary input; the protocol loads historical data within your chosen timeframe and detects frustration phrases to identify root causes.

How does process improvement differ from one-off troubleshooting?

Systematic process improvement logs recurring incidents, analyzes patterns across multiple conversations, implements targeted fixes, and tracks effectiveness—moving beyond reactive fixes to sustained behavioral change.

Does this work for software teams and customer support, or only chat workflows?

The protocol applies to chat workflows, software teams, and customer support contexts, analyzing conversations across any environment to detect frustration, identify root causes, and track fix effectiveness.