agentleFS
freejam099-altfreejam099-alt/Edge-Ai/skills/built-in/mood-tracker/SKILL.md

mood-tracker

Skill0 starsChanged 8 months agoApache-2.0View on GitHub

A simple mood tracking skill that stores your daily mood and comments. Use this when the user wants to log their mood, track how they feel, or see their mood history.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 2

    1. google-ai-edge/gallery★ 25k100% same
    2. jegly/Box★ 995100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository10 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 7 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a user wants to log their mood, call the run_js tool with:

    line 15
  2. Distinctive:

    If user says "today", pass "today".

    line 22
  3. Distinctive:

    If user says "yesterday", pass "yesterday".

    line 23
  4. Distinctive:

    If user gives a specific date (e.g., "March 18"), format it as YYYY-MM-DD or pass the original date string.

    line 24
  5. Distinctive:

    If no date is mentioned, default to "today".

    line 25
  6. Very specific:

    When a user asks what their mood was on a specific date, call the run_js tool with:

    line 28
  7. Very specific:

    When a user wants to see their mood history ("last week", "past 10 days") or the dashboard, call the run_js tool with:

    line 35
  8. Very specific:

    When a user wants to visualize their mood trends with a chart (e.g., "Plot my mood for 7 days"), call the run_js tool with:

    line 43
  9. Distinctive:

    When a user asks for an analysis of their mood (e.g., "Are there any trends?", "Am I feeling better?"), follow these steps:

    line 52
  10. Very specific:

    Call run_js with action: "get_history" and an appropriate days count (e.g., 30 for a monthly analysis).

    line 53
  11. Very specific:

    When a user wants to delete only a single day's entry (e.g., "Delete my mood for today"), call the run_js tool with:

    line 61
  12. Very specific:

    When a user wants to backup or export their data, call the run_js tool with:

    line 68
  13. Very specific:

    When a user wants to clear their entire mood history and start fresh, call the run_js tool with:

    line 74
  14. Distinctive:

    Privacy: All data is stored locally on your device.

    line 120
  15. Distinctive:

    No Entry: If no mood entry exists for a specific date requested, explicitly inform the user that no entry was found for that date.

    line 121

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Mood Tracker

Instructions

The mood-tracker skill helps you keep track of your daily emotional well-being. You can log your mood on a scale of 1 to 10 and add a short comment about how you're feeling.

Actions

1. Log Mood

When a user wants to log their mood, call the run_js tool with:

  • script name: index.html
  • data: A JSON string with:
    • action: "log_mood"
    • score: Number (1-10)
    • comment: String (Optional)
    • date: String. IMPORTANT: Identify the date for the entry.
      • If user says "today", pass "today".
      • If user says "yesterday", pass "yesterday".
      • If user gives a specific date (e.g., "March 18"), format it as YYYY-MM-DD or pass the original date string.
      • If no date is mentioned, default to "today".

2. Get Mood for a Specific Date

When a user asks what their mood was on a specific date, call the run_js tool with:

  • script name: index.html
  • data: A JSON string with:
    • action: "get_mood"
    • date: String (Identify the date from the user's request)

3. Get History / Show Dashboard

When a user wants to see their mood history ("last week", "past 10 days") or the dashboard, call the run_js tool with:

  • script name: index.html
  • data: A JSON string with:
    • action: "get_history"
    • days: Number (Optional, default 7. E.g., for "last week" use 7)
    • show_dashboard: Boolean (Optional)

4. Plot Mood Trends (Line Chart)

When a user wants to visualize their mood trends with a chart (e.g., "Plot my mood for 7 days"), call the run_js tool with:

  • script name: index.html
  • data: A JSON string with:
    • action: "get_history"
    • days: Number (Optional, default 7)
    • show_dashboard: true
    • TIP: This will trigger the plotting view in the dashboard.

5. Analyze Trends and Patterns

When a user asks for an analysis of their mood (e.g., "Are there any trends?", "Am I feeling better?"), follow these steps:

  1. Call run_js with action: "get_history" and an appropriate days count (e.g., 30 for a monthly analysis).
  2. Once you receive the JSON history, analyze the scores and comments.
  3. Provide a thoughtful response to the user covering:
    • General trend (improving, declining, stable).
    • Any clusters of particularly good or bad days.
    • Themes or patterns found in the comments.

6. Delete Mood for a Specific Date

When a user wants to delete only a single day's entry (e.g., "Delete my mood for today"), call the run_js tool with:

  • script name: index.html
  • data: A JSON string with:
    • action: "delete_mood"
    • date: String (Identify the date)

7. Export Data (Backup)

When a user wants to backup or export their data, call the run_js tool with:

  • script name: index.html
  • data: A JSON string with:
    • action: "export_data"

8. Wipe All Data

When a user wants to clear their entire mood history and start fresh, call the run_js tool with:

  • script name: index.html
  • data: A JSON string with:
    • action: "wipe_data"

Sample Commands

You can use these samples to interact with the mood tracker:

  • Logging Mood:
    • "Log my mood as 8 today, feeling great!"
    • "Set my mood yesterday as a 2"
    • "Set my mood on March 18, 2026 as a 1"
    • "I'm feeling like a 5 today, a bit tired."
    • "Last Friday I felt like a 7."
    • "Record a mood of 9 for me."
  • Viewing History:
    • "Show me my mood history."
    • "Get my mood from last week."
    • "How have I been feeling lately?"
    • "Show my mood for the last 10 days."
    • "Open the mood dashboard."
    • "What was my mood on March 18?"
    • "What was my mood yesterday?"
  • Analyzing Trends:
    • "Analyze my mood for the last 30 days — are there any patterns?"
    • "Am I generally feeling better or worse over time?"
    • "Are there any clusters of bad days in my history?"
    • "What do my recent comments suggest about my well-being?"
  • Wiping & Deleting:
    • "Delete my mood for today."
    • "Remove my mood log for yesterday."
    • "Delete the entry for March 18."
    • "Clear my mood history." (Use wipe_data for this)
    • "Wipe my data." (Use wipe_data for this)
  • Charting Trends:
    • "Plot my mood for the last 7 days."
    • "Show me a chart of my mood this month."
    • "Visualize my scores for the past 14 days."
    • "Graph my mood progress."

Rules

  • Privacy: All data is stored locally on your device.
  • No Entry: If no mood entry exists for a specific date requested, explicitly inform the user that no entry was found for that date.
  • Updates: Logging a mood for a date that already has an entry will update that entry.
  • Dashboard: The dashboard is only shown when you explicitly ask to see your history or the dashboard itself.

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.