/what-am-i-missing
Surface risks, blind spots, overlooked items, and accountability across commitments and relationships. Triggers on "what am I overlooking?", "blind spots", "what's falling through the cracks", "what do I owe?", "am I overdue?", "check my commitments". See also: `risk-surfacer`
$ npx -y skills add kbanc85/claudia --skill what-am-i-missing --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
/what-am-i-missing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Surface risks, blind spots, overlooked items, and accountability across commitments and relationships. Triggers on "what am I overlooking?", "blind spots", "what's falling through the cracks", "what do I owe?", "am I overdue?", "check my commitments". See also: `risk-surfacer`
SKILL.md
what-am-i-missing.SKILL.mdname: what-am-i-missing
description: Surface risks, blind spots, overlooked items, and accountability across commitments and relationships. Triggers on "what am I overlooking?", "blind spots", "what's falling through the cracks", "what do I owe?", "am I overdue?", "check my commitments". See also: `risk-surfacer` for the proactive auto-firing version on overdue items and cooling relationships.
argument-hint: "[person name or 'overdue']"
effort-level: high
What Am I Missing
Surface risks, blind spots, overlooked items, and accountability across all areas.
What to Check
1. Commitment Risks
From `context/commitments.md`:
- Overdue items
- Items at risk (due soon, no progress)
- Patterns of slippage
- Cascading delays
2. Relationship Risks
From `people/` files:
- Cooling relationships (60+ days)
- Unfulfilled promises to key people
- Sentiment shifts detected
- Key relationships not nurtured
3. Waiting Risks
From `context/waiting.md`:
- Overdue items from others
- Critical dependencies at risk
- Patterns (chronic late deliverers)
4. Pattern Risks
From `context/patterns.md`:
- Recurring issues not addressed
- Blind spots observed
- Capacity concerns
- Self-limiting patterns
5. Strategic Risks
Looking at the bigger picture:
- Important-but-not-urgent items being neglected
- Opportunities cooling
- Decisions being avoided
6. Data Consistency Check
Cross-reference memory DB against file state to catch divergence:
- Run `claudia memory recall "project status commitments" --project-dir "$PWD" --limit 10`
- Compare recalled statuses (interview completion, deliverable state) against file-based trackers
- For any active project with a dashboard/README tracker, grep actual file statuses and compare to stated counts
- Flag contradictions: "Memory says X is completed, but tracker shows it outstanding" (or vice versa)
- Recommend correction path: update the stale source to match the authoritative one
This step catches the scenario where an interview/task was processed but only some status sources were updated.
Output Format
## What You Might Be Missing - [Date]
### Commitment Risks
**Overdue:**
- [Item] was due [date] - [impact]
**At Risk:**
- [Item] due [date] - [concern]
### Relationship Risks
**Cooling:**
- [Person] - last contact [X] days ago
-> Was: [relationship context]
-> Risk: [what could happen]
**Open Loops:**
- Promised [thing] to [person] - [status]
### Waiting Risks
**Overdue from Others:**
- [Item] from [person] - expected [date]
-> Impact: [why this matters]
-> Suggested action: [what to do]
### Pattern Risks
- [Pattern] - seen [X] times recently
-> Concern: [why it matters]
-> Suggestion: [what to consider]
### Strategic Blind Spots
- [Thing being neglected]
-> Why it matters: [impact]
-> Suggestion: [action]
### By Relationship
#### [Person/Client Name]
**I Owe:**
- [Item] - due [Date]
**They Owe:**
- [Item] - since [Date]
[Repeat for key relationships with open items]
**Recovery Actions:**
- [Overdue item]: [What to do now]
### Data Consistency
- [Source A] says [X], but [Source B] says [Y]
-> Authoritative source: [which one and why]
-> Fix: Update [stale source] to match
### Summary
Critical: [X items need immediate attention]
Watch: [Y items to keep an eye on]
Consider: [Z strategic things to think about]
Consistency: [N data mismatches found across sources]
Tone
- Matter-of-fact, not alarmist
- Specific, not vague
- Actionable suggestions
- Prioritized by importance
- Respectful of user's judgment
When to Use
- When feeling overwhelmed and wanting perspective
- Before important planning sessions
- When something feels "off" but unclear what
- As a regular check-in (weekly or biweekly)
Usage Variations
**Full analysis:** Comprehensive review across all risk categories and relationships.
**For specific person:** `/what-am-i-missing [person name]` Filters to only show commitments and risks involving that person.
**Quick overdue only:** `/what-am-i-missing overdue` Shows only overdue items and immediate recovery actions.
**Quick check:** Major risks only, no deep analysis.
Read more
name: what-am-i-missing description: Surface risks, blind spots, overlooked items, and accountability across commitments and relationships. Triggers on "what am I overlooking?", "blind spots", "what's falling through the cracks", "what do I owe?", "am I overdue?", "check my commitments". See also: `risk-surfacer` for the proactive auto-firing version on overdue items and cooling relationships. argument-hint: "[person name or 'overdue']" effort-level: high
What Am I Missing
Surface risks, blind spots, overlooked items, and accountability across all areas.
What to Check
1. Commitment Risks
From `context/commitments.md`:
- Overdue items
- Items at risk (due soon, no progress)
- Patterns of slippage
- Cascading delays
2. Relationship Risks
From `people/` files:
- Cooling relationships (60+ days)
- Unfulfilled promises to key people
- Sentiment shifts detected
- Key relationships not nurtured
3. Waiting Risks
From `context/waiting.md`:
- Overdue items from others
- Critical dependencies at risk
- Patterns (chronic late deliverers)
4. Pattern Risks
From `context/patterns.md`:
- Recurring issues not addressed
- Blind spots observed
- Capacity concerns
- Self-limiting patterns
5. Strategic Risks
Looking at the bigger picture:
- Important-but-not-urgent items being neglected
- Opportunities cooling
- Decisions being avoided
6. Data Consistency Check
Cross-reference memory DB against file state to catch divergence:
- Run `claudia memory recall "project status commitments" --project-dir "$PWD" --limit 10`
- Compare recalled statuses (interview completion, deliverable state) against file-based trackers
- For any active project with a dashboard/README tracker, grep actual file statuses and compare to stated counts
- Flag contradictions: "Memory says X is completed, but tracker shows it outstanding" (or vice versa)
- Recommend correction path: update the stale source to match the authoritative one
This step catches the scenario where an interview/task was processed but only some status sources were updated.
Output Format
## What You Might Be Missing - [Date] ### Commitment Risks **Overdue:** - [Item] was due [date] - [impact] **At Risk:** - [Item] due [date] - [concern] ### Relationship Risks **Cooling:** - [Person] - last contact [X] days ago -> Was: [relationship context] -> Risk: [what could happen] **Open Loops:** - Promised [thing] to [person] - [status] ### Waiting Risks **Overdue from Others:** - [Item] from [person] - expected [date] -> Impact: [why this matters] -> Suggested action: [what to do] ### Pattern Risks - [Pattern] - seen [X] times recently -> Concern: [why it matters] -> Suggestion: [what to consider] ### Strategic Blind Spots - [Thing being neglected] -> Why it matters: [impact] -> Suggestion: [action] ### By Relationship #### [Person/Client Name] **I Owe:** - [Item] - due [Date] **They Owe:** - [Item] - since [Date] [Repeat for key relationships with open items] **Recovery Actions:** - [Overdue item]: [What to do now] ### Data Consistency - [Source A] says [X], but [Source B] says [Y] -> Authoritative source: [which one and why] -> Fix: Update [stale source] to match ### Summary Critical: [X items need immediate attention] Watch: [Y items to keep an eye on] Consider: [Z strategic things to think about] Consistency: [N data mismatches found across sources]
Tone
- Matter-of-fact, not alarmist
- Specific, not vague
- Actionable suggestions
- Prioritized by importance
- Respectful of user's judgment
When to Use
- When feeling overwhelmed and wanting perspective
- Before important planning sessions
- When something feels "off" but unclear what
- As a regular check-in (weekly or biweekly)
Usage Variations
**Full analysis:** Comprehensive review across all risk categories and relationships.
**For specific person:** `/what-am-i-missing [person name]` Filters to only show commitments and risks involving that person.
**Quick overdue only:** `/what-am-i-missing overdue` Shows only overdue items and immediate recovery actions.
**Quick check:** Major risks only, no deep analysis.
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 - /client-health
Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
Open skill

