personalize-skills
Skill17 starsChanged 9 months agoMITView on GitHub
Customize Operator Skills for your environment. Use when first installing skills or when you want to update your personal values.
In this repository20 other files it gives its agents.
- adversarial-verifierSkill
- candidate-screeningSkill
- coachSkill
- contract-reviewSkill
- create-briefingSkill
- credits-inventorySkill
- handoffSkill
- hiring-helperSkill
- inbox-commanderSkill
- interviewSkill
- investor-auditsSkill
- monthly-financialsSkill
- prompt-improverSkill
- ralph-loop-creatorSkill
- reality-checkSkill
- sensitive-content-scannerSkill
- show-and-tellSkill
- skill-customizerSkill
- technical-orientationSkill
- writeupSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
After first installing Operator Skills
- Distinctive: line 13
When you want to update your personal info
- Distinctive: line 14
After updating to a new version of the skills
- Distinctive: line 19
Ask you for each value (grouped by type)
- Distinctive: line 20
Update all occurrences across all skills
- Distinctive: line 67
All identity questions together
- Distinctive: line 68
All path questions together
- Distinctive: line 69
All URL questions together
- Distinctive: line 138
If a placeholder is marked optional, you can skip it.
- Very specific: line 141
Run /personalize-skills again anytime to update your values.
- Distinctive: line 144
Before personalizing, consider backing up your skills directory:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Personalize Skills
Walk through all customization points in your Operator Skills and set your personal values.
When to Use
- After first installing Operator Skills
- When you want to update your personal info
- After updating to a new version of the skills
How It Works
- Scan all skills for
[YOUR_*]placeholders - Ask you for each value (grouped by type)
- Update all occurrences across all skills
- Confirm what was changed
Invocation
/personalize-skills — Full interactive setup
/personalize-skills --list — Just show what needs customizing
/personalize-skills --reset — Clear customizations (restore placeholders)
Workflow
Step 1: Scan for Placeholders
Scan ~/.claude/skills/ for all [YOUR_*] patterns.
Group by placeholder type:
Found 12 placeholders across 6 skills:
Identity:
[YOUR_NAME] — used in 3 skills
[YOUR_EMAIL] — used in 2 skills
Paths:
[YOUR_CLOUD_PATH] — used in 2 skills
[YOUR_KNOWLEDGE_ARCHIVE] — used in 1 skill
URLs:
[YOUR_NOTION_URL] — used in 1 skillStep 2: Collect Values
For each placeholder, ask the user:
[YOUR_NAME]
Used in: coach, writeup, inbox-commander
Description: Your name for personalized interactions
Example: Danny
What's your name? > ___Group related questions:
- All identity questions together
- All path questions together
- All URL questions together
Step 3: Apply Changes
For each value provided:
- Find all occurrences of the placeholder
- Replace with the user's value
- Track what was changed
Applying changes...
✓ [YOUR_NAME] → "Alex" in 3 files
- coach/SKILL.md (2 occurrences)
- writeup/SKILL.md (1 occurrence)
- inbox-commander/references/known-senders.md (1 occurrence)
✓ [YOUR_EMAIL] → "alex@startup.com" in 2 files
- inbox-commander/SKILL.md
- inbox-commander/references/known-senders.mdStep 4: Confirm
Show summary:
Personalization complete!
Values set: 5
Files updated: 8
Placeholders remaining: 2 (optional)
Optional placeholders not set:
- [YOUR_KNOWLEDGE_ARCHIVE] — Only needed if you have a personal knowledge base
- [YOUR_NOTION_URL] — Only needed if you use Notion
You can set these later by running /personalize-skills again.Placeholder Reference
Common placeholders and what they're for:
Identity
| Placeholder | Description | Example |
[YOUR_NAME] | Your name | Alex |
[YOUR_EMAIL] | Your email address | alex@company.com |
[YOUR_COMPANY] | Your company name | Acme Inc |
Paths
| Placeholder | Description | Example |
[YOUR_CLOUD_PATH] | Cloud storage folder | ~/Dropbox/ |
[YOUR_KNOWLEDGE_ARCHIVE] | Personal knowledge base | ~/Documents/knowledge/ |
[YOUR_DRAFTS_FOLDER] | Where to save drafts | ~/Documents/drafts/ |
URLs
| Placeholder | Description | Example |
[YOUR_NOTION_URL] | Notion workspace URL | your-workspace.notion.site |
Tips
Skip optional placeholders
If a placeholder is marked optional, you can skip it. The skill will work without it.
Update later
Run /personalize-skills again anytime to update your values.
Back up first
Before personalizing, consider backing up your skills directory:
cp -r ~/.claude/skills ~/.claude/skills-backupCheck the guide
See CUSTOMIZATION-GUIDE.md in the repo for detailed explanations of each placeholder.
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.