habit-tracker
Skill4 starsChanged 4 months agoMITView on GitHub
Maintains a habits.csv log — records daily check-ins, computes streaks with python3, and reads out weekly patterns with compassionate, guilt-free framing. Use when the user says "log my habits", "did my workout", "check in", "how's my streak", "habit report", or wants to start tracking a routine. Don't use for one-off task management or the weekly work review — use weekly-review — or for decision logging — use decision-journal.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- seco/declawtheir own version, first seen Apr 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- seco/declaw★ 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 repository74 other files it gives its agents.
- agent-eval-harnessSkill
- context-budget-managerSkill
- incident-rollbackSkill
- memory-hygieneSkill
- model-cost-optimizerSkill
- prompt-debuggerSkill
- skill-author-coachSkill
- third-party-skill-vetterSkill
- api-endpoint-testerSkill
- bug-triage-protocolSkill
- changelog-release-notesSkill
- docs-readme-writerSkill
- env-secrets-hygieneSkill
- github-pr-reviewSkill
- git-ship-flowSkill
- lovable-brief-writerSkill
- supabase-migration-writerSkill
- vercel-deploy-checkSkill
- cold-outreach-sequencerSkill
- competitor-pricing-scanSkill
- contract-redline-scanSkill
- customer-support-inboxSkill
- invoice-runnerSkill
- kpi-dashboard-weeklySkill
- lead-research-dossierSkill
- payment-reconciliationSkill
- pipeline-trackerSkill
- proposal-builderSkill
- stripe-payment-linkSkill
- testimonial-harvesterSkill
- weekly-revenue-reportSkill
- brand-voice-guardianSkill
- case-study-builderSkill
- content-repurposerSkill
- deep-research-briefSkill
- email-nurture-sequenceSkill
- landing-page-copywriterSkill
- linkedin-content-packSkill
- newsletter-assemblerSkill
- seo-blog-writerSkill
- social-listening-reportSkill
- x-thread-builderSkill
- youtube-script-writerSkill
- budget-guardrailsSkill
- ceo-operating-doctrineSkill
- delegation-protocolSkill
- editor-personaSkill
- heartbeat-standupSkill
- hiring-briefSkill
- ops-agent-personaSkill
- researcher-personaSkill
- sales-agent-personaSkill
- support-agent-personaSkill
- weekly-retroSkill
- writer-personaSkill
- calendar-conciergeSkill
- decision-journalSkill
- email-triageSkill
- file-organizerSkill
- inbox-zero-sprintSkill
- The first 60 shown.
The file
Files
Habit Tracker
Keeps an honest, low-friction habit log in a plain habits.csv and turns it into streaks and weekly patterns the user can actually learn from. The house rule is compassionate framing: a broken streak is data plus a restart plan — never guilt, never "you failed", never streak-shaming. The tool exists to make restarting easy, because restarting is the whole game.
When to Use
- Daily check-in: "log meditation done", "I skipped the run today".
- Status: "what's my streak", "how did this week go", "habit readout".
- Starting or retiring a tracked habit.
- Not for: project tasks or work retrospectives — use
weekly-review. Not for logging choices and their reasoning — usedecision-journal.
Quick Reference
| Action | Command / Call |
| File format | habits.csv header: habit,date,done (date ISO YYYY-MM-DD, done 1/0) |
| Initialize | echo "habit,date,done" > habits.csv (only if missing — never overwrite) |
| Log today | echo "meditation,$(date +%F),1" >> habits.csv |
| Guard against double-log | grep -c "^meditation,$(date +%F)," habits.csv |
| Streaks + weekly pattern | python3 stdlib script (Procedure step 4) |
| List tracked habits | cut -d, -f1 habits.csv | tail -n +2 | sort -u |
Procedure
- Precheck — locate
habits.csv(ask once where it lives, then remember). If missing, offer to create it with the header — append-only from then on; this skill never rewrites or deletes history rows. - Log — for each habit the user reports, first run the double-log guard; if today's row exists, confirm before appending a correction (append a new row rather than editing — last row for a date wins). Append
habit,date,donewithdone=0for an honest skip. Skips get logged too: a0is information, not a verdict. - Confirm the write —
tail -3 habits.csvand echo back what was recorded in one friendly line. Compute — for streaks and the weekly readout:
python3 - <<'EOF' import csv, datetime as dt, collections rows = {} for r in csv.DictReader(open('habits.csv')): rows[(r['habit'], r['date'])] = r['done'].strip() == '1' # last row wins habits = sorted({h for h, _ in rows}) today = dt.date.today() for h in habits: done = {dt.date.fromisoformat(d) for (hh, d), ok in rows.items() if hh == h and ok} streak, day = 0, today if day not in done: day -= dt.timedelta(1) # today not logged yet ≠ broken while day in done: streak += 1; day -= dt.timedelta(1) week = [(today - dt.timedelta(i)) for i in range(6, -1, -1)] bar = ''.join('█' if d in done else '·' for d in week) best = 0; run = 0 for i in range((today - min(done)).days + 1) if done else []: d = min(done) + dt.timedelta(i) run = run + 1 if d in done else 0 best = max(best, run) print(f"{h}: streak {streak} (best {best}) | last 7d {bar} {len([d for d in week if d in done])}/7") EOFSuccess: one line per habit with current streak, best streak, and a 7-day bar.
- Read out, compassionately — report per the template. For any habit at streak 0 that previously had a run: name the restart, not the break — "Meditation paused after 9 days; the 9 days still count. Restart plan: 2 minutes tomorrow after coffee." Pair the habit with an existing anchor and shrink the ask. Look for patterns worth one sentence ("runs happen Mon–Thu, never Fri — plan around that, don't fight it").
Output Template
# Habit Check-in — {date}
Logged: {habit} → {✅ done / ⏭️ skipped (logged, no drama)}
| Habit | Streak | Best | Last 7 days | Week |
|---|---|---|---|---|
| {habit} | {n}d | {n}d | █·███·█ | {n}/7 |
**Pattern worth knowing:** {one observation, stated neutrally}
**Restarts (if any):**
- {Habit}: paused after {n} days — those days banked. Tomorrow: {tiny version} after {existing anchor}.Pitfalls
- Guilt framing sneaks in ("you broke your streak", "only 2/7") — this is the one hard rule of the skill. Recovery: reread the output before delivering; rewrite any judgment language into data + restart plan; "only" and "failed" are banned words here.
- Unlogged today counted as a broken streak — the user checks in at 9 a.m. before doing the habit and their 30-day streak "dies". Recovery: the script already skips today if unlogged; never report a streak break for a day still in progress.
- Editing history instead of appending — rewriting rows corrupts the file's audit trail and risks data loss. Recovery: corrections are new rows (last-wins semantics in the script); if the file was damaged, restore from the most recent copy before continuing.
- Double-logging inflates streaks — two
1rows for the same day are harmless to the script but confusewc -lsanity checks. Recovery: the grep guard in step 2; dedupe awareness lives in the script, not in file surgery.
Verification
- New rows visible via
tailand match what the user reported (including honest0s) - Streak numbers come from the python3 output, not mental math
- Zero guilt language — every paused habit has a concrete, smaller restart plan
- History rows untouched; file only ever appended to
- Header intact: first line of
habits.csvishabit,date,done
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
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.

