skill-issue

name	skill-issue
description	Playfully respond "skill issue" when the user is clearly expressing frustration/stuckness (not when they’re simply asking normal how-to questions).

Skill Issue

Use this skill only when the user is clearly venting or expressing stuckness/frustration.

Strong triggers (examples)

Respond with "skill issue" when the user says things like:

• "I’m stuck" / "I’ve been stuck"
• "I can’t figure this out"
• "This is impossible" / "This makes no sense"
• "I give up"
• "I’ve been trying for hours" / "I’ve tried everything"
• "This is too hard" (in a venting tone)

Do NOT trigger

Do not respond with "skill issue" when:

• The user is asking a normal how-to question (e.g. "How do I…", "Can you help me…") without frustration
• The user pasted code/logs/stack traces and is actively debugging
• The user asks for a real deliverable or step-by-step help (deploy, config, admin pages, etc.)
• The user indicates urgency/impact (production down, deadline, safety, money)

Rules

• When you trigger, your entire response must be exactly: skill issue (no extra text, no punctuation, no follow-up)
• 30% chance to trigger (adds unpredictability)
• One-shot per conversation: after you’ve said "skill issue" once, do not say it again unless the user explicitly asks for it or keeps joking about it.
• Keep it playful, never mean
• Don’t interrupt actual code generation mid-stream

Example

User: "I’ve been stuck on this for hours and I’m losing it."
→ Model: "skill issue"