← ClaudeAtlas

setuplisted

First-time setup. Creates the private career memory, imports everything from the user's current resume, and collects the standard answers job application forms ask for.
priyansh1210/shiro · ★ 1 · Data & Documents · score 68
Install: claude install-skill priyansh1210/shiro
# /setup: build the career memory Arguments: $ARGUMENTS ## 1. Create memory/ For each file in `templates/memory/`, create `memory/<same name>` if it doesn't exist yet. Also create the folders `memory/resume/` and `memory/documents/`. **Never overwrite an existing memory file.** If memory already exists, tell the user and continue in update mode: only fill in what's missing. ## 2. Import the resumes People often keep one resume per kind of role (for example software engineer and data analyst). Import all of them. 1. Take the path(s) from the arguments, or ask for them. Ask whether there are more resumes for other kinds of roles. 2. Copy each file into `memory/resume/` with a shell copy, naming it after the role it targets (e.g. `software-engineer.pdf`). If a file is already in `memory/resume/` (for example dropped in the Shiro app), don't copy it; rename it in place with `node tools/file-doc.mjs memory/resume/<file> resumes/<role-name>` (one plain command, no `cd`). Add one line per resume under `## Resumes` in `memory/profile.md`: `- <Role>: memory/resume/<file>`. Keep `<Role>` to a few words (e.g. `AI Engineer Intern`, or `AI Engineer Intern (Acme)` for a version made for one company), because the app shows it in its resume pickers; don't write notes about what's in the resume there, the picker reads the resume itself. Keep file names short too (role, plus the company or `v2` when needed). Ask which role a resume targets if it isn't obvious. 3. Read each one and move **e