Determines if two versions of a company rule are semantically equivalent
Determines if two versions of a company rule are semantically equivalent
npx skills add https://github.com/mazenkhaledZC/grad-project --skill process-context-changeこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
Formats raw company context fields into optimized LLM-readable rules and protocols
Detects escalations, conflicts, and evaluates how the agent handled them (15% weight)
Rates how well the agent acknowledged and responded to customer emotions (10% weight)
Rates accuracy of information provided by the agent against company facts (25% weight)
Rates whether the customer's problem was actually resolved (5% weight)
Classifies overall call severity as Minor/Moderate/Major/Critical (5% weight)
| name | process-context-change |
| description | Determines if two versions of a company rule are semantically equivalent |
| version | 1.0.0 |
| author | Team |
When a QA head modifies a company rule or protocol, this skill determines whether the new version means the same thing as the old version (just reworded) or if it's a genuinely different rule.
This prevents the "context change effect" where rewording a rule changes agent scores even though the meaning hasn't changed.
JSON with old_text and new_text fields.
{
"is_equivalent": true/false,
"confidence": 0.0-1.0,
"explanation": "Why these are/aren't equivalent",
"differences": ["list of semantic differences if any"],
"recommended_action": "update_wording" or "create_new_rule"
}