agentleFS
Sign inStart free
h-watah-wata/claude-skills/skills/work-log/SKILL.md

work-log

Skill0 starsChanged 6 months agoApache-2.0View on GitHub

Log work notes based on the current conversation

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read config.json to get output path

    line 15
  2. Distinctive:

    Create file if it doesn't exist

    line 16
  3. Distinctive:

    Add timestamp heading (HH:MM format)

    line 17
  4. Distinctive:

    Write the memo content in Japanese.

    line 25
  5. Distinctive:

    If $ARGUMENTS is provided, incorporate it as additional context.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 6 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

First, read ~/work/claude-skills/config.json to get the obsidian_daily_path.

Based on the conversation in this thread, create a work log entry.

Output

Append to {obsidian_daily_path}/$(date +%Y-%m-%d).md

Steps

  1. Read config.json to get output path
  2. Create file if it doesn't exist
  3. Add timestamp heading (HH:MM format)
  4. Append to end of file

Content to include

  • What was worked on in this thread
  • What changes were made
  • Key decisions or important points

Write the memo content in Japanese.

If $ARGUMENTS is provided, incorporate it as additional context.

Additional instructions: $ARGUMENTS

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