agentleFS
SkillMedevSkillMedev/personal-operating-system/skills/habit-builder/SKILL.md

habit-builder

Skill1 starsChanged 39 days agoMITView on GitHub

Turns a vague intention into a one-page habit plan - a specific implementation intention, a habit-stack anchor sentence, cue-craving-routine-reward loop mapping, environment design, a never-miss-twice tracking method, and weekly review questions. Use when someone says "help me build a habit", "I want to exercise more but can't stick with it", "why do my habits keep failing", or wants to break a bad habit by removing its cues. Do NOT use for goal-setting with an accountability structure - use goals-accountability instead; for a full training program, use fitness-program.

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use 0-template, github-actions-builder and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JayRHaSkill

    0-template

    Template for creating a new Agent Skill. Copy this folder, rename it to your skill's kebab-case name, and fill in every section. Use this as the starting point whenever you author a new skill for the AgentSkills library.

    Also in 3 projects that use this

  • JayRHaSkill

    github-actions-builder

    Builds reliable, fast, and secure GitHub Actions CI/CD workflows with dependency caching, build matrices, scoped secrets, concurrency control, and reusable/composite workflows. Use this skill when the user asks to "create a GitHub Actions workflow", "set up CI", "add CI/CD", "fix a flaky/slow GitHub Actions pipeline", "add a build matrix", "cache dependencies in CI", "write a reusable workflow", "configure deployment with environments and secrets", or mentions files under .github/workflows.

    Also in 3 projects that use this

  • xcrrrSkill

    proofreader

    Use this skill when reviewing written content for grammar, spelling, punctuation, style consistency, and tone—before publishing, submitting, or sending. Trigger phrases: 'proofread this', 'check my writing', 'review this for errors', 'edit this email/report/essay'. Do NOT use when structural rewrites or content changes are needed—proofreading fixes surface errors, not substantive problems.

    Also in 3 projects that use this

  • xmqywxSkill

    meeting-summarizer

    Transform meeting transcripts into structured summaries with action items, decisions, follow-ups, and efficiency analysis. Works with any meeting format.

    Also in 3 projects that use this

  • MehdibargachSkill

    okr-writer

    Turn business goals into structured OKRs with measurable Key Results, linked initiatives, alignment check, and anti-goals. Takes a strategic priority and outputs ready-to-use OKRs.

    Also in 3 projects that use this

  • +7 more from JayRHa

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to turn a vague intention ("exercise more") into a concrete, trackable habit system.

    line 12
  2. Distinctive:

    Every habit has four parts.

    line 21
  3. Distinctive:

    Use the format: "I will [BEHAVIOR] at [TIME] in [LOCATION]." Example: "I will meditate for 2 minutes at 7:00am in my bedroom." Specificity …

    line 28
  4. Distinctive:

    Use a simple streak tracker (calendar X's or a habit app).

    line 44
  5. Distinctive:

    Never miss twice. One miss is an accident.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Habit Builder

Note: This is general self-improvement education, not professional, medical, or psychological advice. Consult a qualified professional for clinical concerns.

Use this skill to turn a vague intention ("exercise more") into a concrete, trackable habit system.

1. Define the target behavior

Make it specific and small. Bad: "read more." Good: "read one page after I pour my morning coffee." Ask the user:

  • What is the smallest version of this habit that still counts? (the "two-minute rule")
  • What identity does this habit reinforce? ("I am someone who reads daily")

2. Map the habit loop

Every habit has four parts. Fill each one in explicitly:

  • Cue: the trigger that starts the behavior (time, location, preceding action, emotional state).
  • Craving: the motivation or anticipated reward.
  • Routine: the action itself, kept minimal.
  • Reward: the satisfying payoff that closes the loop.

3. Write an implementation intention

Use the format: "I will [BEHAVIOR] at [TIME] in [LOCATION]." Example: "I will meditate for 2 minutes at 7:00am in my bedroom." Specificity dramatically increases follow-through versus a generic goal.

4. Stack the habit

Anchor the new habit to a stable existing routine: "After I [CURRENT HABIT], I will [NEW HABIT]." Example: "After I brush my teeth at night, I will lay out tomorrow's workout clothes." Chain no more than one new habit per anchor at first.

5. Design the environment

  • Make good habits obvious: put the cue in your line of sight (book on pillow, water bottle on desk).
  • Make them easy: reduce friction (gym bag packed the night before).
  • Make bad habits invisible and hard: remove the cue, add friction (log out of distracting apps).

6. Track without perfectionism

Use a simple streak tracker (calendar X's or a habit app).

  • Never miss twice. One miss is an accident; two starts a new (bad) pattern.
  • Track the action, not the outcome. "Did I show up?" beats "Did I hit my goal?"

7. Review weekly

Each week, ask:

  • Did I complete the habit at least 5 of 7 days?
  • Was the cue reliable? If not, pick a stronger anchor.
  • Was the routine too big? Shrink it until it is effortless.
  • Is the reward still satisfying? If not, add an immediate reinforcement.

8. Scale gradually

Once a habit is automatic (typically 4-8 weeks), increase difficulty by ~10% or add a second stacked habit. Avoid scaling more than one habit at a time.

Output for the user

Produce a one-page plan containing: the implementation intention, the habit stack sentence, the environment changes, the tracking method, and the weekly review questions.

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.