/client-health
Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
$ npx -y skills add kbanc85/claudia --skill client-health --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/client-health
Context preview
The summary Claude sees to decide when to auto-load this skill.
Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
SKILL.md
client-health.SKILL.mdname: client-health
description: Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
argument-hint: "[client name or 'summary']"
effort-level: low
Client Health
Health check across all active client engagements. Available for Consultant and Solo Professional archetypes.
What to Check
For each client folder in `clients/`:
1. Engagement Health
- Current status and phase
- Milestone progress (if milestone-plan.md exists)
- Any overdue deliverables
- Contract/engagement end dates approaching
2. Relationship Health
- Last contact date
- Communication frequency
- Stakeholder sentiment (if stakeholders.md exists)
- Any concerns or red flags
3. Commitment Status
- Open commitments from overview.md
- Overdue items
- Items waiting on client
- Upcoming deliverables
4. Financial Health (if tracked)
- Outstanding invoices
- Payment status
- Upcoming billing
5. Blockers (if blockers.md exists)
- Active blockers
- Resolution progress
- Impact on deliverables
Output Format
## Client Health - [Date]
### Summary
| Status | Count | Details |
|--------|-------|---------|
| On Track | X | [Names] |
| Attention Needed | X | [Names] |
| At Risk | X | [Names] |
- **Total active clients:** X
- **Open commitments:** X
- **Overdue items:** X
- **Outstanding invoices:** $X
---
### On Track
#### [Client Name]
**Phase:** [Current phase]
**Last Contact:** [Date]
**Health:** All good
**Active Work:**
- [Deliverable] - on track for [Date]
**Open Items:** X (none overdue)
---
### Attention Needed
#### [Client Name]
**Phase:** [Current phase]
**Last Contact:** [Date] - X days ago
**Health:** Needs attention
**Concerns:**
- [Issue 1]
- [Issue 2]
**Open Items:**
- [Overdue or at-risk item]
**Suggested Action:**
- [What to do]
---
### At Risk
#### [Client Name]
**Phase:** [Current phase]
**Issues:**
- [Critical issue]
- [Critical issue]
**Immediate Actions:**
1. [Urgent action]
2. [Follow-up action]
---
### Cross-Client View
#### Deliverables Due This Week
| Client | Deliverable | Due | Status |
|--------|-------------|-----|--------|
| | | | On Track / At Risk / Overdue |
#### Outstanding Invoices
| Client | Amount | Sent | Due | Status |
|--------|--------|------|-----|--------|
| | $X | [Date] | [Date] | Outstanding / Overdue |
#### Relationships Needing Touch
| Client | Last Contact | Days | Suggested Action |
|--------|--------------|------|------------------|
| | [Date] | X | [Action] |
---
### Patterns
- [Cross-client observation]
- [Recurring issue across clients]
### Capacity Check
- **Current active clients:** X
- **Total active engagements:** X
- **Hours committed this week:** X
- **Available bandwidth:** [Assessment]
- **Upcoming endings:** [Client] ends [Date]
- **Pipeline:** X prospects (see /pipeline-review)
Health Scoring
On Track
- Recent contact (within expected cadence)
- No overdue deliverables
- Positive or neutral stakeholder sentiment
- No active blockers
- Invoices paid or not yet due
Attention Needed
- Contact overdue by 1 week+
- Deliverable at risk (due soon, not complete)
- Stakeholder concerns raised
- Minor blocker active
- Invoice overdue by less than 2 weeks
At Risk
- Contact overdue by 2+ weeks
- Deliverable overdue
- Stakeholder actively unhappy
- Major blocker preventing progress
- Invoice overdue by 2+ weeks
- Engagement ending without renewal discussion
Tone
- Factual, scannable
- Lead with concerns (don't bury bad news)
- Specific action suggestions
- Don't sugarcoat problems
- Acknowledge what's going well
When to Run
- Weekly (Monday or Friday)
- Before client meetings (filtered to that client)
- When feeling uncertain about client status
- During weekly review
Usage Variations
**All clients:**
/client-health
**Specific client:**
/client-health [client name]
Deep dive on single client with full history.
**Quick overview:**
/client-health summary
Just the summary stats and any red/yellow flags.
Read more
name: client-health description: Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check". argument-hint: "[client name or 'summary']" effort-level: low
Client Health
Health check across all active client engagements. Available for Consultant and Solo Professional archetypes.
What to Check
For each client folder in `clients/`:
1. Engagement Health
- Current status and phase
- Milestone progress (if milestone-plan.md exists)
- Any overdue deliverables
- Contract/engagement end dates approaching
2. Relationship Health
- Last contact date
- Communication frequency
- Stakeholder sentiment (if stakeholders.md exists)
- Any concerns or red flags
3. Commitment Status
- Open commitments from overview.md
- Overdue items
- Items waiting on client
- Upcoming deliverables
4. Financial Health (if tracked)
- Outstanding invoices
- Payment status
- Upcoming billing
5. Blockers (if blockers.md exists)
- Active blockers
- Resolution progress
- Impact on deliverables
Output Format
## Client Health - [Date] ### Summary | Status | Count | Details | |--------|-------|---------| | On Track | X | [Names] | | Attention Needed | X | [Names] | | At Risk | X | [Names] | - **Total active clients:** X - **Open commitments:** X - **Overdue items:** X - **Outstanding invoices:** $X --- ### On Track #### [Client Name] **Phase:** [Current phase] **Last Contact:** [Date] **Health:** All good **Active Work:** - [Deliverable] - on track for [Date] **Open Items:** X (none overdue) --- ### Attention Needed #### [Client Name] **Phase:** [Current phase] **Last Contact:** [Date] - X days ago **Health:** Needs attention **Concerns:** - [Issue 1] - [Issue 2] **Open Items:** - [Overdue or at-risk item] **Suggested Action:** - [What to do] --- ### At Risk #### [Client Name] **Phase:** [Current phase] **Issues:** - [Critical issue] - [Critical issue] **Immediate Actions:** 1. [Urgent action] 2. [Follow-up action] --- ### Cross-Client View #### Deliverables Due This Week | Client | Deliverable | Due | Status | |--------|-------------|-----|--------| | | | | On Track / At Risk / Overdue | #### Outstanding Invoices | Client | Amount | Sent | Due | Status | |--------|--------|------|-----|--------| | | $X | [Date] | [Date] | Outstanding / Overdue | #### Relationships Needing Touch | Client | Last Contact | Days | Suggested Action | |--------|--------------|------|------------------| | | [Date] | X | [Action] | --- ### Patterns - [Cross-client observation] - [Recurring issue across clients] ### Capacity Check - **Current active clients:** X - **Total active engagements:** X - **Hours committed this week:** X - **Available bandwidth:** [Assessment] - **Upcoming endings:** [Client] ends [Date] - **Pipeline:** X prospects (see /pipeline-review)
Health Scoring
On Track
- Recent contact (within expected cadence)
- No overdue deliverables
- Positive or neutral stakeholder sentiment
- No active blockers
- Invoices paid or not yet due
Attention Needed
- Contact overdue by 1 week+
- Deliverable at risk (due soon, not complete)
- Stakeholder concerns raised
- Minor blocker active
- Invoice overdue by less than 2 weeks
At Risk
- Contact overdue by 2+ weeks
- Deliverable overdue
- Stakeholder actively unhappy
- Major blocker preventing progress
- Invoice overdue by 2+ weeks
- Engagement ending without renewal discussion
Tone
- Factual, scannable
- Lead with concerns (don't bury bad news)
- Specific action suggestions
- Don't sugarcoat problems
- Acknowledge what's going well
When to Run
- Weekly (Monday or Friday)
- Before client meetings (filtered to that client)
- When feeling uncertain about client status
- During weekly review
Usage Variations
**All clients:**
/client-health
**Specific client:**
/client-health [client name]
Deep dive on single client with full history.
**Quick overview:**
/client-health summary
Just the summary stats and any red/yellow flags.
Terminal-based AI chief of staff. Remembers relationships, tracks commitments, helps you think strategically. Runs on Claude Code.
Repo: kbanc85/claudia
Other skills on claudia.
- /auto-research
Iteratively improve a local artifact (draft, document, page) by running a hill-climbing loop. The user names the artifact, the evaluator, and the budget. Claudia edits the artifact, scores it, keeps it if better or reverts if worse, repeats. Use when user says "iterate on this",
Open skill - /brain-monitor
Launch the Brain Monitor TUI, a real-time terminal dashboard for watching Claudia's memory system. Triggers on "brain monitor", "show dashboard", "memory dashboard", "terminal brain". See also: `brain` for a 3D graph view in the browser.
Open skill - /brain
Launch the Brain Visualizer, a real-time 3D view of memory and relationships. Triggers on "show your brain", "visualize memory", "open the brain", "memory graph". See also: `brain-monitor` for a terminal dashboard alternative.
Open skill - /build-team
Propose a personalized team of specialized agents based on the user's profile, goals, and how they actually work. Runs the proposal through an independent Checker, gates on the user's approval, and applies with rollback. Use when the user says "build my team", "set up my
Open skill - /capture-meeting
Process meeting notes or transcript to extract decisions, commitments, and insights. Use when user shares transcript or says "capture this meeting", "here are my notes from the call". See also: `meeting-prep` for pre-call briefings; `follow-up-draft` for post-meeting emails.
Open skill - /databases
View all Claudia memory databases, switch between them, manage isolation. Triggers on "which database?", "switch workspace", "show databases", "list databases".
Open skill

