agentleFS
Sign inStart free
jmlrtjmlrt/skills/englog/SKILL.md

englog

Skill0 starsChanged 4 months agoMITView on GitHub

Read and update the day's time log with the englog CLI. Use when the user asks what they worked on today, to start or stop a time entry, to log a forgotten entry at a past time, or to inspect a daily time file.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use Englog to log the workday as time entries in $ENGLOG_DIR/YYYY-MM-DD.txt.

    line 8
  2. Distinctive:

    Default to read-only access.

    line 9
  3. Very specific:

    Verify a write with englog list.

    line 32
  4. Distinctive:

    If the CLI is unavailable, edit the daily file directly rather than guessing an installation path.

    line 45

≈ “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

Englog

Use Englog to log the workday as time entries in $ENGLOG_DIR/YYYY-MM-DD.txt. Default to read-only access; write only when the user asks.

Read

englog status   # running entry and today's total
englog list     # today's entries with durations

For another day, read $ENGLOG_DIR/YYYY-MM-DD.txt directly.

Write

englog start day prep, check notifs     # ends the running entry; no quotes needed
englog start --at 14:20 1/1 alice       # forgot to log: start at a past time
englog stop                             # or: englog stop --at 17:45
  • Options go before the title: everything after --at HH:MM is the title.
  • Characters the shell treats specially (( ) ; & | < > * ? ' ") still need quoting.
  • --at can't be in the future or earlier than the last line. For any other fix, edit the file directly and keep the lines in time order.
  • Verify a write with englog list.

File format

One HH:MM title line per entry. HH:MM stop ends the running entry (a break, or the end of the day). An entry ends when the next line starts and durations are computed, so never write a duration.

09:00 day prep, check notifs
09:30 1/1 alice
10:00 stop

If the CLI is unavailable, edit the daily file directly rather than guessing an installation path.

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.

Check your setup, free