# The six things you can ask about > One section per Rabbot tool in Sidekick: the overall state, what is blocking sales, problems by area, one product, a fix, and what broke recently. > Category: Ask Sidekick > Canonical: https://rabbot.ai/docs/sidekick/the-sidekick-tools/ > Updated: 2026-09-20 --- Rabbot gives Sidekick six tools. You never type their names: ask a plain question and Sidekick picks the one it judges relevant. If the answer does not look like Rabbot's, [Troubleshooting Rabbot in Sidekick](/docs/sidekick/troubleshooting-sidekick/) covers how to steer it. The names are here so you know what exists and what each one is bound to answer. All six only read. ## Is my store OK The overall state of your store, from `get_store_check_summary`. It comes back as one of four things: passing, issues open, not yet established, or not known right now. With it come the open problem counts at each severity, the pages and checks the answer covers, and how many days your store has been monitored. Ask it as "is my store OK", "is anything broken", or "what should I fix first". It is the right question to open with, because the coverage it reports tells you how much weight the rest of the answers carry. ## Why is nothing selling What is stopping a sale as of the last check, from `list_whats_blocking_sales`. That means a product page that is dead or returning a 404, a landing page throwing an error, a password page left on, a missing add to cart button, or stock that disagrees with your admin. The answer is grouped per product, with the page involved and when the problem started, rather than a flat list of rows. Ask it as "nothing is selling" or "nobody can buy". ## Problems in one area Open problems in one part of your store, from `list_open_issues_by_area`, most serious first. There are three areas. Search covers titles, canonical tags, noindex, redirects, sitemaps, robots rules, and structured data. Storefront covers your pages, the add to cart button, availability, and prices. Site covers robots.txt, your sitemap, whether pages can be reached at all, and domain redirects. Ask it as "do I have SEO problems", "is a page noindexed by accident", or "did a redirect break". ## This one product page Everything Rabbot knows about a single product, from `diagnose_one_product_page`. Give it the product ID, the handle, or the storefront URL. The answer covers when the page was last checked, whether it loaded and could be bought, the state of its structured data, and every open problem on it. Ask it as "this product page is broken", "its price looks wrong", or "why can nobody buy this one". Name the product exactly or the turn ends without an answer. ## How do I fix this What to do about one named check on one page, from `get_fix_for_a_named_check`. The answer names the admin screen to open, says why the check matters, says whether Rabbot re-checks it by itself, and tells you when the state may be deliberate and can be marked intentional instead of fixed. [Dismiss as intentional](/docs/issues/dismiss-as-intentional/) covers that last case in full. Ask it as "how do I fix this" or "is this a real problem". ## What broke this week Problems Rabbot caught that are now resolved, from `list_problems_caught_and_cleared`, reaching back up to 30 days. Each one carries the page, the check, when it opened, when it closed, and how long the gap lasted. Ask it as "what broke this week", "what broke around that theme change", or "how long was that product unbuyable". It is the question to use after an app install or a theme edit, when you want to see what else changed with it.