I have been helping founders build their distribution for almost 9 years. And SEO has been a core strategy for organic distribution. It works, it brings people who already have an intent to buy and use products. It just works.

But lately, things have changed. We are not using keywords on Google to find new things, unless we really are specific. We are going to GPT and Perplexity to ask questions.

And AI agent's own recommendation is playing critical role in our judgement of buying a product. So we released answerrank.so to help people get more visible on AI.

You don't necessarily need this tool and you can use Claude or GPT for this process. But it can definitely give you a lot of insights about hidden opportunity. Also, you can do a competitor analysis and model their processes.

Whether you use this tool or not, I recommend implementing these 3 things in your business:

1. Add more credibility in everything you say or write. For example, discuss real results, proofs and past work that anyhow supports your claims in the articles and videos.

2. Complete answer to a specific question in a segment. Don't create fragmented answers. What I mean by that is, if you are writing a paragraph, try to complete it. Don't say 'I will answer it later'. AI overviews mostly directly put this piece as a full answer with the link. It works

3. If you are using Cloudflare like 40% of the websites on internet, go and 'allow AI crawlers' to access your website. By default it blocks them. And that means your URLs won't be accessible by the bot.

I hope this helps. If you have any other ideas to help comment below.

Surely I have enough credits for one last task

https://fortune.com/article/ai-godfather-radiologists-obsolete-salaries-up-to-571k-demand-growing/

https://preview.redd.it/6ax0t6gxtheh1.png?width=2752&format=png&auto=webp&s=8f4511e4a12a660b4eeefedbbc409cc8eca9a47d

Claude's Fable 5 is the smartest model available, but if you don't make the right moves you'll burn through your usage credits fast. The secret to mastering it without breaking the bank is simple: Fable 5 thinks for 2 prompts, Opus 4.8 does the rest. Bring Fable your hardest problems, set the ground rules up front, let it architect the solution in two turns, and then switch to a cheaper model for the multiple message execution back-and-forth. Here are the 25 pro moves to make every credit count.

Fable 5 is the smartest model most people have ever touched, but it's also where sloppy habits show up on a bill. That combination is a gift. It forces you to work the way you should have been working all along: front-load context, ask for judgment instead of simple tasks.

This guide breaks down everything you need to know: the economics, the exact prompts, the pro moves, and the mistakes that quietly burn your credits. Here are 25 ways to master the model.

Understand the Economics

1. Every message re-reads the whole thread. Claude has no running memory inside a chat. Each time you hit send, the model re-reads everything above it, and you pay for that re-read. Long, meandering chats are the single biggest source of surprise bills.

2. Thinking costs the same as writing. Fable 5 reasons in a hidden scratchpad before it answers, and those thinking tokens are billed like output tokens. Higher effort means more thinking, which means better answers on hard problems and pure waste on easy ones.

3. Effort is a dial, not a cap. The effort setting nudges how thorough the model chooses to be. High effort on a trivial task doesn't buy you a better answer, it buys you a longer wait and a bigger draw on your usage.

Before You Prompt

4. Pick one super hard, expensive problem. Using it for simple admin tasks is shooting a bird with a bazooka. Fable 5 earns its cost on problems where being 20% smarter changes the outcome. If you'd hand the task to an intern, use a cheaper model.

5. New task, new chat. No exceptions. Reusing an old thread means paying to re-read irrelevant conversation and polluting the model's attention. Fresh chat, fresh focus, smaller bill.

6. Select Fable 5, set Effort to High. High is the recommended default for serious work. Save the top tier for truly brutal jobs.

7. Match effort to cognitive demand. A long, detailed prompt about something simple needs less effort. A one-line question about something genuinely hard deserves the top tier.

8. Paste your "about-me" doc. Create a living document covering who you are, your business model, how you write, and what "good" looks like. Paste it at the top. Thirty seconds of pasting replaces twenty messages of the model guessing wrong.

The First Prompt (The 5 Standing Instructions)

This is where 80% of the outcome is decided. Your first message should contain your context doc, your goal, and these five instructions:

9. Give it your goal, not a task.
   Prompt: "I need [task] for [goal]. I expect [goal] achieved once we hit [specific targets]."

10. Add "Ask me questions first."
    Prompt: "Start by asking me questions about the task, goal, and targets to fully understand the context before doing any work."

11. Add "Answer first, explain after."
    Prompt: "Lead with the bottom line. Your first sentence should be the answer or recommendation. Supporting reasoning comes after."

12. Add "Don't say done. Prove it."
    Prompt: "Only report work you can point to evidence for. If something is not verified, say so explicitly."

13. Add "Pick one option. Commit."
    Prompt: "When you have enough information to act, act. Give me a recommendation, not a survey of options. If you'd stake your reputation on one path, tell me which and why."

14. Bonus: Fence the scope.
    Prompt: "Don't add features, sections, or work beyond what the task requires." (Prevents expensive over-delivering).

Run the Session

15. Send it, then answer its questions. It will ask 3 or 4 sharp ones. Answer all of them in a single message, numbered. Don't dribble answers across multiple messages.

16. Let it work. Don't interrupt. Every "oh wait, also..." makes it re-read everything. Batch everything into your next message.

17. Edit your mistakes, don't send corrections. If your last message was wrong, edit that message instead of sending a correction. Editing rewrites history so you don't pay to carry your mistake through every future turn.

18. Stop after 2 messages. Message one is the interview. Message two is the answer. If you're on message six with Fable, you're paying premium rates for execution work.

The Handoff (The Ultimate Pro Move)

19. Switch to Opus 4.8, same chat. This is the highest-leverage move in the entire workflow. Opus reads everything Fable just planned and executes at a fraction of the cost.

20. Finish everything there. Drafts, edits, formatting, the 20-message back-and-forth, all on Opus. Fable thinks for 2 prompts. Opus does the rest.

21. Save it all in a Project. Move your about-me doc, standing instructions, and key outputs into a Project. Tomorrow starts warm instead of from zero.

Things Most People Miss

22. Trim before you paste. Don't dump a 40-page PDF when 3 pages answer the question. You pay for every token on every subsequent turn. Upload .md files instead of PDFs that take a lot of tokens to parse.

23. Ask for the anti-case. After Fable commits, ask: "Steelman the strongest argument against this. What would make it wrong?"

24. Use it as a red team. Paste your own plan and ask: "Find the three weakest assumptions and attack them."

25. Give it your decision, not just your question. "Should I do A or B, here's my current lean and why" gets a dramatically better answer than "compare A and B."

The Master Prompt (Copy-Paste Ready)

[Paste your about-me doc]

I need [task] for [goal]. I expect [goal] achieved once we hit [specific targets].

Ground rules:

•Start by asking me questions about the task, goal, and targets before doing any work.

•Lead with the bottom line. First sentence is the answer, reasoning comes after.

•Only report work you can point to evidence for. If something is not verified, say so.

•When you have enough information to act, act. One recommendation, not a menu.

•Don't add work beyond what the task requires.

Send this to your team. They're burning credits.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

SpaceXAI: In response to user questions about privacy: Since launch, Grok Build has fully respected zero data retention (ZDR). All users have always had the ability to disable data upload in the CLI.

When data upload was disabled, this choice was respected. In the early beta, data retention was enabled by default for non-ZDR users. Based on your feedback, we changed this. We are now going further to protect privacy.

With all retained data deleted, retention default off, and an open-source harness, we are offering complete user privacy. You can also run Grok Build fully open-sourced and local-first with your own inference.

We disabled default retention for all Grok Build users starting on July 12th. Additionally, we are deleting all coding data that was previously retained, ensuring every user’s preferences are respected. With these steps, Grok Build goes beyond other major coding products to protect user privacy.

If you are using Claude regularly, you should be building Skills. They let you do the hard work of prompting once, save it, and reuse it forever.

I have spent a lot of time analyzing the exact anatomy of a Claude Skill that works every single time. There are 9 distinct parts you can include (Name, Description, Purpose, Steps, Format, Always, Never, Examples, Clarify).

But here is the truth: 7 of them barely matter.

There are only two parts that decide if your Skill works flawlessly or fails completely.

1. The Description

This is the most misunderstood part of building a Skill.

The Description is not for you. It is the part Claude reads to decide whether it should fire the Skill or not. If you write a vague description ("A skill for writing emails"), the Skill will just sit there and never fire.

How to fix it: Describe when to reach for it, not what it is. Make the trigger pushy.

Instead of: "This skill writes marketing emails."
Write: "Use whenever the user says 'write an email' or wants to launch a campaign — even if they never say the skill's name directly."

2. The "Never do" line

If you skip this line, your Skill will start hijacking chats it should ignore. It will jump in and try to apply its specific formatting or rules to completely unrelated conversations.

How to fix it: You need a hard guardrail.
Write: "Never use for [the thing it keeps stealing]."
For example: "Never use for internal team updates or casual Slack messages."

Two things the anatomy chart can't show you

1. The Debugging Trick
   If your Skill won't fire, don't rewrite the whole thing. Just ask Claude: "When would you use this skill?"
   Claude will read its own description back to you. You will instantly see exactly what is vague or missing from your trigger.

2. The Token-Saving Math
   People worry that installing 20 Skills will eat up their usage limits or context window. It won't.
   Claude only reads the 3-line header of your Skills until a task actually matches the description. In fact, a complex task that costs 12,000 tokens to run raw will often only cost 6,000 tokens when run through a well-optimized Skill.

Using Skills doesn't just save you time. It literally saves you money and compute.

Here is the full 9-part anatomy if you want to build the ultimate master template:

1.Name: kebab-case, no spaces, no "claude"

2.Description: [What it does] + [when to use it]. Make the trigger pushy.

3.Purpose: One plain sentence a brand-new hire would understand.

4.Steps: The workflow, in the order you actually do them, with reasons why.

5.Format & output: The exact shape of the output (Length, Tone, Structure).

6.Always do: Your hard rules and jargon replacements.

7.Never do: The guardrails. Never [the mistake you keep correcting].

8.Examples: Show, don't tell. Provide one good output and one weak output.

9.Clarify: "Ask before guessing. List questions, don't fill gaps silently."

Build your next workflow into a Skill using this framework, and let me know how it changes your output.

👇 What is the best Skill you've built so far? Let me know in the comments.