Coaching Bridge — Cross-Plugin Insight Sharing
From inner-gamenpx claudepluginhub tenfourty/cc-marketplace --plugin inner-gameThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
This skill defines how the inner-game life coach shares and consumes coaching observations with the Chief of Staff plugin. Both plugins use kbx as their shared memory layer.
The inner-game coach sees whole-life patterns: health scores, relationship quality, stress spirals, identity alignment, energy arcs. The CoS advisor sees work patterns: hero mode, decision avoidance, meeting overload, energy through a professional lens. Neither can build on the other's observations without a shared persistence format.
Directory: memory/coaching/insights/
Both plugins write to and read from this directory. Files are auto-indexed by kbx and discoverable via search and tags.
---
title: "[Brief insight title]"
date: YYYY-MM-DD
tags: [coaching-insight, <source-tag>, <signal-type>]
source_plugin: inner-game | chief-of-staff
source_agent: coach | advisor
signal_type: pattern | state | connection | observation
supersedes: "YYYY-MM-DD-<slug>" # optional — only for state signals replacing a previous one
---
[2-5 sentences. Specific, dated, actionable. Reference actual journal entries, scores, sessions, or behaviours.]
Every insight gets coaching-insight plus:
| Tag | Meaning |
|---|---|
ig-insight | Written by inner-game |
cos-insight | Written by chief-of-staff |
pattern | Recurring behaviour observed across multiple data points |
state | Current emotional/energy/stress state signal |
connection | Cross-domain link the other plugin should know about |
observation | One-off notable observation (not yet a pattern) |
| Type | What to Write | Example |
|---|---|---|
| pattern | Behaviour seen across multiple journal entries or sessions | "Gratitude entries have mentioned work accomplishments exclusively for 3 weeks — Fun & Adventure and Relationships completely absent" |
| state | Current emotional/energy state that affects work coaching | "Persister stress sequence active — increasingly critical, withdrawing. Energy scores: 4, 3, 3 over the last 3 days." |
| connection | A link between life domains and work performance | "Health score dropped from 6 to 3 over 4 weeks. Sleep deprivation correlates with the period of 3 concurrent initiative overcommitment." |
| observation | Notable one-off signal worth sharing | "Evening journal revealed deep frustration about 'not being heard' in leadership meetings — first time this theme has surfaced" |
Write a coaching insight when:
After /inner-game:session (Step 7): If the session surfaces a pattern or state that has work performance implications. Not every session produces a cross-plugin insight — only write when something is genuinely useful for the work advisor.
After /inner-game:review (Step 5): If the weekly/monthly review reveals energy trends, alignment gaps, or domain scores that connect to work patterns.
After /inner-game:wheel: If Wheel of Life scores reveal significant changes (2+ point drops) or persistent lows that affect work domains (Career, Health, Inner Life).
After /inner-game:evening: Only if a clear state signal emerges from repeated patterns across 3+ days (e.g., declining energy, recurring frustration theme). Do NOT write an insight after every evening entry.
Do NOT write:
Write directly to memory/coaching/insights/YYYY-MM-DD-<slug>.md with proper frontmatter using the Write tool. kbx will auto-index it on next search.
Keep insights to 2-5 sentences. Be specific — reference dates, scores, journal entries, sessions.
Read CoS insights during:
/inner-game:boot context loading (Step 1): Search for recent CoS insights alongside other coaching context.
kbx search "coaching-insight" --tag cos-insight --fast --json --limit 5
/inner-game:session context loading (Step 1): Check for work-pattern signals that inform the coaching conversation.
/inner-game:review data gathering (Step 2): Include CoS insights in the period's analysis.
/inner-game:morning context loading (Step 1): Only recent state signals (last 48h) — weave into the morning orientation if present.
kbx search "coaching-insight" --tag cos-insight --tag state --from YYYY-MM-DD --fast --json --limit 3
Where YYYY-MM-DD is 2 days ago. Keep it light — only state signals, not patterns or connections.
When the inner-game coach reads a CoS insight:
Never reference CoS insights as "your work advisor noticed..." — integrate them naturally. The user experiences one continuous relationship with you, not a system of interconnected agents.
supersedes: "YYYY-MM-DD-<slug>" to the frontmatter. Consumers skip superseded files — only the latest state in a chain is current. This keeps old states for history without polluting active reads./inner-game:review and CoS /review) are natural points to check if previous insights are still current — and to write superseding state signals when a state has shifted