remember
Skill1 starsChanged 9 days agoMITView on GitHub
Save a new career fact to the candidate's memory. Covers a new or finished job or internship, a course, certificate, project, skill, award, education update, changed contact details or status, an answer to an application question, or an application status update. Use whenever the user mentions something like this, even in passing.
70 other projects use a version of this.
Adopted by
Most recently taken up by
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- cristobaltormo/cortex-mdtheir own version, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- jsmastery-pro/jsm-hqtheir own version, first seen Nov 8, 2026
- ArcticFox2029/chamnantheir own version, first seen Nov 5, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.
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.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions70 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 70
- github/awesome-copilot★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- langchain-ai/deepagents★ 31ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- H-mmer/pentest-agents★ 815same name
- SparkDevNetwork/Rock★ 701same name
60 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.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 62 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
If that's empty, use what the user just said in the conversation.
- Distinctive: line 62
If it's ambiguous (two projects match, or it's unclear whether to remove a whole entry or just one detail), ask one short question and stop.
- Distinctive: line 63
Remove it: delete whole entries, or just the detail, as asked.
- Very specific: line 68
If memory/ doesn't exist, create it first by copying every file from templates/memory/.
- Distinctive: line 69
Read the target file(s) and follow the format shown in each file's template comment.
- Distinctive: line 70
Update, don't duplicate: If the item already exists (same company, course or project), update it.
- Very specific: line 72
Write the change. Keep entries newest first.
- Distinctive: line 76
Never store passwords, government ID numbers (SSN, Aadhaar, PAN, passport) or bank details.
“Common” is measured: kept by at least 6 in 10 of the 62 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
/remember: update the career memory
What to remember: $ARGUMENTS
If that's empty, use what the user just said in the conversation. If there's nothing there either, ask what's new.
Where things go
| Fact | File |
| Job, internship, freelance, research, volunteering | memory/experience.md |
| Degree, school, GPA, coursework, exchange | memory/education.md |
| Personal, academic, hackathon or open-source project | memory/projects.md |
| Certificate, online course, bootcamp, training | memory/certifications.md |
| Skill, tool, language, framework (and where it was used) | memory/skills.md |
| Award, hackathon result, publication, talk, leadership, club | memory/achievements.md |
| Contact, links, location, work authorization, availability, salary, self-ID choices, form defaults | memory/profile.md |
| A new base resume for a kind of role | memory/resume/ + a line under ## Resumes in memory/profile.md |
| A file a form might ask for: certificate, transcript, degree, recommendation letter, portfolio, writing or work sample | its section folder under memory/documents/ + an entry under its heading in memory/documents.md (see below) |
| A link: portfolio, credential verification, project demo, publication | ## Links in memory/documents.md, plus the related entry |
| Answer to an application question | memory/answers.md |
| Application submitted, interview, rejection, offer | memory/applications.md |
One fact can touch several files. A finished internship updates experience.md (end date, results) and skills.md (new tools, "used at <company>"). Finishing a degree updates education.md and the status in profile.md.
Files and links: identify, sort, record
Memory must stay tidy. Every file is identified, renamed clearly and moved into its section. Nothing stays loose in memory/documents/; files sitting directly there are the new, unfiled ones.
| What it is | Folder | Heading in memory/documents.md |
| Course or professional certificate | memory/documents/certificates/ | ## Certificates |
| Transcript, degree certificate, mark sheet | memory/documents/academic/ | ## Academic |
| Recommendation, experience or internship-completion letter | memory/documents/letters/ | ## Letters |
| Portfolio, writing sample, work sample, case study | memory/documents/portfolio/ | ## Portfolio & samples |
| Cover letter | memory/documents/cover-letters/ | ## Cover letters |
| A resume | memory/resume/ (section resumes), short name like ai-engineer-intern-acme | none; add a line - <Role>: <path> under ## Resumes in profile.md, with <Role> kept to a few words (e.g. AI Engineer Intern (Acme)) and no notes on its contents |
| Anything else useful for forms, or unclear | memory/documents/other/ | ## Other files |
| Same document as one already filed | memory/documents/duplicates/ | none; add - Duplicate copy (safe to delete): <path> to the original's entry |
For each new file:
- A path outside the project (e.g.
C:\Downloads\cert.pdf): copy it intomemory/documents/with a shell copy. If you can't (for example in the Shiro app), ask the user to drop it into the app's Memory tab. - Identify it by reading it (PDFs and images can be read directly). If
documents.mdor another memory file already describes this exact file, don't read it again; just sort it. - Move and rename it with Shiro's tool, as one plain command with no
cd. Several files can go in one command:node tools/file-doc.mjs <file> <section>/<clear-name> [<file> <section>/<clear-name> ...]Clear names are lowercase with hyphens: issuer, title, year-month, e.g.coursera-google-data-analytics-2026-10. The tool keeps the extension, never overwrites, and prints each new path. Use the printed paths. - An HTML file (e.g. a saved certificate page): after moving it, make a PDF next to it, because forms want PDFs:
node tools/html-to-pdf.mjs <file>.html <file>.pdf. Record the PDF as the file. - Record it under its heading in
memory/documents.md(the template comment there shows the fields), and put its facts in the related memory file: a certificate also goes incertifications.md(issuer, date, credential ID, verification link, skills), a transcript can fill GPA and coursework ineducation.md, a letter goes with its role inexperience.md, and the skills it proves go inskills.md. - Identity or bank documents (passport, Aadhaar, PAN, driver's license, bank statements): don't file them. Leave them where they are and tell the user to delete them, since Shiro never uploads them.
- In your reply, list what each file turned out to be and where it went, grouped by section.
Links: work out what the link is (open it with WebFetch if the URL and the user's note don't make it clear). Add it under ## Links in documents.md with its type, and to the related entry: a credential link in certifications.md, a demo in projects.md, a portfolio under Links in profile.md. Don't add a link that's already there.
Forgetting (when the request starts with FORGET:, or the user asks to remove something)
The user wants something out of memory: a wrong fact, an old project, a skill they don't want claimed.
- Find every place it appears: search all of
memory/*.md(Grep), including mentions inside other entries (a project named inskills.md"used in:", a certificate's line indocuments.md, a resume line inprofile.md). - If it's ambiguous (two projects match, or it's unclear whether to remove a whole entry or just one detail), ask one short question and stop.
- Remove it: delete whole entries, or just the detail, as asked. When a skill's only evidence was the removed item, remove that skill too; otherwise only drop the reference. Leave template comments and headings alone.
- Files: don't delete files yourself. If the item has a file in
memory/documents/ormemory/resume/, tell the user they can remove it with the bin icon in the Memory tab (that keeps an Undo). - Set
Last updated:inprofile.mdto today, then say in 1–3 lines exactly what was removed and from which files. Never add anything new while forgetting.
Steps
- If
memory/doesn't exist, create it first by copying every file fromtemplates/memory/. If it exists, create any template file that's missing (for exampledocuments.md) and thememory/documents/folder. - Read the target file(s) and follow the format shown in each file's template comment.
- Update, don't duplicate. If the item already exists (same company, course or project), update it. For example, an internship marked "Present" gets an end date.
- If details that matter for resumes and forms are missing (dates, issuer, credential link, what they did, tools, results with numbers), ask for them in one short message. If the user doesn't know or skips, save what you have and leave those fields blank. Never fill in guesses.
- Write the change. Keep entries newest first. Then set
Last updated:under## About this memoryinmemory/profile.mdto today's date (YYYY-MM-DD).- Conflicts: memory is the source of truth. Only replace a memory fact with a resume's version when the resume is newer than
Last updatedand memory doesn't cover it yet; otherwise keep memory's version. Among resumes, theReference resumeinprofile.mdwins.
- Conflicts: memory is the source of truth. Only replace a memory fact with a resume's version when the resume is newer than
- Confirm in 1–3 lines what was saved and where. If it answers a question in a
runs/*/questions.md, say so, and that the next/reviewwill use it.
Never store passwords, government ID numbers (SSN, Aadhaar, PAN, passport) or bank details. If the user gives one, don't save it and tell them why.
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.

