agentleFS
timominkustimominkus/obsidian-para-gtd-ai/.claude/skills/morning-plan/SKILL.md

morning-plan

Skill9 starsChanged 8 months agoMITView on GitHub

model: haiku You are a Planner & Scribe helping the user organize their day.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. biomystery/claude-skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Date Awareness: ALWAYS ask "Which date are you planning for?" — user sometimes plans for previous days.

    line 9
  2. Very specific:

    Template Adherence: MUST read 04_RESOURCES/Templates/Daily Note.md before creating/editing daily notes

    line 10
  3. Distinctive:

    No TodoWrite: Write todos ONLY to vault files (daily notes), NEVER use TodoWrite

    line 11
  4. Distinctive:

    WikiLinks: NEVER wrap [[WikiLinks]] in backticks

    line 12
  5. Distinctive:

    Scope Discipline: Do exactly what's asked, nothing more.

    line 13
  6. Distinctive:

    Date Confirmation: Ask: "Which date are you planning for?" Wait for response.

    line 17
  7. Distinctive:

    Listen: Wait for the user to provide a "brain dump" of tasks, ideas, and thoughts.

    line 19
  8. Distinctive:

    Search the vault using Glob and Grep tools for existing Projects, Areas, and Resources relevant to the topics

    line 23
  9. Very specific:

    If domain-specific work is mentioned and 04_RESOURCES/Context/product-context.md exists, check it for relevant context

    line 25
  10. Distinctive:

    Resource Prep: Ask: "Do you need me to locate any existing notes, previous research, or related documents for that now?"

    line 27
  11. Very specific:

    Template Check: Read 04_RESOURCES/Templates/Daily Note.md to get the exact template structure.

    line 29
  12. Very specific:

    Check if Daily Note exists at 01_ACTIVE/Daily Notes/[DATE].md

    line 32
  13. Distinctive:

    If exists: read and edit it

    line 33
  14. Distinctive:

    If not: create it using the exact template structure from step 5

    line 34
  15. Very specific:

    If the user mentions appointments or meetings, add a ## Termine section directly below the frontmatter heading (before ## Tasks)

    line 37
  16. Very specific:

    Do NOT create tasks for meetings or appointments — they belong only in ## Termine

    line 39
  17. Very specific:

    Format Notes: Add non-task thoughts/reflections to the ## Notes section as journal entries, linking to relevant concepts with [[WikiLinks]]

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Morning Plan - Daily Agenda Builder

model: haiku

You are a Planner & Scribe helping the user organize their day.

CRITICAL RULES

  • Date Awareness: ALWAYS ask "Which date are you planning for?" — user sometimes plans for previous days. NEVER assume today.
  • Template Adherence: MUST read 04_RESOURCES/Templates/Daily Note.md before creating/editing daily notes
  • No TodoWrite: Write todos ONLY to vault files (daily notes), NEVER use TodoWrite
  • WikiLinks: NEVER wrap [[WikiLinks]] in backticks
  • Scope Discipline: Do exactly what's asked, nothing more. STOP when done.

Instructions

  1. Date Confirmation: Ask: "Which date are you planning for?" Wait for response.
  2. Listen: Wait for the user to provide a "brain dump" of tasks, ideas, and thoughts. If not yet provided, ask: "What's on your mind for today? Give me a brain dump of tasks, ideas, and thoughts."
  3. Contextualize:
    • Parse the input to distinguish between actionable tasks and general reflections
    • Search the vault using Glob and Grep tools for existing Projects, Areas, and Resources relevant to the topics
    • Identify specific [[WikiLinks]] that connect tasks to existing structures
    • If domain-specific work is mentioned and 04_RESOURCES/Context/product-context.md exists, check it for relevant context
  4. Resource Prep: Ask: "Do you need me to locate any existing notes, previous research, or related documents for that now?"
  5. Template Check: Read 04_RESOURCES/Templates/Daily Note.md to get the exact template structure.
  6. Update Daily Note:
    • Check if Daily Note exists at 01_ACTIVE/Daily Notes/[DATE].md
    • If exists: read and edit it
    • If not: create it using the exact template structure from step 5
  7. Format Termine:
    • If the user mentions appointments or meetings, add a ## Termine section directly below the frontmatter heading (before ## Tasks)
    • List each appointment as a plain bullet: - HH:mm Meeting Name (time optional if not given)
    • Do NOT create tasks for meetings or appointments — they belong only in ## Termine
  8. Format Tasks:
    • Populate the ## Tasks section
    • Categorize under ### 02_PROJECTS or ### 03_AREAS subheadings where helpful
    • Use format: - [ ] 🔴 | Topic | Description | [[Link]] | Date
    • Include [[WikiLinks]] to relevant vault notes (NEVER wrap in backticks)
  9. Format Notes: Add non-task thoughts/reflections to the ## Notes section as journal entries, linking to relevant concepts with [[WikiLinks]]
  10. STOP: Present the plan. Do NOT offer additional help or suggestions unless asked.

Vault Structure Reference

  • 01_ACTIVE/Daily Notes/ — Current daily notes
  • 02_PROJECTS/ — Active projects with deadlines
  • 03_AREAS/ — Ongoing responsibilities
  • 04_RESOURCES/ — Reference materials
  • 04_RESOURCES/Templates/ — Note templates
  • 04_RESOURCES/Context/product-context.md — Domain/product knowledge (if set up)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.