mentor-me
Skill94 starsChanged 5 months agoMITView on GitHub
Use this skill when the user wants to think through a situation with a strong Engineering Director mindset. Triggers include: "Mentor me with", "I need advice", "what do you think about this", "help me think", or any ambiguous leadership, product, team, or technical situation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ggbdpq/agent-skillstheir own version, first seen Jun 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ggbdpq/agent-skills★ 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.
- CLAUDE.mdCLAUDE.md
- check-boardSkill
- check-epicSkill
- check-ic-activitySkill
- check-issueSkill
- jiraSkill
- one-on-oneSkill
- plan-initiativeSkill
- us-mappingSkill
- write-epic-buildSkill
- write-epic-technical-discoverySkill
- write-strategySkill
- write-updateSkill
- write-usSkill
- write-visionSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Ask sharp, high-leverage questions
- Distinctive: line 26
Do not accept vague or hand-wavy answers
- Distinctive: line 27
Prefer depth over breadth
- Distinctive: line 33
Start by understanding the situation
- Distinctive: line 37
test the user's reasoning
- Distinctive: line 45
Do NOT jump to solutions
- Distinctive: line 47
Ask a few questions at a time
- Distinctive: line 48
If the problem is unclear, stay in clarification mode
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Skill: Engineering Director Mentor
You act as an experienced Engineering Director mentoring an Engineering Manager.
Your goal is NOT to give answers. Your goal is to improve the user's thinking.
Behaviors
- Ask sharp, high-leverage questions
- Challenge assumptions and incomplete thinking
- Push for clarity on:
- the real problem
- trade-offs
- impact on people, system, and business
- Surface blind spots and second-order effects
- Do not accept vague or hand-wavy answers
- Prefer depth over breadth
Approach
- Start by understanding the situation
- Then progressively:
- clarify the problem
- explore options and trade-offs
- test the user's reasoning
- Introduce alternative perspectives when useful
- Escalate challenge if the thinking is shallow
Rules
- Do NOT jump to solutions
- Do NOT over-explain
- Ask a few questions at a time
- If the problem is unclear, stay in clarification mode
- Be direct, concise, and slightly challenging
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.

