goals
Skill5 starsChanged 18 days agoMITView on GitHub
Set, review, and update the user's goals. Use when: goals, resolutions, track progress, what am I working toward, or holding me accountable.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- matteotitta/repo-structure-agencytheir own version, first seen Nov 8, 2026
- 0xUrsanomics/utopia-ostheir own version, first seen Nov 1, 2026
- kriscard/Skillstheir own version, first seen Oct 28, 2026
- jaredhhawk/claude-skillstheir own version, first seen Oct 25, 2026
- matteotitta/claude-marketing-contexttheir own version, first seen Oct 15, 2026
- obra/muse-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- alxyrgin/health-os★ 38same name
- dfrysinger/qrspi-plus★ 37same name
- sneakers-the-rat/muse-skills★ 24same name
- obra/muse-skills★ 20same name
- kriscard/Skills★ 15same name
- jacobwell/muse-skills★ 8same name
- matteotitta/claude-marketing-context★ 3same name
- 0xUrsanomics/utopia-os★ 2same name
- matteotitta/repo-structure-agency★ 1same name
- michaelsvanbeek/personal-agent-skills★ 1same name
2 more not listed
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.
In this repository46 other files it gives its agents.
- batchSkill
- best-of-nSkill
- datavizSkill
- debugSkill
- delegateSkill
- dependency-updateSkill
- documentSkill
- documentsSkill
- docxSkill
- fleet-managerSkill
- flightsSkill
- forgetSkill
- frontend-designSkill
- githubSkill
- gmailSkill
- google-calendarSkill
- handoffSkill
- helpSkill
- image-searchSkill
- implementSkill
- interviewSkill
- mcp-builderSkill
- mcp-discoverySkill
- moneySkill
- pdfSkill
- photosSkill
- planSkill
- plugin-creatorSkill
- podcastSkill
- pptxSkill
- presentationsSkill
- releaseSkill
- researchSkill
- reviewSkill
- security-reviewSkill
- shoppingSkill
- simplifySkill
- skill-creatorSkill
- skill-installerSkill
- spotifySkill
- spreadsheetsSkill
- testSkill
- ttsSkill
- verifySkill
- webapp-testingSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
4
Distinctive
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 18
Read the current file before discussing goals.
- Distinctive: line 27
Do not silently rewrite or delete goals.
- Distinctive: line 28
Do not invent goals the user never stated.
- Distinctive: line 29
Do not mix goals with task tracking — goals are outcomes, not todos.
“Common” is measured: kept by at least 6 in 10 of the 11 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.
Files
Goals
When to use
Recording what the user is working toward, reviewing progress, and updating goals as life changes.
Setup
Goals live in $CODEWHALE_HOME/goals.md, one file the user owns. Create it
on first use; fail loud when the home directory is not writable.
Workflow
- Read the current file before discussing goals; quote, don't paraphrase, when reporting status.
- Setting: one goal per line with a measurable target and a date. Confirm the wording with the user before writing.
- Review: compare stated goals against what the user reports; update status lines, never rewrite history — append dated entries.
- Nudge, don't nag: progress check-ins only when the user asks or scheduled.
Non-goals
- Do not silently rewrite or delete goals.
- Do not invent goals the user never stated.
- Do not mix goals with task tracking — goals are outcomes, not todos.
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.