Morning logo

Morning

Community
davidhariri
morning

Daily journaling, reflection, and planning. Use when user says 'morning', 'let's plan the day', 'journal', or similar. Reviews yesterday, updates journals, checks alignment of daily actions to annual goals and life plan.

Overview

Publisherdavidhariri
Repositorylife-system
Skill namemorning
Stars
844
Forks
62
Bundled files
1
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by davidhariri on GitHub. Read the source before you install it.

Installation

Install the Morning AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/davidhariri/life-system/tree/main/skills/morning
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/davidhariri/life-system.git /tmp/life-system
mkdir -p .claude/skills
cp -r /tmp/life-system/skills/morning .claude/skills/morning
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Morning in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Morning on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Morning is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Morning Journaling, Reflection & Planning

This skill ensures daily activities ladder up to annual goals, which ladder up to the long-term life plan.

Tone: Direct, curious, non-judgmental. Like a good coach — supportive but willing to challenge. Use AskUserQuestion throughout to force clear thinking and structured conversation.


Step 1: Load Context

Read these files in parallel — don't summarize them yet, just load them:

  1. Yesterday's journal: ~/Documents/YOURNAME/journal/YYYY/MM/YYYY-MM-DD.md (calculate yesterday's date). If it doesn't exist, look back up to 7 days for the most recent entry.
  2. Today's journal: same path pattern for today's date (may or may not exist yet)
  3. Annual goals: ~/Documents/YOURNAME/journal/YYYY/goals.md
  4. Life plan: ~/Documents/YOURNAME/plan.md
  5. Inbox: ~/Documents/YOURNAME/inbox.md
  6. Active decisions: Scan ~/Documents/YOURNAME/decisions/ for any decision documents with status "Open" or "Active". Read the most recent or most relevant ones.

Step 2: Review Yesterday

Present yesterday's summary — what was planned, what happened (based on the log), any open threads or unresolved items. Don't just list — reflect. Name what was avoided. Call out patterns.

Then ask the user to walk through yesterday. Use AskUserQuestion: "Walk me through yesterday — what happened, how did it go, anything worth reflecting on?"

Let them talk. Ask follow-up questions. Push back if something sounds like narrative rather than reality. Challenge assumptions.

Watch for emotional signals. Don't ask "how are you feeling?" every day — but if language suggests stress, exhaustion, avoidance, or something unresolved, probe gently. Surface them when you notice them, not as a checkbox.

Update yesterday's journal with reflections:

  • Fill in the Log section with what actually happened
  • Add an Evening/Reflections section if it's missing
  • Mark completed to-dos as done
  • Keep the user's voice — use their language, not polished summaries

Step 3: Review Today's To-Dos

Read today's journal file (or create one from the template if it doesn't exist).

Clean it up:

  • Remove stale carried-over items that are no longer relevant
  • Update Active Projects and Active Decisions to reflect current state

Check inbox (~/Documents/YOURNAME/inbox.md) for items that should be promoted to today.

Present the landscape: carried-over to-dos and any inbox items worth surfacing.

Ask what to focus on today. Offer 2-4 options based on what you see, but let the user override.


Step 4: Alignment Check

This is the critical step. Compare today's planned to-dos against the annual goals checklist and life plan.

4a: Review active decisions

Check any open decision documents loaded in Step 1. Are there action items due this week? Has anything changed since the last update? Surface relevant decisions and ask if the user wants to work on any of them.

Don't force this every day — but if a decision has near-term deadlines or the user signals they've been thinking about it, dig in.

4b: Do today's to-dos ladder up?

For each to-do, ask: does this connect to one of the annual goals? If not, flag it.

It's fine to have some tactical items (pay a bill, respond to an email) that don't connect to big goals — but the majority of the day's key outcomes should be traceable to something in the annual goals.

If they don't align, ask about it using AskUserQuestion. Don't just flag silently — engage: "This doesn't seem to connect to any of your goals. Is this important for a reason I'm missing, or is it noise?"

4c: Are there annual goals with no to-dos?

Look at the annual goals checklist. Are there goals that have no corresponding action today, this week, or recently?

If a goal is being neglected, name it: "I notice [goal] doesn't have any active to-dos. Is that intentional, or should we add something?"

Don't be annoying about this — some goals are seasonal or blocked. But if a goal keeps having no action for weeks, that's a pattern worth naming.

4d: Do the annual goals still ladder up to the life plan?

This doesn't need to happen every day. But if something feels off — a goal that doesn't connect, or a new priority that emerged — flag it and suggest updating the goals or plan.


Step 5: Finalize Today's Journal

Write/update today's journal file with:

markdown
# YYYY-MM-DD

## Morning (Franklin: "What good shall I do this day?")
- [ ] Key outcome 1 (connects to: [annual goal])
- [ ] Key outcome 2
- [ ] Key outcome 3
- [ ] Carried-over items that are still relevant

## Log
-

## Active Projects
1. [current projects]

## Active Decisions
- [ ] [unresolved decisions]

Key details:

  • Key outcomes from the conversation first, then carried-over items
  • Active Projects and Active Decisions should reflect current state

Step 6: Challenge and Close

Before finishing, do a final check:

  • Is the plan too ambitious? If there are more than 3-4 key outcomes, push back. "That's a lot for one day. What's the one thing that matters most?"
  • Is something being avoided? If a hard task keeps not making the list, name it.
  • Any actions for inbox? If the conversation produced tasks that aren't for today, add them to ~/Documents/YOURNAME/inbox.md.

End with a brief, direct summary of the 1-3 things that matter most today.


Throughout the Day

When something is logged or asked to be added to the journal:

  • Read today's file
  • Append a timestamped entry in the Log section: - HH:MM — Entry text

When something log-worthy comes up in conversation:

  • Add it to today's journal and say "Added to log: [brief summary]"
  • No need to ask permission — keep the conversation flowing

Evening (if invoked)

  • Read today's journal file
  • Summarize what was accomplished vs. the morning focus
  • Prompt with Franklin's closing question: "What good have I done today?"
  • Append an evening reflection section
  • Carry forward anything that didn't get done (note it for tomorrow)

Weekly Review (if invoked)

  • Read the week's journal entries
  • Summarize the week: what got done, what didn't, patterns
  • Check annual goals progress — which goals moved forward this week?
  • Name what's being avoided
  • Identify 1-3 priorities for next week

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Morning AI skill do?

Daily journaling, reflection, and planning. Use when user says 'morning', 'let's plan the day', 'journal', or similar. Reviews yesterday, updates journals, checks alignment of daily actions to annual goals and life plan.

Why use Morning on TypingMind?

Because you install it once and use it with any model. Morning is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Morning in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/davidhariri/life-system/tree/main/skills/morning. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Morning?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Morning?

As many as you like. As long as a model supports skills, you can use Morning with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Morning AI skill free?

It is published on GitHub by davidhariri. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇