← Back to Setup and basicsOpenClaw getting started
What to ask OpenClaw first
The best first prompts are practical, bounded, and verifiable. This page gives you a useful starter database instead of filler prompt theory.
Prompt ruleAsk for something that can be checked against a file, route, process, document, or named artifact.
Starter prompts
The five first asks that usually pay off
Workspace orientation“Summarize this workspace, tell me what project is here, and name the files I should read first.”
Rules and constraints“Find the local rules, startup instructions, or docs that will change how you should behave here.”
Locate the important thing“Find where the deploy script, config file, or docs for this feature actually live.”
Safe small improvement“Clean up this section of text or this static page block and verify the exact file changed.”
Truth check“Verify whether this service or route is healthy and show the evidence.”
Bad starter asks
What not to lead with
Huge ambiguous builds
“Build my whole app” is a bad first ask if nothing about the environment or constraints has been grounded yet.
Pure speculation
“What do you think is wrong?” is weaker than asking for a real inspection of files, logs, or routes.
Unverifiable style talk
Do not burn the first turn on abstraction when a concrete artifact would teach more.
Useful examples
Examples matched to real operator goals
For a website ownerAsk for a live route check, broken-link scan, or page structure summary.
For a content workflowAsk for article bundle validation, missing asset detection, or internal-link verification.
For a local coding repoAsk for project map, test commands, deploy path, and the critical startup files.
Open deeper reference links for this page