agentleFS
leoleolroleoleolro/career-os/.claude/skills/log/SKILL.md

log

Skill0 starsChanged 55 days agoMITView on GitHub

Log something the candidate did or learned at work into the achievements file and turn it into a resume bullet. Use when the candidate says "log", "I did X today", "add to my resume", "I learned", "I built", "/log".

19 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

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask at most 2 clarifying questions if the impact or scale is missing (who was it for, what changed, any number: hours saved, users, …

    line 8
  2. Very specific:

    Only after the candidate says yes: edit master-resume.md.

    line 12
  3. Very specific:

    If the achievement is a good interview story, add a stub to profile/story-bank.md (STAR skeleton with [FILL] markers).

    line 13
  4. Very specific:

    Never embellish. If the candidate describes something small, log it small — the file is a diary, not a brochure.

    line 15

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

/log <what happened>

  1. Ask at most 2 clarifying questions if the impact or scale is missing (who was it for, what changed, any number: hours saved, users, records, revenue, defects). Skip if they gave enough.
  2. Append to profile/achievements.md under the current year: - <YYYY-MM-DD> — <what> — impact: <…> — skills: <…> — client: <generalised>
  3. Propose one resume bullet (verb + what + tool + outcome; ≤ 2 lines; no jargon they can't defend in an interview) and say which section of profile/master-resume.md it belongs in and whether it should replace a weaker bullet there.
  4. Only after the candidate says yes: edit master-resume.md. If the bullet touches a skill not yet listed, add it to the Skills block too. If it's a new cert, update profile/certifications.md as well.
  5. If the achievement is a good interview story, add a stub to profile/story-bank.md (STAR skeleton with [FILL] markers).

Never embellish. If the candidate describes something small, log it small — the file is a diary, not a brochure; /tailor chooses what to surface.

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.