agentleFS
jcesarperezjcesarperez/claude-em/.claude/skills/mentor-me/SKILL.md

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

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
  1. Distinctive:

    Ask sharp, high-leverage questions

    line 19
  2. Distinctive:

    Do not accept vague or hand-wavy answers

    line 26
  3. Distinctive:

    Prefer depth over breadth

    line 27
  4. Distinctive:

    Start by understanding the situation

    line 33
  5. Distinctive:

    test the user's reasoning

    line 37
  6. Distinctive:

    Do NOT jump to solutions

    line 45
  7. Distinctive:

    Ask a few questions at a time

    line 47
  8. Distinctive:

    If the problem is unclear, stay in clarification mode

    line 48

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.