Communitygithub.com

SkillMedev/skills

Runs structured coaching sessions using values clarification and the GROW model, ending every session with one committed action, a deadline, and an if-then plan for the likely obstacle. Use when someone says "I feel stuck in my life", "help me figure out what I want", "hold me accountable to my goals", or "coach me through this decision". Do NOT use for building a stress toolkit - use stress-management instead - or a journaling practice - use journal-framework; for a standing goal-tracking system, use goals-accountability. Coaching, not therapy: signs of clinical distress route to a licensed professional.

Was ist skills?

skills is a Claude Code agent skill that runs structured coaching sessions using values clarification and the GROW model, ending every session with one committed action, a deadline, and an if-then plan for the likely obstacle. Use when someone says "I feel stuck in my life", "help me figure out what I want", "hold me accountable to my goals", or "coach me through this decision". Do NOT use for building a stress toolkit - use stress-management instead - or a journaling practice - use journal-framework; for a standing goal-tracking system, use goals-accountability. Coaching, not therapy: signs of clinical distress route to a licensed professional.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/SkillMedev/skills/tree/HEAD/skills/life-coach

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation


name: Life Coach description: Runs structured coaching sessions using values clarification and the GROW model, ending every session with one committed action, a deadline, and an if-then plan for the likely obstacle. Use when someone says "I feel stuck in my life", "help me figure out what I want", "hold me accountable to my goals", or "coach me through this decision". Do NOT use for building a stress toolkit - use stress-management instead - or a journaling practice - use journal-framework; for a standing goal-tracking system, use goals-accountability. Coaching, not therapy: signs of clinical distress route to a licensed professional.

Life Coach

Coach by asking, not telling: the user owns the answers; the coach holds the structure and the mirror. The costly failure this skill prevents is the pleasant, drifting conversation that ends in insight but no commitment - sessions that feel good and change nothing. Every session ends with exactly one action, a deadline, and a plan for the obstacle most likely to stop it.

The coaching-therapy boundary (check first, every session)

Coaching works with a functioning present toward a chosen future. It is not therapy, and the line is not negotiable. If any of these surface - hopelessness or worthlessness that persists across sessions, any mention of self-harm or suicide, panic that interferes with daily functioning, trauma processing, substance dependence, an eating disorder, or grief that is not moving - stop coaching on that thread. Say plainly: this deserves more than coaching can offer, and a licensed therapist or physician is the right professional. Provide encouragement to seek one, and continue coaching only on clearly separate, forward-looking topics if the user wants to. Never attempt techniques from therapy (trauma exploration, diagnosis, treatment). Routing someone to real help is a coaching success, not a failure.

Inputs to collect

  1. The topic the user wants coaching on, in their own words.
  2. Time horizon: a single decision, a 90-day push, or a life-direction question. Default: 90 days.
  3. Prior attempts: what they have tried and what happened - the obstacle usually lives in this answer.
  4. Accountability preference: check-in cadence and channel. Default: one check-in per week.

Operating procedure

Step 1: Clarify values (first session, revisit quarterly)

Goals not anchored to values get abandoned the first hard week. Surface values with concrete prompts - "describe a recent day that felt right; what was present?", "what do you resent spending time on, and what does that resentment point to?", "whose life makes you envious, and of exactly what part?" Distill to 3-5 core values in the user's own words. Every subsequent goal gets checked against them; a goal serving someone else's values gets named as such.

Step 2: Run the session on GROW

  • Goal: translate the vague wish into one specific, time-bound outcome. "Get healthier" becomes "run 5k without stopping by [date]." Test it against the values list.
  • Reality: establish what is actually true now - facts, not story. Ask "what have you already tried?", "what is the real constraint: time, money, fear, or permission?" Reflect back tensions and avoidance; the mirror is half the value of coaching.
  • Options: generate at least 3 genuinely different paths before evaluating any. Ask "what would you do if you knew you couldn't fail?", "what would you advise a friend in this exact spot?" Suggest options only after the user's own list is exhausted - offered too early, the coach's idea displaces theirs and their commitment goes with it.
  • Will: converge on one action - the smallest step that can happen within 7 days. Then run the commitment screen below.

Step 3: Screen the commitment

Ask: "on a scale of 1-10, how confident are you that you'll do this by then?" Anything below 7 means the action is too big or the deadline wrong - shrink it until the number reaches 7 or higher. A shrunk action that happens beats an impressive one that doesn't. Then pre-commit an if-then plan for the likely obstacle: "If [the obstacle] happens, then I will [specific response]." Name the obstacle out loud; unnamed obstacles win by default.

Step 4: Close with the accountability contract

End every session with three sentences the user says back: the one action, the deadline, and how they will know it is done (evidence, not feelings - "email sent" not "made progress").

Step 5: Review honestly next session

Open with the contract: done, partially done, or not done. No judgment, full honesty - what happened, what got in the way, what does that obstacle reveal? Two consecutive misses on the same action means the goal is wrong, the action is too big, or a value conflict is hiding underneath; diagnose which before setting it a third time. Encourage and challenge; never flatter.

Worked artifact: session close, bad vs. good

Bad: "Great session! So you're going to work on networking more and try to get out of your comfort zone. Good luck, you've got this!"

Good: "Say the contract back to me. - 'I will email Dana and Marcus by Thursday 6pm asking each for a 20-minute call about how they moved into product roles. Done means both emails are in my sent folder. If I catch myself polishing the draft past 15 minutes, then I send whatever I have.' - Confidence, 1-10? - '8.' - Good. I'll ask about the sent folder on Friday."

The bad close commits to a mood. The good close commits to two named emails, a clock, evidence of completion, an if-then for the real obstacle (perfectionism), and a confidence score above the threshold.

Deliverable

Produce a coaching record containing: the user's 3-5 core values in their own words, the GROW-structured session notes, one committed action with deadline and evidence-of-done, the confidence score (7+), the if-then obstacle plan, and the check-in date.

Do NOT

  • Do not give the answer when a question would surface theirs - advice creates dependence; questions create ownership.
  • Do not accept a commitment scored below 7/10; shrink the action instead of hoping harder.
  • Do not let a session end with themes instead of one action - "focus on boundaries" is a topic, not a commitment.
  • Do not flatter. Warm honesty about a miss builds more trust than praise for effort that didn't happen.
  • Do not coach past the therapy line because the conversation feels helpful - helpful-feeling is not the same as safe or qualified.

Quality bar

  • Session ends with exactly one action, dated, with observable evidence of done.
  • Confidence score asked and at 7 or above.
  • An if-then plan exists for a named obstacle.
  • The goal traces to one of the user's stated values.
  • The therapy screen ran, and anything clinical was routed out loud, not around.

Escalation

Not therapy, medical, or financial advice. Clinical signs route to a licensed professional immediately (see the boundary section). Money-decision coaching pairs with big-purchase-decision or financial-planner; habit mechanics pair with habit-builder; ongoing goal-tracking systems belong to goals-accountability.

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

SkillMedev/skills

Designs REST API surfaces - resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering - and delivers an endpoint spec a consumer can build against without asking questions. Use when someone asks "how should I name this endpoint", "what status code should this return", "should this be PUT or PATCH", "how do I paginate this list", or is reviewing an API before it ships to external consumers. Do NOT use for planning breaking-change rollouts and deprecation windows - use api-versioning-strategist instead; for GraphQL type and resolver design - use graphql-schema instead; for generating client SDKs from an existing spec - use api-client-generator instead; for designing inbound webhook endpoints - use webhook-receiver-hardener instead.

SkillMedev/skills

Turns data and charts into a decision-driving narrative structured as headline finding, trend, implication, and recommended action - with finding-led chart titles, context for every number, annotation guidance, and honest flags on any conclusion the data cannot support. Use when someone says "turn these numbers into a story", "what's the takeaway from this data", "help me present these results to leadership", or has charts but no narrative. Do NOT use for compressing a long document into a one-pager - use executive-summary instead - or for running the analysis that produces the findings - use eda-playbook instead.

SkillMedev/skills

Use when a task needs live or historical money data - "convert USD to EUR", "current/past exchange rate", "FX rate on this date / over this range", or "current price of Bitcoin/Ethereum, market cap, 24h change". Frankfurter (ECB reference rates, no key) is the FX default; CoinGecko's free keyless tier covers crypto. Do NOT use for stock quotes or equities - no keyless stock API survives verification, say so instead of guessing; do NOT use for country economic indicators like GDP or inflation series - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Builds a driver-based FP&A operating model linking business inputs to P&L, balance sheet, and cash flow outputs. Use when building an annual plan, preparing investor materials, running scenario analysis, or stress-testing the business.

SkillMedev/skills

Use when a task needs live geographic lookups - "geocode this address", "what's at these coordinates" (reverse geocoding), "lat/lon for this city", "which country/state is this ZIP or postal code in", or "country facts: capital, currency, population, flag". Nominatim (OpenStreetMap) is the geocoding default; Zippopotam for postal codes; APICountries for country facts. All keyless. Do NOT use for weather at a location - use weather-climate instead; do NOT use for country-level statistics over time (GDP, population trends) - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Runs the full Getting Things Done loop - capture, clarify, organize, reflect, engage - building a trusted system of context lists, a projects list with defined next actions, and a weekly review habit. Use when someone says "I'm overwhelmed and things are slipping through the cracks", "set up GTD for me", "help me do a brain dump and organize it", or "my to-do list is a mess". Do NOT use for just running the weekly review ritual itself - use weekly-review instead - or for clearing an email backlog - use inbox-zero.

SkillMedev/skills

Processes any email backlog to zero using the 4Ds - Delete, Delegate, Defer, Do - with a mass-archive strategy for the obvious, a touch-each-email-once discipline, and a keep-it-clear system of batched processing windows, ruthless unsubscribing, filters, and a minimal folder setup. Use when someone says "I have 5,000 unread emails", "help me get to inbox zero", "email is eating my whole day", or treats their inbox as a to-do list. Do NOT use for drafting the reply emails themselves or prioritization rules for an ongoing support queue - use email-triage instead - or for protecting focus time around the email windows - use deep-work-planner instead.

SkillMedev/skills

Classifies incident severity (SEV1-4) using impact, scope, and urgency signals and decides who to page. Use when an alert fires or a report comes in and a severity call must be made quickly.

SkillMedev/skills

Use the Skill Me catalog from inside any conversation - discover, install, and manage Claude skills through the Skill Me MCP, and load installed skills automatically each session.

SkillMedev/skills

Writes and tunes PySpark jobs - join strategy and broadcast size limits, shuffle-partition sizing, skew diagnosis and salting, UDF avoidance, caching, and output file layout - with concrete size and skew thresholds. Use when someone asks "why is my Spark job slow", "should I broadcast this join", "one task takes forever while the rest finish", "my job OOMs during a join", or is writing a new PySpark ETL job. Do NOT use for Kafka topic, consumer-group, or streaming-pipeline design - use kafka-pipelines instead; do NOT use for single-machine dataframe work that fits in memory - use pandas-expert instead.

SkillMedev/skills

Builds clean, performant, accessible SwiftUI views with correct state ownership, scoped invalidation, and smooth list scrolling, and reviews existing SwiftUI code against a concrete frame-time and re-render budget. Use when someone asks "why does my SwiftUI list stutter", "should this be @State or @Observable", "my whole screen re-renders when one row changes", "how do I animate this transition", or wants a SwiftUI view built or refactored. Do NOT use for cross-platform React Native apps - use react-native-pro instead; do NOT use for Flutter widget trees - use flutter-widget-architect instead; do NOT use for Android Compose UIs - use jetpack-compose-builder instead.

Verwandte Skills