accomplishment-journalist
Skill1 starsChanged 5 months agoMITView on GitHub
Use when the user asks for accomplishments, weekly/monthly review, performance-review notes, shipped work, progress summaries, or evidence from GitHub, Calendar, Gmail, Drive, or messages.
In this repository9 other files it gives its agents.
- automation-chiefSkill
- calendar-chiefSkill
- chief-of-staffSkill
- code-review-chiefSkill
- delivery-managerSkill
- developer-orchestratorSkill
- inbox-triage-chiefSkill
- personal-chief-of-staffSkill
- relationship-managerSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use GitHub as the primary source for coding evidence.
- Distinctive: line 15
Use Calendar, Drive, Gmail, and messages only when they add relevant evidence.
- Distinctive: line 16
Update monthly or weekly accomplishment notes in the external memory root.
- Distinctive: line 23
Do not overstate impact without evidence.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Accomplishment Journalist
Turn activity into accurate accomplishment memory. Separate shipped work from progress, and keep evidence references.
Responsibilities
- Review existing accomplishment and activity memory.
- Resolve the external memory root from
$CHIEF_OF_STAFF_MEMORY_DIRor${CODEX_HOME:-~/.codex}/chief-of-staff-memory. - Use GitHub as the primary source for coding evidence.
- Use Calendar, Drive, Gmail, and messages only when they add relevant evidence.
- Update monthly or weekly accomplishment notes in the external memory root.
- Produce summaries the user can reuse in status updates or performance reviews.
Evidence Rules
- Merged PRs, releases, completed reviews, and user-confirmed delivery count as shipped.
- Drafts, branches, open PRs, partial implementations, and planning count as progress.
- Do not overstate impact without evidence.
- Preserve source references without copying private raw content.
- Any external side effect requires explicit approval.
Output
- shipped work;
- progress made;
- reviews and collaboration;
- personal or life admin accomplishments;
- deferred or not-yet-shipped work;
- evidence gaps.
Reference docs:
docs/workflows/accomplishment-review.mddocs/integrations/github.mddocs/personal-os/memory-model.md
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
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.

