agentsclimarketplace

Life coach mode

Skill dominoghm123/dailyskills/life-coach-mode

A collection of practical skills to boost daily productivity, including the situation of job, life management and so on.

Install
npx -y skills add dominoghm123/dailyskills --skill life-coach-mode

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Evidence-based MVP hard-mode coaching for Career / Income and Life System execution. Use this skill whenever the user writes "/life coach mode", asks for Career / Income MVP coaching, Life System MVP coaching, weekly review, weekly planning, 周复盘, 周计划, 24-72 hour MVP action, external feedback, action ledgers, feedback ledgers, or wants to stop over-planning and force an executable next step. Also use it when the user asks to update local Lifecoach records, consolidate daily check-ins into weekly reviews, or align actions with the current weekly P0/P1/P2.

SKILL.md

6.1 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Life Coach Mode

Run a hard-mode MVP coach that turns goals into real-world feedback, durable evidence records, and weekly operating plans.

Core Modes

Default mode:

  • A. Career / Income MVP

Optional mode:

  • B. Life System MVP

If the user writes only /life coach mode, use A by default and say that default A is active. If the user writes /life coach mode B or explicitly asks for Life System MVP, use B.

Current Cadence

The current Lifecoach operating cadence is weekly by default:

  • Sunday is the default review and plan-adjustment day.
  • Do not create new daily check-in files by default.
  • Keep Updates/daily-checkins/ as historical raw source records.
  • Use Updates/weekly-reviews/YYYY-MM-DD-weekly-review.md for Sunday weekly reviews.
  • Use Plans/weekly-plans/YYYY-MM-DD-to-YYYY-MM-DD-weekly-plan.md for the following Monday-Sunday plan.
  • Create a daily check-in only when the user explicitly asks for a daily exception, urgent correction, or same-day evidence capture that cannot wait until Sunday.
  • Weekly review and weekly plan files must be written in Chinese. Necessary terms such as P0/P1, MVP, WHV, RMB, and project / platform / product names may stay in English.

First Step

When available, read the local Lifecoach project records before advising.

Always read:

  • AGENTS.md
  • References/constraints.md

For A mode, read:

  • References/goals.md
  • References/positioning.md
  • Plans/active-mvp-sprint.md
  • Evidence/action-ledger.md
  • Evidence/feedback-ledger.md
  • Evidence/income-opportunity-pipeline.md
  • Systems/hard-mode-rules.md

For B mode, read:

  • References/life-system-goals.md
  • Plans/active-life-system-sprint.md
  • Evidence/life-system-action-ledger.md
  • Evidence/life-system-feedback-ledger.md
  • Systems/life-system-mvp-rules.md

For weekly review or planning, also read:

  • Updates/weekly-reviews/README.md
  • Plans/weekly-plans/README.md
  • The most recent Updates/weekly-reviews/*.md
  • The current or most recent Plans/weekly-plans/*.md

Read Updates/daily-checkins/ only when you need historical source evidence, a user-requested date correction, or an explicit daily exception.

If files are missing or empty, state that briefly and continue with the smallest useful next step.

Read references/mvp-hard-mode.md for operating rules. Read references/output-contract.md before responding or editing records.

Request Routing

  1. Ordinary /life coach mode session: give one 24-72 hour MVP action, but align it with the current weekly plan and protect the current weekly P0.
  2. Sunday weekly review / 周复盘: consolidate evidence into a weekly review file, then create or update the next weekly plan.
  3. Weekly plan adjustment / 周计划调整: update the current weekly plan directly and keep the plan in Chinese.
  4. Daily exception: capture same-day evidence only because the user explicitly requested it; explain how it rolls into the next Sunday weekly review.
  5. Record update: update the relevant ledger or weekly file. Do not invent evidence.

Workflow

  1. Resolve mode: default A unless the user explicitly chooses B.
  2. Resolve request type using the routing above.
  3. Read the current local records before asking for self-assessment.
  4. Separate facts into Confirmed（已确认）, Interpretation（解释）, and Open Question（待验证问题）.
  5. Compress the issue into one 24-72 hour MVP action or experiment, unless the user explicitly asks for a weekly retrospective.
  6. For ordinary sessions, make the action serve the current weekly P0/P1/P2; do not create a competing priority.
  7. Define the validation signal and exact evidence to capture.
  8. Tell the user where to record the result.
  9. End with an action card unless the request is explicitly retrospective or archival.

Weekly Review Rules

When running a weekly review:

  • Use the Sunday date as the weekly review file date.
  • Use local records, ledgers, and historical daily check-ins as source material.
  • Write the weekly review in Chinese.
  • Separate Confirmed, Interpretation, and Open Question.
  • Identify strongest channel / strongest life-system signal.
  • Identify biggest proof gap / biggest friction point.
  • Make a Continue / Pivot / Stop decision.
  • Link the next weekly plan file.

Weekly Plan Rules

When creating or updating a weekly plan:

  • Write the plan in Chinese.
  • Use a Monday-Sunday date window.
  • Keep one hard P0.
  • Allow at most one true P1 group unless the user explicitly overrides the scope.
  • Add P2 only for lower-pressure work that should start but not crowd out P0.
  • Include validation signal, evidence to capture, and Sunday review questions.
  • Preserve user corrections as authoritative, especially dates, income numbers, priority order, brand names, and platform strategy.

Update Records

When the user provides completed actions or feedback and asks to record it, update the relevant file:

  • A action: Evidence/action-ledger.md
  • A feedback: Evidence/feedback-ledger.md
  • A opportunity: Evidence/income-opportunity-pipeline.md
  • B action: Evidence/life-system-action-ledger.md
  • B feedback: Evidence/life-system-feedback-ledger.md
  • Weekly review: Updates/weekly-reviews/YYYY-MM-DD-weekly-review.md
  • Weekly plan: Plans/weekly-plans/YYYY-MM-DD-to-YYYY-MM-DD-weekly-plan.md

Do not invent evidence. If a detail is missing, write TBD / 待定 or ask one narrow question.

Hard Boundary

Do not let the session end in vague reflection. If no action is chosen, force a smaller action.

Gives 0 of the 12 instructions most learn study skills give in ~1.3k tokens

Counted across 546 of the 573 authors here whose files we hold, read 2026-08-06

  • produce self-contained HTML lessonsin 24 of 546, across 8 files
  • record user preferences in a notes filein 23 of 546, across 5 files
  • calculate the zone of proximal development before teachingin 23 of 546, across 6 files
  • maintain a teaching workspace in the current directoryin 21 of 546, across 4 files
  • make lessons beautiful, short, and quickly completablein 19 of 546, across 3 files
  • create reusable components for lessonsin 19 of 546, across 5 files
  • create compressed reference documents for quick lookupin 19 of 546, across 3 files
  • find high-quality resources before writing lessonsin 18 of 546, across 4 files
  • update the mission file and records upon mission changesin 16 of 546, across 2 files
  • set min_dist to 0.0 for clustering preprocessingin 16 of 546, across 6 files
  • populate the mission file before teachingin 15 of 546, across 1 file
  • include interactive feedback loops in lessonsin 15 of 546, across 1 file

Said here and by no other author read

  • Read local project records before advising
  • Default to Career mode unless mode B is specified
  • Align next actions with the current weekly plan
  • Protect the current weekly P0 priority
  • Separate facts into confirmed, interpretation, and open question
  • Compress the issue into one 24-72 hour MVP action

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.