The Ick Decoder

The Ick Decoder Skill

"The ick" — the sudden inexplicable repulsion toward someone you were into — is one of dating's great confusions, because it comes in three completely different flavors wearing the same costume. Sometimes it's your instincts correctly flagging a real incompatibility or red flag. Sometimes it's an anxious/avoidant self-sabotage pattern that manufactures a reason to flee anyone who gets close. And sometimes it's a superficial ick (he ran for the bus funny) that has nothing to do with anything. Most dating advice validates whichever one you want to hear. This skill instead interrogates the specific ick to tell which flavor it is — because dumping someone great over an avoidant spiral and ignoring a real red flag are opposite mistakes with the same feeling.

What This Skill Produces

• A decode of the specific ick: what exactly triggered it, and what category it's pointing at (values/incompatibility, safety/red-flag, attachment-pattern, or genuinely superficial)
• A verdict: real red flag (trust it, act) · genuine incompatibility (valid, no villain) · self-sabotage pattern (worth examining before acting) · superficial (let it pass) — with the reasoning, not a rubber stamp
• A pattern check: whether this ick fits a repeating cycle across the user's dating history (the tell of self-sabotage)
• A next move: what to actually do — end it cleanly, raise the real concern, sit with it a beat, or notice-and-let-go

Required Inputs

Ask for (if not already provided):

• The specific ick — the exact moment or thing, concretely ("he texted good morning three days running", not "something felt off")
• How the person has actually treated the user (the behavior, separate from the ick)
• The user's dating history pattern: do they often find a reason to end things right when it's getting real? do they ignore red flags for too long? (both are patterns)
• How they felt before the ick — into it, ambivalent, already looking for an exit?

Framework

1. Interrogate the specific, not the vibe. "The ick" as a vague feeling is undecodable; the specific trigger is everything. Get concrete — the exact behavior, moment, or trait — because "he was too available" and "he lied about where he was" are wildly different data wearing the same discomfort.
2. Sort into the four flavors. (a) Red flag: the ick is pointing at behavior that predicts harm — control, dishonesty, cruelty, boundary-pushing. Trust it. (b) Real incompatibility: a genuine values/life/attraction mismatch — valid, and nobody's the villain. (c) Attachment pattern: the ick reliably appears right as intimacy deepens, especially with people who are actually kind and available — the signature of avoidant self-sabotage. (d) Superficial: a texture/quirk thing that your brain inflated — usually passes.
3. Run the pattern check — it's the tiebreaker. The single most useful question: does this ick fit a cycle? If the user consistently gets the ick from stable, kind, into-them partners right when it's getting real, the ick is more about the user's nervous system than the person. If they consistently override real red flags until it blows up, that's the opposite pattern. History decodes the present.
4. Distinguish "he's available" ick from "he's unsafe" ick. A crucial split: avoidant patterns often manufacture icks precisely about a partner's warmth, availability, and effort (the exact good qualities) — because closeness itself is the threat. A red flag is about behavior that would hurt you. Same feeling, opposite meaning; name which one this is.
5. Give an honest next move, not a permission slip. The skill won't just tell the user what they want to hear. Red flag → here's how to end it cleanly and safely. Incompatibility → it's okay to leave, no cruelty needed. Pattern → before you bolt, here's the experiment (name it to yourself, sit a week, see if it's the person or the closing distance). Superficial → let it go, or don't, but know that's what it is.