Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Habit Tracker

ASecurity

Design habit systems that stick: habit selection, tracking methods, streaks, environment design, and recovery from slips. Use when building new routines or fixing ones that keep failing.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill habit-tracker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Habit Tracker?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Habit Tracker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-habit-tracker/badge)](https://www.skillsdirectory.com/skills/aicodedecode-habit-tracker)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: habit-tracker
description: Design habit systems that stick: habit selection, tracking methods, streaks, environment design, and recovery from slips. Use when building new routines or fixing ones that keep failing.
category: productivity
---

# Habit Tracker

## Overview

Habits are behaviors on autopilot — the closest thing to free productivity.

Formation loop: cue -> routine -> reward. Tracking adds feedback: the checkmark becomes part of the reward.

Tracking alone doesn't build habits. The habit must be tiny, cue-linked, and rewarding enough to repeat.

Effective systems: 3-7 habits max, seconds-per-day tracking, misses treated as data not failure.

Design for your lowest-energy self. Motivation starts habits; systems sustain them.

## When to use

- Starting new habits (exercise, reading, meditation, writing, languages)
- Breaking bad habits by replacing them with better ones
- Choosing a habit-tracking app or analog method
- Recovering after falling off a routine
- Designing team or family habit challenges

## Core concepts

- **Start ridiculously small.**
  'Read 2 pages' sticks; 'read 20 pages' fails. Initial goal is showing up, not output. Scale after the identity forms.
- **Habit stacking.**
  Attach to an existing habit: 'After coffee, I journal.' Existing habits are the most reliable cues available.
- **Implementation intentions.**
  'I will [behavior] at [time] in [location].' Specificity beats motivation. 'Walk 15 min at 7am' works; 'exercise more' doesn't.
- **Environment design.**
  Good habits obvious (shoes by door), bad habits hard (phone in another room). Willpower is unreliable; friction is forever.
- **Never miss twice.**
  One miss is an accident; two is a new habit of skipping. After a slip, resume immediately — never 'restart Monday.'
- **Identity over outcomes.**
  'I'm a reader' outlasts 'lose 5kg.' Each completion is a vote for the identity. Track the votes.
- **Track, don't judge.**
  The tracker is a dashboard, not a courtroom. Gaps reveal obstacles to design around, not failures to feel bad about.
- **Minimum viable version.**
  Define the bad-day version of each habit explicitly. The 2-minute version keeps the streak of showing up alive.

## Practical workflow

1. **Choose 3-5 habits max.**
   Fewer than you want. Each under 10 minutes initially, with a 2-minute starter version for bad days.
2. **Write implementation intentions.**
   Exact behavior, cue, time, place — plus the minimum version. Vague plans produce vague results.
3. **Pick a tracking method.**
   App, spreadsheet, wall calendar, notebook grid. Under 10 seconds per habit per day, visible, satisfying to mark.
4. **Design the environment first.**
   Change one thing per habit before day one: reduce friction or add a cue. Don't wait to fail first.
5. **Set a weekly review.**
   Which habits are automatic? Which need redesign (size, cue, time) rather than more willpower? Adjust the system.
6. **Handle slips by protocol.**
   Miss once: note cause, resume tomorrow. Miss twice: shrink the habit or change the cue immediately.
7. **Evolve quarterly.**
   Graduate easy habits, retire automatic ones from active tracking, add one new habit at a time. Keep the list short forever.
8. **Pair habits with rewards.**
   After the routine, something genuinely pleasant — even just marking the X. The loop needs its reward to close.

## Common pitfalls

- **Too many habits at once.**
  Ten new habits in January, zero by February. One at a time is faster long-term because it survives.
- **All-or-nothing tracking.**
  Binary pass/fail punishes the 20-minute walk that was still worthwhile. Partial credit keeps showing up alive.
- **Tracking without design.**
  Logging failures for months without changing cue, size, or environment. Data without redesign is a guilt log.
- **Streak obsession.**
  A broken 100-day streak can end the habit ('it's ruined'). Value the 90%-of-days trend over the unbroken chain.
- **Vague habits.**
  'Be healthier' can't be tracked. 'No soda on weekdays' can. No checkmark possible = not a habit yet.
- **Relying on motivation.**
  Design every habit for your busiest, most distracted, lowest-energy self — that's who has to do it.
- **Punishing rest.**
  7-days-a-week with no recovery leads to burnout and abandonment. Schedule rest days deliberately.
- **Copying someone's stack.**
  Borrow principles, not schedules. Build from your life, chronotype, and constraints — not an influencer's routine.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →