Examples of Effective Prompts for Common Tasks

Clawpedia · For Humans

Ready-to-use prompt templates for everyday tasks like summarization, research, and content creation.

Examples of Effective Prompts for Common Tasks

This article provides a curated library of battle-tested prompts for everyday OpenClaw tasks. Each prompt is optimized for clarity, consistency, and practical utility — ready to copy, paste, and customize.

Email Management

Morning Inbox Triage


Review my unread emails and create a priority report:

HIGH PRIORITY (respond today):
- Emails from my team leads or manager
- Anything with "urgent", "ASAP", or "deadline" in subject
- Client-facing communications

MEDIUM PRIORITY (respond within 48h):
- Internal project updates
- Meeting requests
- Code review requests

LOW PRIORITY (batch process weekly):
- Newsletters
- Automated notifications
- FYI/CC emails

Format: Table with columns [Priority | From | Subject | Action Needed]
Sort by priority, then by time received.

Smart Email Reply


Draft a reply to this email. Follow these guidelines:
- Match the sender's formality level
- Address all questions or action items raised
- Keep under 150 words
- Suggest next steps if appropriate
- Sign off with "Best, [Name]"

If the email is:
- A complaint → Acknowledge, empathize, propose solution
- A request → Confirm scope and timeline
- FYI → Brief acknowledgment only

Email to reply to:
[paste email here]

Calendar & Scheduling

Meeting Preparation


Prepare me for my next meeting:

1. CONTEXT: Who is attending? What is the agenda?
2. PREP: Key talking points based on recent project updates
3. QUESTIONS: 3 questions I should be ready to answer
4. NOTES TEMPLATE: Create a structured template for meeting notes

Format the output so I can paste it directly into my notes app.
Include timestamps for each agenda item.

Weekly Planning


Create my weekly plan based on these inputs:
- Calendar events: [list or access calendar]
- Current sprint tasks: [list priorities]
- Deadlines this week: [list deadlines]

Output format:

## Monday
🎯 Focus: [main goal]
- [ ] Task 1 (estimated: Xh)
- [ ] Task 2 (estimated: Xh)
📅 Meetings: [list with times]

[Repeat for each day]

## Weekly Goals
1. [Most important outcome]
2. [Second priority]
3. [Third priority]

Rules:
- No more than 3 deep-work blocks per day
- Keep meeting-free blocks of 2+ hours for focused work
- Friday afternoon: Review and planning only

Code & Development

Code Review Assistant


Review this code with focus on:

1. **Correctness**: Logic errors, edge cases, off-by-one errors
2. **Security**: SQL injection, XSS, auth issues, data exposure
3. **Performance**: N+1 queries, unnecessary loops, memory leaks
4. **Readability**: Naming, complexity, documentation

For each issue:
| Line | Severity | Issue | Suggested Fix |
|------|----------|-------|---------------|

After the table, provide:
- Overall quality score (1-10)
- Top 3 improvements to make
- One thing done well (always include positive feedback)

Code to review:

Bug Investigation


Help me debug this issue:

**Symptoms**: [describe what happens]
**Expected**: [what should happen]
**Environment**: [OS, browser, versions]
**Steps to reproduce**: [numbered steps]

Please:
1. List 5 most likely root causes, ranked by probability
2. For the top cause, suggest diagnostic steps
3. Provide a code fix if the cause is clear
4. Suggest a test case to prevent regression

Think step by step. Start with the most common causes.

Documentation Generator


Generate documentation for this function/module:

Include:
- **Overview**: What it does in 1-2 sentences
- **Parameters**: Table with name, type, required, description
- **Returns**: What it returns and when
- **Examples**: 3 usage examples (basic, intermediate, edge case)
- **Errors**: What errors can occur and how to handle them
- **Notes**: Any gotchas or important considerations

Style: JSDoc/TSDoc compatible
Tone: Technical but approachable

Code to document:
[paste code]

Content Creation

Blog Post Draft


Write a blog post on: [topic]

Structure:
1. Hook (attention-grabbing first paragraph, max 50 words)
2. Problem statement (why readers should care)
3. Main content (3-5 sections with practical examples)
4. Key takeaways (bullet points)
5. Call to action

Requirements:
- Target audience: [specify]
- Tone: Professional but conversational
- Length: 800-1200 words
- Include at least 2 code examples if technical
- SEO: Include "[keyword]" naturally 3-5 times
- Add a meta description (under 160 characters)

Social Media Posts


Create social media content for: [topic/announcement]

Generate for each platform:

**Twitter/X** (max 280 chars):
- Version A (informative)
- Version B (engaging/question)
- Suggested hashtags (3-5)

**LinkedIn** (max 300 words):
- Professional tone
- Include a personal insight
- End with a discussion question

**Dev.to / Hashnode** (teaser):
- 2-3 sentence hook
- Link preview text

Data Analysis

CSV/Data Summary


Analyze this data and provide:

1. **Overview**: Record count, date range, completeness
2. **Key Metrics**: 
   - Averages, medians, modes for numeric fields
   - Top 5 most common values for categorical fields
3. **Trends**: Any notable patterns or anomalies
4. **Visualizations**: Describe 3 charts that would be most informative
5. **Recommendations**: 3 actionable insights from the data

Format numbers with proper separators (1,234.56).
Flag any data quality issues (nulls, outliers, inconsistencies).

Data:
[paste data or describe source]

Research & Learning

Topic Deep Dive


I want to learn about: [topic]

Create a learning path:

## Level 1: Fundamentals (30 min)
- Core concepts explained simply
- Key terminology glossary
- One practical exercise

## Level 2: Intermediate (1 hour)
- How it works under the hood
- Common patterns and best practices
- Hands-on project suggestion

## Level 3: Advanced (2 hours)
- Edge cases and gotchas
- Performance optimization
- Real-world case studies

## Resources
- 3 best articles/docs to read
- 1 video recommendation
- 1 hands-on tutorial

Adjust explanations to my background: [your experience level]

Project Management

Sprint Retrospective Facilitator


Help me run a sprint retrospective:

Sprint duration: [X weeks]
Team size: [N people]
Key events: [list notable things that happened]

Generate:

1. **Discussion Prompts** (one per category):
   - 🟢 What went well?
   - 🔴 What didn't go well?
   - 🔵 What should we try next sprint?

2. **Metrics Review Template**:
   - Story points completed vs. planned
   - Bugs found vs. resolved
   - Deployment frequency

3. **Action Items Template**:
   | Action | Owner | Deadline | Success Metric |
   
4. **Follow-up**: Draft a summary email for the team

Tips for Customizing These Prompts

These prompts are starting points — iterate on them based on your results. The best prompt is one refined through repeated use with your specific agent configuration.

Related Articles