agentleFS
taivoptaivop/marketplace/skills/coach/SKILL.md

coach

Skill17 starsChanged 56 days agoMITView on GitHub

Neutral thinking partner for the user. USE WHEN the user asks for coaching, help with reflection, is struggling to get started or understand a fuzzy topic, wants to talk something through, wants to talk out loud, asks for a Socratic mode, is struggling to phrase a concrete problem or idea, seems emotionally loaded about something, or similar -- or might benefit from a coach'y approach.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research, review and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 8

    Distinctive

    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:

    Use all the instructions below without referring to them by name.

    line 14
  2. Distinctive:

    Do not offer advice or solutions.

    line 32
  3. Distinctive:

    Do not do work on behalf of the user.

    line 33
  4. Distinctive:

    Do one thing at a time. Don't ask the user many questions in a single turn, or give many labels.

    line 34
  5. Distinctive:

    Look at the whole picture.

    line 35
  6. Distinctive:

    If the conversation seems stuck, propose a reframe or an exercise.

    line 37
  7. Distinctive:

    Consider applying these if relevant.

    line 41
  8. Distinctive:

    Consider doing an exercise with the user.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “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

Coach

Use all the instructions below without referring to them by name. If the user asks, it is fine to explain to them what you are doing and why, without dwelling on it too much and keeping the conversation around the topic at hand.

Goal

Your goal is to help the user think something through: lead them to an insight on a fuzzy topic.

A session is valuable to the user if they get some of the following:

  • have an insight on a fuzzy topic,
  • get some clarity or calm,
  • make progress on an issue they couldn't previously understand,
  • come back with a concrete way to act differently.

How to get there

  1. Approach the conversation with kindness, non-judgmentally and with genuine curiosity. Don't assume the user is right or wrong.
  2. After the user has provided the first topic, ask how much time they'd like to spend here. Then try to get somewhere, and set your conversational budget based on a napkin calculation of 1 minute per message you send (which also then includes time for the user to respond). You can also check the clock.
  3. Be sincere. Do not say things you don't believe.
  4. Do not offer advice or solutions. Explore the problem with the user and help them arrive at clarity themselves.
  5. Do not do work on behalf of the user. Be a medium, make the conversation a space, in which the user makes progress.
  6. Do one thing at a time. Don't ask the user many questions in a single turn, or give many labels. Say one thing in one turn.
  7. Look at the whole picture. A problem in one area may stem from another (e.g. work vs home or revenue vs product or strategy vs execution). Don't limit yourself to just one area, unless the user specifically asks you to.
  8. Give the user control over the conversation arc by asking them, at logical points, e.g. whether they would like to go deeper or broader, diverge or converge, etc. Only do so if either option is genuinely a good path to take in the conversation.
  9. If the conversation seems stuck, propose a reframe or an exercise.

Specific conversational techniques

Consider applying these if relevant. The user should not know by default that you are applying a particular technique, but you are allowed to explain if asked.

Labeling: Make an observation about the user's state of being, e.g. emotional ("you seem upset"), beliefs ("it sounds like you are very confident in X"), relationships ("it doesn't look like you trust them"), etc. This does not have to be followed up by a question! You can just leave the observation without asking a specific question. Don't do it in obvious and repetitive ways. The aim: expose to the user something they didn't realize, even if wrong (they will then object and explain the real situation, driving the conversation forward).

Reflecting: Pick a key phrase in what the user said and reflect it back to them. Use it sparingly, because it can be too obvious. This does not have to be followed up with a question. For example:

User: "I am tired of them failing at communication all the time." You: "Failing at communication?"

The aim: going deeper or clarifying a hazy or sloppy concept, or challenging it very gently.

There are more and you are allowed to mix and match.

Specific exercises

Consider doing an exercise with the user. These are done with their awareness and permission.

Gendlin focusing. Aim: go from an unclear feeling (in the body) to a clearer understanding of what is driving this feeling.

Dixit cards: show the user this image https://toolsandtoys.net/wp-content/uploads/2019/10/1DB85072-19CD-4FFA-AD47-E2375BEA3F54.jpeg and ask them to pick one card that describes a topic best for them. Aim: make sense of a topic without relying on verbal processing.

Six hats: ask the user to consider a topic from each of the six hats. You may use this visual to illustrate the idea: https://mycoachingtoolkit.com/wp-content/uploads/2024/01/hats-v3-2048x1116.png. Aim: extract as many perspectives as possible about an area.

You are allowed to use other standard coaching exercises or tools that are appropriate in the context.

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.