setup-profile
Skill0 starsChanged 3 months agoMITView on GitHub
Create or update the candidate's canonical factual career profile from their resume and answers.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- IrinaSer/Meal-AI-templatetheir own version, first seen Jun 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- IrinaSer/Meal-AI-template★ 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/job-agent.mdcCursor rule
- answer-questionsSkill
- claim-checkSkill
- daily-briefSkill
- find-broad-jobsSkill
- find-consulting-opportunitiesSkill
- find-jobsSkill
- record-outcomeSkill
- refresh-candidate-brandSkill
- research-target-personSkill
- review-search-performanceSkill
- score-fitSkill
- tailor-resumeSkill
- write-cover-letterSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Very specific: line 15
Read user's pasted resume text or file in candidate/.
- Distinctive: line 17
Do NOT invent metrics or embellish scope.
- Distinctive: line 28
Use opportunity tracks when the candidate plausibly spans distinct role families (for example AI consulting + product building + growth).
- Distinctive: line 29
Keep every track grounded in actual evidence from the profile.
- Distinctive: line 30
Do not create a track merely to chase a posting the candidate cannot support.
- Very specific: line 33
Run python scripts/doctor.py to confirm profile files are valid and protected by .gitignore.
≈ “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
setup-profile
Transform the candidate's raw résumé and search preferences into a durable, local-first source of truth.
Workflow
- Ingest Existing Résumé:
- Read user's pasted resume text or file in
candidate/. - Extract strictly verified facts: work history, company names, titles, dates, education, and technical competencies.
- Do NOT invent metrics or embellish scope.
- Read user's pasted resume text or file in
- Establish Files in
candidate/:MASTER_PROFILE.md: Complete chronological career history, contact info, summary, and honest framing notes.SEARCH_PREFERENCES.md: Target roles, work mode (remote/hybrid/onsite), locations, compensation minimum, and company exclusions.VERIFIED_ACHIEVEMENTS.md: Bullet points with verified metrics and outcomes.CAREER_STORIES.md: STAR-format narratives of key technical challenges.skills.json: Categorized JSON taxonomy of proven vs transferable skills.OPPORTUNITY_TRACKS.json(optional): Multiple legitimate career/revenue lanes, each with its own search queries and fit signals. Start fromtemplates/OPPORTUNITY_TRACKS_TEMPLATE.json.
- Configure Multi-Track Search When Needed:
- Use opportunity tracks when the candidate plausibly spans distinct role families (for example AI consulting + product building + growth).
- Keep every track grounded in actual evidence from the profile.
- Do not create a track merely to chase a posting the candidate cannot support.
- Verify Integrity:
- Run
python scripts/doctor.pyto confirm profile files are valid and protected by.gitignore.
- Run
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.