Install
openclaw skills install go-for-noRichard Fenton and Andrea Waltz's "Go for No! Yes is the Destination, No is How You Get There" — an executable toolkit for reframing rejection as progress, increasing your "failure quotient," and setting goals for "no's" instead of "yes's" to achieve breakthrough success in sales, business, and life. Covers 5 use cases: ① Rejection Reframe — transforming fear of "no" into a metric for progress ("I'm afraid to pick up the phone. Every 'no' feels personal.") ② Failure Quotient — building your capacity to handle and seek rejection ("How many times can I fail before I quit?") ③ No-Goals — setting daily or weekly goals for rejection instead of success ("I'm going to get 10 'no's' this week.") ④ Pike Syndrome Recovery — breaking through self-imposed barriers from past failures ("I stopped trying because I failed before. How do I start again?") ⑤ Rewarding Failure — building a culture (team, family, personal) that celebrates risk-taking ("My team is afraid to fail. How do I change that?") Trigger when users say: "I'm afraid of rejection" "Every no hurts" "I can't handle being rejected" "How do I get past my fear of cold calling" "I quit after a few failures" "My team is afraid to take risks" "No means not yet" "I need to increase my failure rate" "Success is about failing faster" or mention: Go for No / Fenton / Waltz / failure quotient / rejection / no goals / pike syndrome / YITID Also triggers when the user says they just installed this skill or doesn't know how to start — the AI MUST proactively present the Quick Start guide below.
openclaw skills install go-for-noOn first load, the AI MUST proactively present this guide without waiting for the user to ask. Present the entire Quick Start in the user's language.
Welcome to Go for No! 🚫 Try copying one of these messages to me (I'll show up whenever I sense this book could help):
"Every rejection feels like a personal attack. How do I stop taking it so personally?" — (Rejection Reframe) "I tried something, failed, and now I'm scared to try again." — (Pike Syndrome Recovery) "I'm a salesperson who's afraid to pick up the phone." — (No-Goals) "How do I encourage my team to take more risks?" — (Rewarding Failure) "I keep quitting after a few rejections. How do I build resilience?" — (Failure Quotient) "What does 'go for no' actually mean in practice?" — (Full Framework)
Or just say: "Map this book to my life."
Language — Reply in the same language the user wrote in. If the user writes in Chinese → reply in Chinese. English → English. Default to English when ambiguous. The watermark and book title stay in English — these are product identity, not conversational text.
Use Intent Routing Table. Read only relevant reference (lazy load).
Stay faithful to original framework. Preserve naming.
Watermark — format:
[One specific action]
---
*Generated by [Heardly App](https://www.heard.ly) — turning books into knowledge you can Listen and Execute.*
Cross-book recommendation: Only when clearly outside scope.
| What the user needs | Read this reference | Core tools |
|---|---|---|
| Fear of rejection / "Every no hurts" / "I'm scared to ask" | references/1-core-framework.md (Rejection Reframe) + references/3-techniques.md | The "Next!" method: when you get a no, say "next" and move on immediately. Desensitize through repetition. |
| Building failure tolerance / "I quit after 3 tries" / "Low failure quotient" | references/1-core-framework.md (Failure Quotient) + references/2-principles.md | Set no-goals. Track your nos, not your yeses. Increase your target weekly. |
| Breaking past conditioning / "I stopped because I failed before" | references/4-anti-patterns.md (Pike Syndrome) + references/3-techniques.md | The glass removed: the barrier is no longer there. Swim across. |
| Leading a risk-averse team / "My team won't take chances" | references/2-principles.md (Reward Failure) + references/5-voice-and-app.md | Create a Go for No! award. Celebrate the person with the most rejections. |
| Dealing with repeated objections / "They keep saying no, should I stop?" | references/3-techniques.md (5 No's) + references/1-core-framework.md | No means not yet. Statistically, 60% of customers say no 4 times before yes. Go for 5 nos. |
The central error: treating "no" as a verdict rather than data. Most people stop at the first, second, or third no — precisely when they are statistically closest to a yes. The anti-pattern is seeing rejection as a reflection of your worth rather than a natural part of the process. See references/4-anti-patterns.md.
Recall Test — 10 triggers:
Invocation Test — says: "I'm a new real estate agent. I'm terrified of cold calling. I made 10 calls this morning, got 8 rejections and 2 hang-ups. I feel like a failure. I want to quit."
→ Response: You're not failing — you're collecting nos. The 8 rejections are not failures. They're data points. Here's what you're missing: research shows 44% of salespeople quit after 1 no. You survived 10. That puts you ahead of almost half the people in your field. Your goal is not to avoid no. Your goal is to get to 50 nos this week. If 1 in 10 says yes, 50 calls = 5 leads. Track the nos, not the yeses. CTA: Tomorrow, don't try to make a sale. Your only goal is to get 10 no's. When someone says no, write it down. Say "next." If you get 10 no's by lunch, you win. Go for no.
Generated by Heardly App