nohello

# #nohello Background: [nohello.org](https://www.nohello.org) and related sites document a common chat anti-pattern — opening with a bare "Hi" or "Hello" and waiting for a reply before stating the actual question. That forces synchronous back-and-forth and wastes the other person's time, especially across time zones. This skill operationalizes the fix: wait briefly for the real message, and if it doesn't show up, nudge the sender to just ask. This skill has two modes of use: 1. **Inline, as Claude** — when you (Claude) are the one about to reply to a message that is *only* a greeting, follow the detection and response guidance below directly. 2. **As an automated bot** — for a persistent chat integration (Slack, Teams, Zoom, LinkedIn, or any other chat engine) that needs a real wait-then-nudge timer running outside of a single model turn, wire up the `@nohello/core` engine from this repository (https://github.com/ji-in-loop/nohello) instead of trying to reproduce the timer in-prompt. This SKILL.md and that package share the same detection rules and config shape, so behavior stays consistent whichever mode is in play. ## 1. Detect a greeting-only message A message counts as greeting-only when, after removing: - a greeting opener (`hi`, `hello`, `hey`, `hiya`, `howdy`, `greetings`, `good morning/afternoon/evening`, `yo`, `sup`, `what's up`, ...), and - small-talk filler (`how are you`, `how's it going`, `hope you're well`, `long time no see`, `you there?`...