How do I install the Daily Reflection skill?

Run npx skillmds@latest add phoenixrr2113/daily-reflection in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Daily Reflection safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Daily Reflection?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Daily Reflection free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Daily Reflection?

Phoenixrr2113 (@phoenixrr2113) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Daily Reflection by phoenixrr2113 — Agent Skill

Name: Daily Reflection
Author: Phoenixrr2113

Daily Reflection

Scheduled end-of-day synthesis. Runs at 18:00 daily — reads the day's sessions, writes a structured journal entry to memory/journal/, and proposes rule candidates from patterns across recent journals. Use when the harness schedule fires or when the user asks to summarize today's activity.

Phoenixrr2113 319ff3c 9 files · 21.5 KB Updated Sep 17, 2026

File contents

Workflow: Daily Reflection

When to use

This skill is triggered automatically at 18:00 by the harness scheduler (metadata.harness-schedule: 0 18 * * *). Invoke it manually when:

The user asks to synthesize or summarize today's work.
The user asks what was accomplished, learned, or left open.
You want to extract rule candidates from recent journals after a significant session.

Available scripts

scripts/synthesize.sh [--date YYYY-MM-DD] [--harness-dir <path>] — Run the daily journal synthesis for the given date (default: today). Returns structured JSON with journal_path, sessions_processed, and patterns_detected.
scripts/propose-rules.sh [--harness-dir <path>] — Analyze recent journals and propose instinct/rule candidates. Returns JSON with a list of candidates and their source reasoning.

Workflow

Synthesize: Run scripts/synthesize.sh (optionally with --date). On status: ok, the journal file is at result.journal_path.
Propose rules: Run scripts/propose-rules.sh to extract rule candidates from the new (and recent) journal entries.
Review: Present the journal summary and rule candidates to the user for review before any rule is promoted to an instinct.

Gotchas

Both scripts require a working harness binary on PATH (or --harness-dir pointing to a valid harness directory).
synthesize.sh is idempotent by default — re-running on the same date overwrites the existing journal entry. Pass --no-force if you want to preserve an existing entry.
propose-rules.sh reads the last 7 days of journal entries. On a fresh harness with fewer than 7 days of history the output will be sparse — this is expected.

Failure modes

NO_SESSIONS — No session files found for the requested date. Nothing to synthesize. Inform the user and exit.
JOURNAL_COMMAND_FAILED — The underlying harness journal command returned a non-zero exit code. The error details are in error.message. Check that Ollama is running and the configured model is available.
LEARN_COMMAND_FAILED — The harness learn command failed. See error.message. Same checks as above.
INVALID_DATE — The --date argument does not match YYYY-MM-DD. Fix the format and retry.

---name: daily-reflectiondescription: Scheduled end-of-day synthesis. Runs at 18:00 daily — reads the day's sessions, writes a structured journal entry to memory/journal/, and proposes rule candidates from patterns across recent journals. Use when the harness schedule fires or when the user asks to summarize today's activity.license: MIT---# Workflow: Daily Reflection## When to useThis skill is triggered automatically at 18:00 by the harness scheduler(`metadata.harness-schedule: 0 18 * * *`). Invoke it manually when:- The user asks to synthesize or summarize today's work.- The user asks what was accomplished, learned, or left open.- You want to extract rule candidates from recent journals after a significant session.## Available scripts- `scripts/synthesize.sh [--date YYYY-MM-DD] [--harness-dir <path>]` — Run the daily journal synthesis for the given date (default: today). Returns structured JSON with `journal_path`, `sessions_processed`, and `patterns_detected`.- `scripts/propose-rules.sh [--harness-dir <path>]` — Analyze recent journals and propose instinct/rule candidates. Returns JSON with a list of candidates and their source reasoning.## Workflow1. **Synthesize:** Run `scripts/synthesize.sh` (optionally with `--date`). On `status: ok`, the journal file is at `result.journal_path`.2. **Propose rules:** Run `scripts/propose-rules.sh` to extract rule candidates from the new (and recent) journal entries.3. **Review:** Present the journal summary and rule candidates to the user for review before any rule is promoted to an instinct.## Gotchas- Both scripts require a working `harness` binary on `PATH` (or `--harness-dir` pointing to a valid harness directory).- `synthesize.sh` is idempotent by default — re-running on the same date overwrites the existing journal entry. Pass `--no-force` if you want to preserve an existing entry.- `propose-rules.sh` reads the last 7 days of journal entries. On a fresh harness with fewer than 7 days of history the output will be sparse — this is expected.## Failure modes- `NO_SESSIONS` — No session files found for the requested date. Nothing to synthesize. Inform the user and exit.- `JOURNAL_COMMAND_FAILED` — The underlying `harness journal` command returned a non-zero exit code. The error details are in `error.message`. Check that Ollama is running and the configured model is available.- `LEARN_COMMAND_FAILED` — The `harness learn` command failed. See `error.message`. Same checks as above.- `INVALID_DATE` — The `--date` argument does not match `YYYY-MM-DD`. Fix the format and retry.

Frequently asked questions