explore-resume
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Understand the user's background comprehensively — technical stack, project experience, research experience, publications, research directions. Allows user to express interest beyond their resume. Execute once only, never re-run.
In this repository32 other files it gives its agents.
- actor-profilingSkill
- and-or-decomposeSkill
- ask-constraintsSkill
- ask-decomposition-validationSkill
- ask-intentionalitySkill
- ask-obstacle-acceptanceSkill
- assess-obstacle-severitySkill
- broad-paper-searchSkill
- broad-web-searchSkill
- clarify-resourcesSkill
- cold-startSkill
- crystallize-north-starSkill
- deep-web-searchSkill
- direction-narrowingSkill
- feasibility-checkSkill
- final-validationSkill
- formulate-top-goalSkill
- generate-candidate-fieldsSkill
- generate-research-briefSkill
- goal-decompositionSkill
- hot-startSkill
- identify-obstaclesSkill
- landscape-reconnaissanceSkill
- landscape-synthesisSkill
- north-star-crystallizationSkill
- north-star-synthesisSkill
- obstacle-analysisSkill
- present-and-askSkill
- present-candidatesSkill
- propose-mitigationsSkill
- validate-leavesSkill
- warm-startSkill
The file
Files
Explore Resume
Build a comprehensive picture of who the user is professionally and academically.
Execution
Dialogue — inline, no subagent.
What to Ask About (one at a time)
- Technical stack (languages, frameworks, tools they're proficient in)
- Project experience (what have they built or contributed to)
- Course/research experience (what have they studied formally)
- Publications (if any — papers, preprints, technical reports)
- Current research directions (what are they working on now)
- Areas of interest beyond current experience (what excites them that they haven't done yet)
Key Behaviors
- Allow user to express interest in areas outside their resume — this is not a constraint-gathering exercise
- In cold-start: user may not know what they can do. That's fine — capture what they've done and what excites them
- Execute once only. Never re-run this SOP.
Output
Background section of ActorProfile.
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.