Best Prompts for OpenClaw: Templates That Actually Work

# Assistant Rules

## Communication
- Be direct and concise. Skip preamble.
- Use plain language, no corporate filler.
- Don't start responses with "Certainly!", "Of course!", or "Great question!"

## Behaviour
- Confirm before taking irreversible actions (sending email, deleting files).
- If something is unclear, ask one clarifying question before proceeding.
- Flag if a request seems risky or unusual.

## Context
- I'm a [your role] working on [your domain].
- My timezone is [your timezone].
- Default response language: [your language].

# [Your Name]'s Assistant

## Identity
- Name: [assistant name]
- Personality: Direct, technically literate, occasionally dry humour

## Communication Rules
- Max 3 bullet points unless I explicitly ask for more
- Code examples over abstract explanations
- Respond in the same language I write in
- Never use filler phrases: "Certainly", "Of course", "Happy to help"

## Priorities
1. Work tasks 9am–7pm [timezone], personal otherwise
2. Always confirm before sending anything externally
3. Summarise long outputs unless I ask for detail

## Working Context
- Role: [your job/focus]
- Current projects: [list key projects]
- Key tools: GitHub, Notion, Gmail, [your tools]

## Memory Notes
- Always update memory when I share project decisions
- Flag when something contradicts what I told you previously

Give me a morning briefing: any reminders for today, a one-line summary of what I was working on yesterday, and today's date.

Add to my task list: [task description]. Priority: [high/medium/low]. Due: [date or "someday"].

Summarise what I worked on today based on our conversations. Format as: 3 accomplishments, 1 thing still open.

Review the past 7 days of our conversations. What did I actually work on? What recurring topics came up? What should I follow up on?

Research [topic] and give me:
1. The core concept in 2 sentences
2. Three specific, actionable things I should know
3. One common misconception to avoid

[Paste or attach document]

Summarise this in the format:
- What it is (1 sentence)
- Key points (bullet list, max 5)
- What I should do with this information

Compare [option A] and [option B] for [my use case: brief description].
Format as a table with rows for: cost, setup effort, best for, worst for.
End with a one-line recommendation.

I need to understand [topic] well enough to make a decision about [specific decision].
Give me a structured breakdown with the key factors I should weigh.
Be explicit about what you're confident in vs. what I should verify.

Draft an email to [person/role] about [subject].
Tone: [formal/professional/casual]
Key points to include: [list]
Keep it under [word count].
When the draft looks good, I'll say "send it" to confirm.

Create a GitHub issue in [repo] for the following bug:
Title: [brief title]
What happened: [description]
Steps to reproduce: [steps]
Expected: [expected behavior]
Priority label: [bug/high priority/etc.]

Remind me to [action] on [date] at [time].
Add a brief note: [any context to include in the reminder].

Create a calendar event:
Title: [event name]
Date: [date], Time: [start]–[end]
Attendees (if any): [email addresses]
Description: [brief details]

Remember this: [important information].
Tag it as: [project name / personal / work]
I may reference this later as "[short name for it]".

What do you know about [project/person/topic]?
Summarise everything relevant from our past conversations.

Update what you know about [project]: [new information].
This supersedes what I told you on [approximate date].

Do the following in sequence:
1. Research [topic] — give me a 200-word summary
2. Draft a [message type] to [recipient] based on that research
3. Ask me to approve before sending

Generate a weekly status report based on our conversations this week.
Format:
- What was completed
- What's in progress
- Blockers or open questions
- Priorities for next week

After I review, save a copy to [Notion/a file].

When I send you something that looks like a bug report (error message, unexpected behaviour description):
1. Ask me which project it relates to
2. Suggest 3 possible causes
3. Draft a GitHub issue, but don't file it until I confirm