Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
Finding, maintaining, and providing mentorship relationships.
$ npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills mentorship --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mentorship .claude/skills/mentorship && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mentorship" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/mentorship into .claude/skills/mentorship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mentorship", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/mentorshipType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills mentorship --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mentorship .agents/skills/mentorship && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mentorship" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/mentorship into .agents/skills/mentorship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mentorship", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills mentorship --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mentorship .cursor/skills/mentorship && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mentorship" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/mentorship into .cursor/skills/mentorship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mentorship", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/mentorship--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills mentorship --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mentorship .gemini/skills/mentorship && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mentorship" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/mentorship into .gemini/skills/mentorship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mentorship", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills mentorshipInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mentorship .github/skills/mentorship && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mentorship" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/mentorship into .github/skills/mentorship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mentorship", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills mentorship --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mentorship .opencode/skills/mentorship && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mentorship" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/mentorship into .opencode/skills/mentorship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mentorship", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
mentorshipFinding, maintaining, and providing mentorship relationships.
Mentorship is an agent skill from LeoYeAI/openclaw-master-skills. Finding, maintaining, and providing mentorship relationships. Use when someone wants guidance in career or skill development, wants to find a mentor, has been asked to mentor someone, or values cross-generational knowledge transfer.
Its SKILL.md is about 5.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
It sits in Agent Workflows, covering Skill authoring. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
justFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
hbr.orgFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Mentorship loads about 5.3k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 866 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 866 words, ~5,261 tokens.
.claude/skills/mentorship/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub."Will you be my mentor?" is the worst way to start a mentorship. It puts pressure on the other person, frames the relationship as a burden, and usually comes from someone who hasn't done the groundwork to make the relationship valuable for both sides. Real mentorship happens when you bring specific problems to someone with relevant experience, follow through on their advice, and report back on what happened. The formal "mentor/mentee" label is almost never necessary — the best mentorships look like regular conversations between two people who respect each other, one of whom happens to be further down the road. This skill covers both sides: how to find and learn from a mentor, and how to mentor someone when you're convinced you're not qualified (you almost certainly are).
This skill references and extends: adult-social-skills, difficult-conversations.
# Localization note — mentorship structures and norms vary by culture and industry.
- Formality levels:
US/CA/AU: Relatively informal mentorship culture. Coffee meetings, casual check-ins.
UK: Slightly more formal. Professional networking through industry bodies, alumni networks.
Germany/Japan/Korea: More hierarchical. Mentorship often follows seniority structure.
Formal programs through companies or professional associations are more common.
India: "Guru-shishya" tradition. Mentorship carries deep cultural respect.
- Trades and manual work:
Apprenticeship models vary. In Germany, the dual education system (Ausbildung) is
formalized. In the US/UK/AU, apprenticeships exist but are less standardized outside
union trades. Informal "learning by doing alongside someone experienced" is universal.
- Gender and access:
Women and minorities often have less access to informal mentorship networks.
Formal mentorship programs, industry associations, and organizations like Lean In,
/dev/color, or Code2040 can bridge this gap.
- Cross-cultural mentorship:
When mentor and mentee come from different cultural backgrounds, communication
styles, expectations around hierarchy, and feedback norms may differ. Name it early.
- Digital vs. in-person:
Some cultures expect in-person relationship building before any mentorship.
Others (especially in tech/remote industries) are comfortable with purely digital
mentorship. Match the norms of the field.Agent action: Explain why the direct ask backfires and provide the better approach.
WHY "WILL YOU BE MY MENTOR?" DOESN'T WORK
1. It's vague. What are you actually asking them to do?
2. It's a big commitment ask from someone who doesn't know you yet.
3. It puts them in an awkward position — saying no feels mean,
saying yes feels like signing up for something undefined.
4. It signals that you want someone to tell you what to do, which
isn't what good mentorship looks like.
WHAT TO DO INSTEAD — THE ORGANIC APPROACH
Phase 1: IDENTIFY (who's 2-5 steps ahead of you?)
- Not celebrities or CEOs. Someone accessible who does what you
want to do, slightly further along. A senior person at your
company. Someone in your industry you've met at events. A
skilled tradesperson in your shop. A person whose work you respect.
Phase 2: ENGAGE WITH THEIR WORK
- If they create content, engage with it thoughtfully (not "great post!"
but a genuine question or observation).
- If they're at your workplace, ask for their input on a specific
problem you're working on.
- If you met at an event, follow up about something specific they said.
Phase 3: ASK A SPECIFIC QUESTION
- "I'm working on [specific thing] and I'm stuck on [specific problem].
You've dealt with this — would you have 15 minutes to share how
you approached it?"
- This is a small, defined ask. Easy to say yes to.
Phase 4: FOLLOW UP WITH RESULTS
- After they help you, tell them what you did with their advice.
"I tried what you suggested. Here's what happened."
THIS IS THE MOST IMPORTANT STEP. It shows you actually listen.
Most people who ask for advice never report back. Be the exception.
Phase 5: LET IT GROW ORGANICALLY
- After 3-4 exchanges like this, you have a mentorship. You don't
need to label it. The relationship IS the mentorship.Agent action: Provide the structured approach for mentor meetings.
HOW TO HAVE A PRODUCTIVE MENTOR MEETING
BEFORE THE MEETING:
- Prepare 3 specific questions. Not "what should I do with my life?"
but "I'm choosing between [A] and [B] and here's what I've considered
so far. What am I missing?"
- Do your homework. If they've written or spoken about the topic,
read it first. Don't ask them to repeat what's already public.
- Be clear about the time ask. "Can I take 20 minutes of your time?"
is better than "Can we meet sometime?"
DURING THE MEETING:
- Lead with context, then the question. Don't make them guess.
"Here's my situation: [30-second summary]. Here's what I've
tried: [brief list]. Here's where I'm stuck: [specific question]."
- Take notes. Visibly. It signals respect.
- Listen more than you talk. You asked for their input — let them give it.
- If they share a mistake they made, that's gold. Ask follow-up questions
about what they learned.
AFTER THE MEETING:
- Send a thank-you within 24 hours. Short. Not gushing.
"Thanks for your time today. The advice about [specific thing] was
exactly what I needed. I'm going to try [specific action]."
- Within 2-4 weeks, follow up with results. "I tried [thing]. Here's
what happened: [outcome]." Even if it didn't work — reporting back
is the point.
FREQUENCY:
- Monthly is usually right. More often is too much unless they offer.
- Don't assume ongoing meetings. Each time, ask: "Would it be helpful
to check in again in a month, or would you prefer I reach out
as things come up?"Agent action: Clarify what makes a mentee valuable vs. draining.
WHAT MENTORS WANT FROM YOU (AND WHAT DRIVES THEM AWAY)
WHAT TO BRING:
- Specific problems, not vague requests for guidance
- What you've already tried (shows you're not asking them to do
your thinking)
- Willingness to do the uncomfortable thing they suggest
- Follow-through and results reports
- Genuine curiosity about their experience
- Respect for their time
WHAT DRIVES MENTORS AWAY:
- Asking for advice and then arguing why it won't work
- Never following up on what they suggested
- Treating them as a therapist (venting without wanting input)
- Asking for favors too early (introductions, recommendations)
before you've built the relationship
- Being vague: "I just want to get ahead" — ahead of what? toward what?
- Not doing your own research first
THE VALUE EXCHANGE:
Good mentorship isn't charity. Mentors get value too:
- Fresh perspective on their industry from a newer viewpoint
- The satisfaction of helping someone develop (this is real and matters)
- Staying connected to the ground-level reality of the field
- Sometimes, practical help — younger mentees often have skills
(tech, social media, current tools) that experienced people don't
Don't assume you have nothing to offer. You do.Agent action: Explain how to recognize and gracefully end a mentorship.
MENTORSHIPS AREN'T FOREVER — AND THAT'S FINE
SIGNS IT'S RUN ITS COURSE:
- You've outgrown the specific help they can offer
- Conversations feel repetitive — same advice, same topics
- Your paths have diverged and their experience is less relevant
- Meetings feel like obligation rather than value
- You've reached the level they're at (congratulations)
HOW TO END IT GRACEFULLY:
Don't ghost. Don't make it dramatic. Reduce frequency naturally.
"I want you to know how much your guidance has meant to me over
the past [time period]. I feel like I've gotten to a point where
I need to [next phase]. I'd love to stay in touch — can I reach
out occasionally when something comes up?"
This:
- Acknowledges their impact (people want to know they mattered)
- Explains the natural transition
- Keeps the door open without the ongoing commitment
- Treats them as a human, not a resource you're discarding
AFTER:
- Check in once or twice a year. Holiday message. Quick update on
your progress. "Thought you'd want to know — I got [thing] and
your advice about [specific thing] was a big part of that."
- Mentors remember the people who stayed grateful. The relationship
can reignite years later in unexpected ways.Agent action: Address the imposter syndrome that stops people from mentoring.
YOU'RE QUALIFIED IF YOU'RE 2 STEPS AHEAD
The biggest myth about mentoring: you need to be an expert. You don't.
You need to have already solved the problem the other person is facing.
JUST FINISHED YOUR FIRST YEAR IN A TRADE?
You can mentor someone in their first week. You know things they don't:
which tools to buy, what the foreman actually cares about, how to
survive the cold, how to not look lost on day one.
JUST GOT YOUR FIRST PROMOTION?
You can mentor someone trying to get theirs. You remember the obstacles.
An executive who got promoted 20 years ago doesn't.
JUST SURVIVED A CAREER CHANGE?
You can mentor someone considering one. You know the fears because
you just had them.
THE 2-STEP RULE: If you're 2 steps ahead of someone, you're close
enough to their reality to be useful and far enough ahead to see
what's coming. That's the sweet spot.
WHY YOUR IMPOSTER SYNDROME IS WRONG:
- You don't need to have all the answers. You need to have RELEVANT
experience.
- The people closest to the problem often give the best advice.
The CEO's perspective is too abstract for a junior worker.
- Your mistakes are as valuable as your successes. "Here's what
I tried that didn't work" saves someone months.Agent action: Provide the technique for effective mentoring conversations.
THE MENTORING CONVERSATION — QUESTIONS, NOT LECTURES
Bad mentoring: "Let me tell you what you should do."
Good mentoring: "Tell me what you've considered so far."
THE FRAMEWORK:
1. ASK BEFORE YOU ADVISE
"What have you already tried?"
"What's your instinct telling you?"
"What's holding you back from [the thing they clearly want to do]?"
2. SHARE EXPERIENCE, NOT DIRECTIVES
"When I was in a similar situation, I tried X and here's what happened."
NOT: "You should do X."
Let them draw their own conclusions from your experience.
3. SHARE MISTAKES GENEROUSLY
Your failures teach more than your successes. "I made this mistake
and here's what it cost me" is the most valuable thing a mentor
can offer. It takes vulnerability. It builds trust.
4. LET THEM DECIDE
Your job is to expand their thinking, not replace it. Even if you
think they're about to make a mistake — unless it's catastrophic,
let them learn from it. Then be there when they want to debrief.
5. ASK THE HARD QUESTION THEY'RE AVOIDING
"What are you afraid of here?"
"What would you do if you weren't worried about [the thing]?"
"Is this what you actually want, or what you think you should want?"
Sometimes the most valuable thing a mentor does is ask the question
nobody else will.
WHAT NOT TO DO:
- Don't make it about you. Brief stories to illustrate a point, not
20-minute monologues about your glory days.
- Don't solve every problem. Ask "do you want advice or do you want
to think out loud?" — sometimes people need a sounding board.
- Don't judge. They're going to make choices you wouldn't. That's
their right.Agent action: Cover informal mentorship in trades and physical skill development.
INFORMAL MENTORSHIP IN TRADES AND PHYSICAL WORK
The trades have practiced mentorship for centuries. The apprenticeship
model works because it's built on watching, doing, and getting feedback
in real time — not classroom instruction.
THE THREE STAGES:
1. OBSERVE: Watch how the experienced person does it. Not just the
technique — their pace, their decisions, how they handle problems.
Ask "why did you do it that way?" after, not during.
2. ASSIST: Work alongside them. They lead, you support. This is where
you learn the rhythm, the shortcuts, the things that aren't in
any manual.
3. DO (with feedback): You take the lead, they watch. They correct in
real time. "Good, but next time start from the other end." This
stage is where real skill forms.
HOW TO LEARN FASTER FROM AN EXPERIENCED WORKER:
- Show up early. Willingness matters more than talent at first.
- Don't pretend to know things you don't. "I haven't done this
before — can you show me?" earns respect, not judgment.
- Write down what they teach you. Even rough notes. It shows you
value their knowledge. Most experienced workers have watched
dozens of people ignore their advice. Be different.
- Don't ask "why?" in a challenging way during the task. Ask "can
you walk me through your thinking on that?" after the task.
- Respect their expertise. "You make that look easy" is a compliment
that opens conversations.
THE KNOWLEDGE TRANSFER CRISIS:
Baby boomers are retiring in massive numbers. In trades especially,
decades of institutional knowledge walk out the door every day.
If you have access to an experienced person who's willing to teach,
treat that access as the valuable resource it is. It won't be there
forever.Agent action: Cover younger-to-older mentorship and the network model.
REVERSE MENTORSHIP — YOUNGER TEACHING OLDER
Not all mentorship flows downhill. Reverse mentorship — where someone
younger or less senior mentors someone more experienced — is
increasingly valuable because the world is changing faster than any
one generation can track.
WHAT YOUNGER PEOPLE CAN MENTOR ON:
- Technology (new tools, platforms, workflows)
- Cultural shifts (communication norms, generational expectations)
- Social media and digital presence
- Current industry trends and what's emerging
- Perspectives the experienced person's bubble doesn't include
HOW TO MAKE IT WORK:
- Frame it as mutual exchange, not "let me teach you how to use
your phone." Respect goes both ways.
- Be patient. Learning new things is uncomfortable at any age.
- Don't condescend. The experienced person's knowledge is real and
deep. They just have a gap in one area.
THE MENTORSHIP NETWORK MODEL
The single-mentor model is outdated. Nobody's career is shaped by
one person anymore. Build a network instead:
- SKILL MENTOR: Teaches you specific technical or professional skills
- CAREER MENTOR: Helps you navigate the industry, make strategic moves
- PEER MENTOR: Same level as you, different perspective. You sharpen
each other.
- LIFE MENTOR: Someone whose overall life you respect, not just
their career. Could be a family member, community elder, or friend.
- MENTEE: Someone you're mentoring. Teaching clarifies your own
thinking.
You don't need all five at once. But aiming for more than one
mentor prevents the problem of getting only one perspective on
every decision.mentorship_session:
user_role: null
mentorship_goal: null
current_mentors: []
current_mentees: []
industry_context: null
specific_question: null
mentorship_stage: null
resources_provided: []
related_skills_referenced: []triggers:
- name: mentor_search
condition: "user wants to find a mentor or asks how to approach someone for guidance"
schedule: "on_demand"
action: "Begin with Step 1 organic approach and Step 2 coffee meeting protocol"
- name: become_mentor
condition: "user has been asked to mentor or wants to give back but feels unqualified"
schedule: "on_demand"
action: "Jump to Step 5 qualification reassurance and Step 6 conversation framework"
- name: mentorship_boundary_issue
condition: "user describes a mentor crossing professional or personal boundaries"
schedule: "immediate"
action: "Flag the boundary issue, reference boundaries-saying-no skill, and help user assess if the relationship should continue"
- name: knowledge_transfer
condition: "user is in a trade or physical job and wants to learn faster from experienced workers"
schedule: "on_demand"
action: "Jump to Step 7 apprenticeship model and provide observation/assist/do framework"© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/mentorship of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Mentorship next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mentorship this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.3k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 11 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Claude Code Command Developmentanthropics/claude-plugins-official | 38k | 10 repos | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Plugin Structureanthropics/claude-plugins-official | 38k | 10 repos | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
anthropics/claude-plugins-official
Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.
anthropics/claude-plugins-official
Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.
rohitg00/ai-engineering-from-scratch
Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Finding, maintaining, and providing mentorship relationships. Mentorship is an agent skill from LeoYeAI/openclaw-master-skills. Finding, maintaining, and providing mentorship relationships.
Mentorship fits situations like: someone wants guidance in career; skill development; wants to find a mentor; has been asked to mentor someone.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a claude-code`. Or copy the skill folder (skills/mentorship in LeoYeAI/openclaw-master-skills) into .claude/skills/mentorship in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a codex`. Or copy the skill folder (skills/mentorship in LeoYeAI/openclaw-master-skills) into .agents/skills/mentorship in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill mentorship -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mentorship, .gemini/skills/mentorship, .github/skills/mentorship and .opencode/skills/mentorship in your project.
Going by SKILL.md and its folder, Mentorship needs the command-line tools its instructions call (just). Our summary lists: Node.js.
SKILL.md names 1 domain. As links in the text: hbr.org. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Mentorship is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.3k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Mentorship: Skill Creator (Azure/azqr, 796 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.