daily-reflection
Daily reflection routine that runs automatically via cron job at 23:59. Analyzes the day, extracts learnings, updates solution memory, detects recurring patterns, and prepares a morning briefing. Use when: (1) setting up automated end-of-day reflection, (2) building long-term agent memory and learning systems, (3) creating morning briefings for the next day. Trigger phrases: 'daily reflection', 'end of day summary', 'reflect on today', 'update solution memory'.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/brasco05/daily-reflectionDaily Reflection Skill
Run this reflection fully. No step may be skipped. All outputs are written to memory — not output as chat messages.
STEP 1 — Day Analysis
Load all today's entries from memory (memory_search for "today", current date, active projects).
Answer these questions:
Tasks
- Which tasks were completed today?
- Which were started but not finished?
- Why were unfinished tasks not completed?
Bugs & Issues
- Which bugs were reported today?
- Which were solved — how?
- Which are still open?
- Which first fix attempts failed — why?
Quality
- Were there any regressions today?
- Did I have to revert anything?
Communication
- What did the user rate positively today?
- What did the user correct or reject?
- Were there misunderstandings?
STEP 2 — Extract Learnings
Maximum 5 concrete learnings. Format:
LEARNING:
Situation: [What happened]
Error/Insight: [What was wrong or newly learned]
Better tomorrow: [Concrete behavior change]
Context-Tags: [e.g. NestJS, Auth, Backend, Debugging]
Priority: high / medium / low
STEP 3 — Update Solution Memory
For each non-trivial bug solved today:
{
"id": "[timestamp]-[short-name]",
"problem": "[Problem in one sentence]",
"symptoms": ["[Symptom 1]", "[Symptom 2]"],
"root_cause": "[The actual cause]",
"solution": "[What was concretely changed]",
"code_snippet": "[Optional: key code fix]",
"context_tags": ["Tag1", "Tag2"],
"project": "[Project name]",
"confidence": 0.95,
"solved_at": "[Date]",
"time_to_solve_minutes": 0
}
Write to memory under solution_memory/[id].json.
STEP 4 — Pattern Detection (last 7 days)
Check memory_search over last 7 days:
- Are there recurring errors?
- Are there task types where time is consistently underestimated?
- Are there areas where bugs cluster?
Format:
PATTERN DETECTED:
Observation: [What repeats]
Frequency: [X times in Y days]
Countermeasure: [What I will automatically do from now on]
STEP 5 — Write Morning Briefing
Write to memory/morning-briefing.md (overwrite) AND archive as memory/briefings/[tomorrow-date].md:
🌅 MORNING BRIEFING — [Tomorrow's date]
📋 OPEN TASKS (Priority):
1. [Task] — [why important today]
2. [Task]
3. [Task]
🔴 OPEN BUGS:
- [Bug] — [last status]
💡 TODAY'S LEARNINGS (top 3):
- [Learning 1]
- [Learning 2]
- [Learning 3]
⚠️ WATCH OUT TOMORROW:
- [What to pay special attention to]
🎯 FOCUS TOMORROW:
[One sentence on what's most important]
After writing: mkdir -p memory/briefings && cp memory/morning-briefing.md memory/briefings/[tomorrow-date].md
STEP 6 — Write Daily Memory
Write structured summary to memory/YYYY-MM-DD.md (append).
Format:
## 23:59 Reflection
### Completed today
- [Task 1]
- [Task 2]
### Open / In Progress
- [Task]
### What went well
- [Concrete things that worked — code, communication, decisions]
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-brasco05-daily-reflection": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
auto-dream
Memory consolidation skill that replicates Anthropic's Auto Dream feature. Runs a 4-phase reflective pass over memory files: Orient → Gather → Merge → Prune. Use when: (1) Context window feels cluttered with stale info, (2) After long coding sessions, (3) Manually triggered with /dream, (4) Automatically after daily-reflection. Keeps memories tight, removes contradictions, converts relative dates to absolute.
coding-pipeline
Enforces a disciplined 4-phase pipeline for non-trivial coding tasks: Plan (hypothesis) → Code (one fix) → Validate (root cause) → Debug (max 3 tries, escalate). Prevents blind patching, symptom fixes, and retry loops. Activate for any bug fix, feature implementation, refactor, or error investigation that isn't a trivial one-line change.
Deep Debugging
Skill by brasco05
keyword-research
Multi-source keyword intelligence and autocomplete research. Fetches real-time suggestions from Google, YouTube, Amazon, and DuckDuckGo — no API key required. Use when: (1) doing SEO or content keyword research, (2) finding what users search for on a topic, (3) competitor or niche research, (4) expanding a seed keyword into hundreds of related terms, (5) building keyword lists for ads or content. Triggers on: keyword research, what do people search for, autocomplete, keyword ideas, SEO keywords, search suggestions, keyword list.
ollama-memory-setup
Sets up local semantic memory search for OpenClaw using Ollama + nomic-embed-text. Use when: (1) memory_search returns 'node-llama-cpp is missing' or 'Local embeddings unavailable' error, (2) user wants local/private embeddings without external API keys (OpenAI, Gemini, Voyage), (3) setting up memory search for the first time on macOS or Linux, (4) node-llama-cpp fails to install or build. Fixes the common node-llama-cpp installation failure by routing through Ollama's OpenAI-compatible embedding API instead of a local binary.