accomplish
Scannednpx machina-cli add skill anombyte93/atlas-ai-skills/accomplish --openclawAccomplish - 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 AEDT
**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 AEDT** - One-liner summary"
STEP 6 — Confirm
Output briefly:
Logged to ~/Hermes/Daily_Accomplishments/DATE_FILE.md
Mirrored to session-context/CLAUDE-activeContext.md
Rules
- NEVER skip the timestamp
- NEVER overwrite existing entries — always APPEND
- Daily_Accomplishments lives at
~/Hermes/Daily_Accomplishments/(FIXED) - 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 | Get date/time (AEDT), 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 |
Source
git clone https://github.com/anombyte93/atlas-ai-skills/blob/main/skills/accomplish/SKILL.mdView on GitHub Overview
Accomplish lets users record wins, milestones, or personal achievements by creating a formatted entry in Daily_Accomplishments and mirroring a concise note to session-context. It guides you from description input through context gathering to a timestamped, append-only log. This creates a persistent, growth-oriented record you can reference later.
How This Skill Works
User provides an accomplishment description (or is prompted for one). The skill gathers context via a script (date/time, git log/diff, and paths), builds a TIMESTAMP AEDT formatted entry with What, Context, Details, and Reflection, then appends it to the daily log file and, if a session-context path exists, mirrors a one-liner there.
When to Use It
- After completing a project milestone or sprint to capture progress.
- When you want to log a daily win or personal achievement for growth tracking.
- To connect an accomplishment to larger goals or metrics you’re pursuing.
- When you’ve overcome a difficult task and want a reflective record.
- When you want to mirror the accomplishment into your project session-context for future chats.
Quick Start
- Step 1: Run /accomplish <description> to provide the accomplishment text or confirm when prompted.
- Step 2: Gather context with: python3 ~/.claude/skills/accomplish/script.py gather-context.
- Step 3: Write the entry and mirror as needed: python3 ~/.claude/skills/accomplish/script.py write-entry --file "DAILY_PATH" --entry "FORMATTED_ENTRY" [--create]; optional: python3 ~/.claude/skills/accomplish/script.py write-mirror --file "SESSION_CONTEXT_PATH" --line "**TIMESTAMP AEDT** - One-liner summary".
Best Practices
- Provide a clear ACCOMPLISHMENT_TEXT to describe What was achieved.
- Link the entry to Context and Details that tie to goals, tools used, and metrics.
- Always include a TIMESTAMP AEDT and never overwrite existing entries; append only.
- Ensure DAILY_PATH exists or use the create option when necessary.
- If available, utilize session-context mirroring to keep a concise summary handy.
Example Use Cases
- What: Launched user onboarding flow; Context: Improved activation rate; Details: updated routes, A/B tests run, metrics captured; Reflection: proud of a polished, user-friendly experience.
- What: Resolved a long-standing bug in the payment module; Context: Stability and reliability goals; Details: reproduced with logs, implemented fix, staged and deployed; Reflection: relief after customer feedback confirmed fix.
- What: Automated daily health checks; Context: Ops reliability; Details: wrote monitoring script, added alerts, reduced incident time; Reflection: automation pays off.
- What: Reached 1000+ commits milestone; Context: personal growth; Details: milestone tag created, commit messages cleaned up; Reflection: consistency paid off.
- What: Documented sprint retro outcomes; Context: team alignment; Details: new wiki pages, actionable items; Reflection: gained clarity and momentum.
