personalize
Skill2 starsChanged 8 months agoMITView on GitHub
This skill should be used when the user asks to "personalize", "set up", "get started", "configure my profile", "add a story", "update my targets", or "change my writing framework". First-time setup or incremental updates to the knowledge base. Detects whether this is a new setup or a returning user. Only runs when explicitly requested.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- duncan-buildroom/profit-room-skillstheir own version, first seen Oct 13, 2026
- duncan-buildroom/freeskillstheir own version, first seen Oct 13, 2026
- chenson42/stackkeeltheir own version, first seen Sep 22, 2026
- aleksander-dytko/ai-pm-workspacetheir own version, first seen Feb 27, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- duncan-buildroom/freeskills★ 65same name
- aleksander-dytko/ai-pm-workspace★ 34same name
- duncan-buildroom/profit-room-skills★ 18same name
- chenson42/stackkeel★ 1same name
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 repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- coffee-chatSkill
- company-researchSkill
- discoverSkill
- fit-analysisSkill
- follow-upSkill
- interview-debriefSkill
- interview-prepSkill
- mock-interviewSkill
- negotiateSkill
- offer-analysisSkill
- pipeline-statusSkill
- write-applicationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
33 rules. 0 are common, 27 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
27
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Check if knowledge/profile.md exists.
- Very specific: line 36
If it DOES exist → Returning User: Read knowledge/profile.md and show:
- Very specific: line 58
If the user specified a section in their command (e.g., /personalize stories), skip the menu and go directly to that section.
- Distinctive: line 60
When updating an existing section, read the current file first, show what's there, then ask what to change.
- Distinctive: line 90
If the user says "quick setup", "fast", or seems pressed for time:
- Distinctive: line 91
Ask for resume only
- Distinctive: line 94
Create sensible defaults for writing framework and negotiation
- Distinctive: line 101
After each step, confirm what was saved before moving to the next.
- Distinctive: line 107
Ask: "Drop your resume here (PDF, or paste the text)."
- Distinctive: line 108
If PDF: read and extract key facts
- Distinctive: line 109
If text: parse directly
- Distinctive: line 117
Ask these one at a time:
- Very specific: line 135
If the user has more stories later: /personalize stories to add more.
- Distinctive: line 141
Ask: "Do you have a communication framework or writing style you follow?"
- Distinctive: line 145
If they say "I don't have one": ask for a writing sample and reverse-engineer their style
- Distinctive: line 153
Ask: "Share 1-2 pieces of writing you're proud of — or say 'skip' and I'll work from your writing framework."
- Very specific: line 155
If provided: save to knowledge/voice/samples.md with a voice profile analysis at the top.
- Distinctive: line 156
If skipped: note "No voice samples yet."
- Distinctive: line 162
Ask one at a time:
- Distinctive: line 174
Ask: "Is there a personal story, value, or motivation that drives your career?
- Very specific: line 176
If shared: save to knowledge/values/personal.md with guidance on when to use each element.
- Distinctive: line 177
If skipped: create a minimal file.
- Distinctive: line 183
If pipeline-data.md doesn't exist, create it using the template.
- Distinctive: line 184
If it already exists, skip this step.
- Distinctive: line 190
Ask: "Want daily check-ins?
- Distinctive: line 192
If yes: create scheduled tasks with CronCreate.
- Distinctive: line 217
Resume won't parse: Ask the user to paste the text directly instead of uploading a file.
- Distinctive: line 218
User gives very short answers: Ask follow-ups — "Can you give me a specific example?"
- Distinctive: line 235
Ask follow-ups if answers are too short.
- Distinctive: line 236
Never skip profile.md or resume — these are required for first-time setup
- Distinctive: line 238
Create all directories that don't exist yet
- Distinctive: line 240
When updating, always show current state before asking what to change
- Distinctive: line 241
Never overwrite existing files without showing the user what will change
“Common” is measured: kept by at least 6 in 10 of the 4 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
/personalize
Usage
/personalize # Auto-detect: new setup or update menu
/personalize quick # First-time: fast setup from resume
/personalize full # First-time: complete 9-step walkthrough
/personalize stories # Update: add or edit stories only
/personalize profile # Update: change targets, pillars, situation
/personalize negotiation # Update: adjust comp targets or priorities
/personalize framework # Update: revise writing frameworkBefore Anything Else: Detect State
Check if knowledge/profile.md exists.
If it does NOT exist → First-Time Setup (quick or full mode below).
If it DOES exist → Returning User. Read knowledge/profile.md and show:
Welcome back, [Name]! Here's your current setup:
knowledge/
├── profile.md ✅ [pillars summary]
├── resume/ ✅ / ❌
├── stories/ ✅ [N] stories
├── frameworks/ ✅ [framework name]
├── voice/ ✅ / ⏭️ Not set up
├── negotiation/ ✅ / ⏭️ Not set up
└── values/ ✅ / ⏭️ Not set up
What would you like to update?
- "Add a new story" → I'll walk you through STAR format
- "Update my targets" → Change target roles or companies
- "Change my comp range" → Update negotiation preferences
- "Redo everything" → Full setup from scratch
- Or tell me what's changed and I'll figure out which section to updateIf the user specified a section in their command (e.g., /personalize stories), skip the menu and go directly to that section.
When updating an existing section, read the current file first, show what's there, then ask what to change. Never overwrite without showing current state.
How It Works (First-Time Setup)
┌─────────────────────────────────────────────────────────┐
│ PERSONALIZE │
├─────────────────────────────────────────────────────────┤
│ QUICK (5 min): Resume → auto-generate everything │
│ FULL (20 min): Walk through 9 steps conversationally │
│ │
│ Step 1: Resume → knowledge/resume/ │
│ Step 2: Profile → knowledge/profile.md │
│ Step 3: Stories (STAR) → knowledge/stories/ │
│ Step 4: Writing style → knowledge/frameworks/ │
│ Step 5: Voice samples → knowledge/voice/ (optional) │
│ Step 6: Negotiation → knowledge/negotiation/ │
│ Step 7: Values → knowledge/values/ (optional) │
│ Step 8: Pipeline setup → pipeline-data.md │
│ Step 9: Daily check-in → scheduled tasks (optional) │
│ │
│ Result: Fully personalized recruitment team │
└─────────────────────────────────────────────────────────┘File templates for each step are in references/templates.md. Load them when generating files.
Quick Start (under 5 minutes)
If the user says "quick setup", "fast", or seems pressed for time:
- Ask for resume only
- Auto-generate profile.md from resume (pillars, targets, situation)
- Auto-extract 3 stories from resume achievements (best-guess STAR)
- Create sensible defaults for writing framework and negotiation
- Skip voice samples and personal values
- Create pipeline-data.md skeleton
- Tell user: "Quick setup done. You can refine anytime with
/personalize full"
Full Setup (20-30 minutes)
Walk through all 9 steps below. Be conversational — ask one section at a time. After each step, confirm what was saved before moving to the next.
Step 1: Resume
Ask: "Drop your resume here (PDF, or paste the text)."
- If PDF: read and extract key facts
- If text: parse directly
- Save to knowledge/resume/base-resume.pdf (or .md if text)
- Extract: name, current role, education, years of experience, key achievements, technical skills
Step 2: Profile
Ask these one at a time:
- "What are the 3 things that make you different from other candidates?" (e.g., "deep technical skills + MBA + sold a startup")
- "What roles are you targeting?"
- "Any specific companies you're focused on?"
- "What's your current situation?" (e.g., "MBA student graduating in June")
Generate knowledge/profile.md using the template from references/templates.md.
Step 3: Stories (STAR Format)
Extract 3-5 stories from the resume. For each major achievement, ask: "Tell me more about [achievement]. What was the situation, your role, what you did, and what happened?"
Save each to knowledge/stories/[descriptive-name].md using the STAR template.
If the user has more stories later: /personalize stories to add more.
Step 4: Writing Framework
Ask: "Do you have a communication framework or writing style you follow?"
- If they name one (Foley, Minto Pyramid, BLUF): generate a structured version, ask for customizations
- If they describe principles ("I like being direct"): ask about tone, banned phrases, signature moves
- If they say "I don't have one": ask for a writing sample and reverse-engineer their style
Save to knowledge/frameworks/writing-framework.md using the template.
Step 5: Voice Samples (Optional)
Ask: "Share 1-2 pieces of writing you're proud of — or say 'skip' and I'll work from your writing framework."
If provided: save to knowledge/voice/samples.md with a voice profile analysis at the top. If skipped: note "No voice samples yet."
Step 6: Negotiation Preferences
Ask one at a time:
- "What's your target compensation range?"
- "What matters most — base, equity, remote, title, team quality?"
- "Is there a number below which you'd walk away?"
- "Have you negotiated offers before, or is this new territory?"
Save to knowledge/negotiation/strategy.md using the template. If they're new to negotiation, generate a beginner-friendly strategy with scripts.
Step 7: Personal Values (Optional)
Ask: "Is there a personal story, value, or motivation that drives your career? Say 'skip' if you'd rather not share."
If shared: save to knowledge/values/personal.md with guidance on when to use each element. If skipped: create a minimal file.
Step 8: Pipeline Setup
If pipeline-data.md doesn't exist, create it using the template. If it already exists, skip this step.
Step 9: Daily Check-In (Optional)
Ask: "Want daily check-ins? Options: pipeline review (morning), role discovery (ongoing), both, or neither."
If yes: create scheduled tasks with CronCreate. If no: skip.
Output Format (When Done)
Show a summary of what was created or updated:
Your recruitment team is ready!
knowledge/
├── profile.md ✅ [Name], [X] years exp
├── resume/ ✅ Uploaded
├── stories/ ✅ [N] stories extracted
├── frameworks/ ✅ Writing framework: [source]
├── voice/ ✅ / ⏭️ Skipped
├── negotiation/ ✅ Target: [range]
└── values/ ✅ / ⏭️ Skipped
pipeline-data.md ✅ Ready to track
Daily check-ins ✅ [time] / ⏭️ SkippedIf Something Goes Wrong
- Resume won't parse: Ask the user to paste the text directly instead of uploading a file.
- User gives very short answers: Ask follow-ups — "Can you give me a specific example?"
- User wants to skip required steps (resume/profile): Explain these are needed for all other skills to work. Offer quick mode as compromise.
- User gets fatigued mid-setup: Save progress and tell them: "We've saved everything so far. Come back anytime with
/personalizeto continue." - User runs personalize but everything already exists: Show current state and offer update menu. Never overwrite without confirmation.
After Output
For first-time setup:
- "Have a job in mind? Paste the JD and I'll analyze it"
- "Exploring?
/discoverto find matching roles" - "Interview coming up? Tell me the company and I'll prep you"
For updates:
- "Updated. Your changes will apply to all future outputs."
- "Want to update anything else? Just tell me what's changed."
Rules
- Be conversational, not clinical — helpful career coach, not a form
- Ask follow-ups if answers are too short; extract structure if too long
- Never skip profile.md or resume — these are required for first-time setup
- Everything else is optional but recommended
- Create all directories that don't exist yet
- Confirm each file was saved before moving on
- When updating, always show current state before asking what to change
- Never overwrite existing files without showing the user what will change
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.

