anombyte93anombyte93/claude-accomplish-skill/SKILL.md

accomplish

Skill1 starsChanged 9 months agoMITView on GitHub

Log an accomplishment to daily accomplishments and session-context. Use when the user wants to record a win, milestone, or personal achievement.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

anombyte93/atlas-ai-skillsedited, first seen Apr 26, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
anombyte93/atlas-ai-skills★ 090% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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

Very specific:
If user provided a description, use it as ACCOMPLISHMENT_TEXT.
line 32
Distinctive:
Keep tone authentic. If they're excited, let it show.
line 62
Very specific:
Only if session_context_path was found:
line 76
Distinctive:
NEVER skip the timestamp
line 94
Distinctive:
NEVER overwrite existing entries — always APPEND
line 95
Very specific:
Default accomplishments directory: ~/.claude/accomplishments/
line 96
Distinctive:
All commands output JSON. Run from any directory.
line 101

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

Accomplish - Daily Accomplishment Logger

Script: ~/.claude/skills/accomplish/script.py handles all file I/O.

Usage

/accomplish <description of what was accomplished>

Execution

STEP 1 — Gather Input

If user provided a description, use it as ACCOMPLISHMENT_TEXT. Otherwise ask:

question: "What did you accomplish?"
header: "Win"
options: []
multiSelect: false

STEP 2 — Gather Context

python3 ~/.claude/skills/accomplish/script.py gather-context

Returns JSON with: date_file, timestamp, daily_path, daily_exists, session_context_path, has_accomplishments_section, git_log, git_diff.

STEP 3 — Build the Entry (AI judgment)

Using ACCOMPLISHMENT_TEXT, git_log, git_diff, and session context, craft:

### TIMESTAMP

**What**: Brief title (from ACCOMPLISHMENT_TEXT)
**Context**: Why this matters — connect to user's journey, business goals, or growth
**Details**: Specifics — repos, files, tools, metrics
**Reflection**: Mirror the user's sentiment genuinely

Keep tone authentic. If they're excited, let it show. If it was hard-won, note the struggle. Include tables if the accomplishment involves structured data.

STEP 4 — Write Daily File

python3 ~/.claude/skills/accomplish/script.py write-entry \
  --file "DAILY_PATH" \
  --entry "FORMATTED_ENTRY" \
  --create  # only if daily_exists is false

STEP 5 — Mirror to Session Context

Only if session_context_path was found:

python3 ~/.claude/skills/accomplish/script.py write-mirror \
  --file "SESSION_CONTEXT_PATH" \
  --line "**TIMESTAMP** - One-liner summary"

STEP 6 — Confirm

Output briefly:

Logged to ~/.claude/accomplishments/DATE_FILE.md
Mirrored to session-context/CLAUDE-activeContext.md

Rules

NEVER skip the timestamp
NEVER overwrite existing entries — always APPEND
Default accomplishments directory: ~/.claude/accomplishments/
Session context mirroring is per-project (wherever session-context/ lives relative to cwd)

Script Reference

All commands output JSON. Run from any directory.

Command	Purpose
`gather-context [--daily-dir DIR] [--project-dir DIR]`	Get date/time (local timezone), git log/diff, file paths and existence flags
`write-entry --file PATH --entry TEXT [--create]`	Write/append formatted entry to daily file
`write-mirror --file PATH --line TEXT`	Append one-liner to Accomplishments section in session-context

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