get-claudia 1.53.2 → 1.53.4

package/CHANGELOG.md

@@ -2,6 +2,25 @@
 
 All notable changes to Claudia will be documented in this file.
 
+## 1.53.4 (2026-03-04)
+
+### The Skill Sharpening Release
+
+Systematic improvement of Claudia's 41 default skills for better contextual triggering, testing, and maintainability. Follows the Skill Creator's best practices for description-driven activation and progressive disclosure.
+
+- **Improved skill descriptions** -- 8 SKILL.md files updated with richer trigger context so Claude matches skills more accurately from natural language (meditate, new-person, draft-reply, follow-up-draft, memory-manager, pattern-recognizer, meeting-prep, weekly-review)
+- **Skill index v2 with examples** -- `skill-index.json` bumped to schema v2. All 41 entries now include `examples` arrays with 3-6 natural-language utterances for long-tail matching (e.g., "anything urgent this morning?" triggers morning-brief)
+- **Consolidated overlapping skills (43 to 41)** -- Merged `concierge` into `research/SKILL.md` (tool detection, staleness tracking, proactive offers). Merged `structure-evolution` into `capability-suggester.md` (usage gap detection, business depth upgrades, suggestion library)
+- **Eval templates for 5 skills** -- Added `evals/basic.yaml` for morning-brief, capture-meeting, new-person, diagnose, and meditate. Compatible with the Skill Creator plugin for automated quality testing
+- **Reference files for 4 skills** -- Added `references/` subdirectories for diagnose (common-issues), ingest-sources (extraction-patterns), research (source-evaluation), and new-workspace (workspace-templates). Keeps SKILL.md lean via progressive disclosure
+- **README updated** -- Documented `examples` field in schema reference, added progressive disclosure and eval documentation, updated effort level table for 41 skills
+
+## 1.53.3 (2026-03-04)
+
+### Fix: Actually restore disabled MCP servers on upgrade
+
+v1.53.2 added restore logic for `_disabled_`-prefixed keys in `mcpServers`, but an early return (`if (!config._disabled_mcpServers) return`) prevented it from running. The function now handles both migration paths independently: the `_disabled_mcpServers` stash (Path 1) and `_disabled_*` prefixed keys directly in `mcpServers` (Path 2). Path 2 is now generic and renames any `_disabled_*` key, not just gmail/google-calendar.
+
 ## 1.53.2 (2026-03-04)
 
 ### Re-enable Gmail and Calendar MCPs

package/bin/index.js

@@ -1014,31 +1014,38 @@ function restoreMcpServers(targetPath) {
   try {
     const raw = readFileSync(mcpPath, 'utf-8');
     const config = JSON.parse(raw);
-    if (!config._disabled_mcpServers) return;
     if (!config.mcpServers) config.mcpServers = {};
 
-    // Restore all previously disabled servers (memory, gmail, google-calendar)
-    const toRestore = ['claudia-memory', 'claudia_memory', 'gmail', 'google-calendar'];
     let changed = false;
     const restored = [];
 
-    for (const key of toRestore) {
-      if (config._disabled_mcpServers[key] && !config.mcpServers[key]) {
-        const serverConfig = { ...config._disabled_mcpServers[key] };
-        delete serverConfig._replaced_by;
-        delete serverConfig._warning;
-        config.mcpServers[key] = serverConfig;
-        delete config._disabled_mcpServers[key];
-        changed = true;
-        restored.push(key);
+    // Path 1: Restore from _disabled_mcpServers stash (older migration format)
+    if (config._disabled_mcpServers) {
+      const toRestore = ['claudia-memory', 'claudia_memory', 'gmail', 'google-calendar'];
+      for (const key of toRestore) {
+        if (config._disabled_mcpServers[key] && !config.mcpServers[key]) {
+          const serverConfig = { ...config._disabled_mcpServers[key] };
+          delete serverConfig._replaced_by;
+          delete serverConfig._warning;
+          config.mcpServers[key] = serverConfig;
+          delete config._disabled_mcpServers[key];
+          changed = true;
+          restored.push(key);
+        }
+      }
+
+      // Clean up _disabled_mcpServers if it's now empty
+      if (Object.keys(config._disabled_mcpServers).length === 0) {
+        delete config._disabled_mcpServers;
       }
     }
 
-    // Also rename _disabled_ prefixed keys in mcpServers itself
+    // Path 2: Rename _disabled_ prefixed keys in mcpServers itself
+    // This handles the case where keys like "_disabled_gmail" exist directly in mcpServers
     for (const key of Object.keys(config.mcpServers)) {
       if (key.startsWith('_disabled_')) {
         const realKey = key.replace('_disabled_', '');
-        if (['gmail', 'google-calendar'].includes(realKey) && !config.mcpServers[realKey]) {
+        if (!config.mcpServers[realKey]) {
           const serverConfig = { ...config.mcpServers[key] };
           delete serverConfig._warning;
           config.mcpServers[realKey] = serverConfig;
@@ -1049,14 +1056,9 @@ function restoreMcpServers(targetPath) {
       }
     }
 
-    // Clean up _disabled_mcpServers if it's now empty
-    if (config._disabled_mcpServers && Object.keys(config._disabled_mcpServers).length === 0) {
-      delete config._disabled_mcpServers;
-    }
-
     if (changed) {
       writeFileSync(mcpPath, JSON.stringify(config, null, 2) + '\n');
-      console.log(` ${colors.green}✓${colors.reset} Restored MCP servers: ${restored.join(', ')} (moved back from _disabled_mcpServers)`);
+      console.log(` ${colors.green}✓${colors.reset} Restored MCP servers: ${restored.join(', ')}`);
     }
   } catch {
     // Not valid JSON or can't read -- skip silently

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-claudia",
-  "version": "1.53.2",
+  "version": "1.53.4",
   "description": "An AI assistant who learns how you work.",
   "keywords": [
     "claudia",

package/template-v2/.claude/skills/README.md

@@ -51,10 +51,16 @@ Skills live in `.claude/skills/` and can be either:
 .claude/skills/
 └── ingest-sources/
     ├── SKILL.md          # Main skill file (required)
+    ├── references/       # Optional deep-dive content (progressive disclosure)
+    ├── evals/            # Optional eval templates (Skill Creator compatible)
     ├── templates/        # Optional supporting files
     └── examples/         # Optional examples
 ```
 
+**Progressive disclosure:** Keep SKILL.md lean (under 500 lines). Move detailed reference content into `references/` subdirectories. Claude reads these on demand when deeper context is needed.
+
+**Eval templates:** Skills can include `evals/basic.yaml` with test prompts and expectations. These are compatible with the Skill Creator plugin for automated skill quality testing.
+
 ### SKILL.md Format
 
 ```yaml
@@ -86,6 +92,9 @@ effort-level: low | medium | high | max
 triggers:                    # Natural language activation patterns
   - "pattern one"
   - "pattern two"
+examples:                    # Full natural-language utterances for matching (v2)
+  - "what should I focus on today?"
+  - "anything urgent this morning?"
 inputs:                      # Expected input data
   - name: input_name
     type: string | entity | date | file
@@ -114,6 +123,7 @@ argument-hint: [arg]
 | `description` | Yes | Used for contextual matching and skill index |
 | `effort-level` | Yes | Thinking budget: `low`, `medium`, `high`, `max` |
 | `triggers` | No | 3-5 natural language phrases that activate the skill |
+| `examples` | No | Full natural-language utterances for long-tail matching (v2) |
 | `inputs` | No | Structured input expectations (name, type, description) |
 | `outputs` | No | What the skill produces (name, type, description) |
 | `invocation` | No | `explicit`, `contextual` (default), or `proactive` |
@@ -197,7 +207,7 @@ effort-level: medium
 |--------|--------|
 | **low** | morning-brief, client-health, financial-snapshot, growth-check, databases, diagnose, brain-monitor, inbox-check, judgment-awareness |
 | **medium** | meeting-prep, draft-reply, follow-up-draft, file-document, new-person, capture-meeting, summarize-doc, memory-audit, brain, fix-duplicates, memory-health, memory-manager, onboarding, structure-generator, agent-dispatcher, new-workspace |
-| **high** | weekly-review, meditate, research, what-am-i-missing, map-connections, commitment-detector, capability-suggester, concierge, connector-discovery, pattern-recognizer, relationship-tracker, risk-surfacer, structure-evolution, hire-agent |
+| **high** | weekly-review, meditate, research, what-am-i-missing, map-connections, commitment-detector, capability-suggester, connector-discovery, pattern-recognizer, relationship-tracker, risk-surfacer, hire-agent |
 | **max** | ingest-sources, pipeline-review, deep-context |
 
 ## Creating Custom Skills

package/template-v2/.claude/skills/capability-suggester.md

@@ -1,6 +1,6 @@
 ---
 name: capability-suggester
-description: Notice repeated user behaviors and suggest new commands, workflows, or structure to streamline their work.
+description: Notice repeated user behaviors and suggest new commands, workflows, structure, or integrations to streamline work. Also detects when the user's setup has outgrown its current structure and suggests targeted upgrades. Activates when repeated task patterns, workflow friction, structural gaps, or business growth signals are detected.
 user-invocable: false
 invocation: proactive
 effort-level: high
@@ -10,22 +10,39 @@ triggers:
   - "frequent status check query"
   - "mentions checking external tool"
   - "workflow gap between steps"
+  - "files created outside existing structure"
+  - "tracking something with no home"
+  - "business complexity has grown"
+  - "workflow friction observed"
 inputs:
   - name: behavior_pattern
     type: string
-    description: Observed repeated behavior or workflow pattern
+    description: Observed repeated behavior, workflow pattern, or structural gap
 outputs:
   - name: suggestion
     type: text
-    description: Proposed enhancement (new command, workflow change, or structure addition)
+    description: Proposed enhancement (new command, workflow change, structure addition, or integration)
   - name: capability
     type: file
-    description: New skill file or structural change if user accepts the suggestion
+    description: New skill file, structural change, or template if user accepts the suggestion
 ---
 
 # Capability Suggester Skill
 
-**Triggers:** Activates when patterns of repeated behavior reach a threshold.
+**Triggers:** Activates when patterns of repeated behavior reach a threshold, or when structural gaps create friction.
+
+---
+
+## Philosophy
+
+Structure should grow organically from actual needs, not be imposed upfront. This skill watches for both repeated behaviors and structural friction, offering targeted solutions.
+
+**Core Principles:**
+- Observe before suggesting
+- One suggestion at a time, not a flood
+- Accept "no" gracefully
+- Remember declined suggestions (don't re-suggest)
+- Explain the why, not just the what
 
 ---
 
@@ -82,19 +99,48 @@ Want me to prompt for client file updates after meeting captures?"
 ### Structure Needs
 
 **Detection:**
+- Files created outside the existing structure repeatedly
 - Topics that don't have a home
 - Files that are getting too long
 - Categories that are emerging
 
 **Examples:**
 ```
-"You've mentioned 'partnerships' in several contexts but don't
-have a dedicated folder. Should we create partnerships/ ?"
+"I notice you've been saving [X] type files in random places.
+Want me to create a dedicated folder for those?"
+
+"You've created 3 client notes in /context.
+Should we set up proper client folders?"
 
 "Your patterns.md is getting long. Want me to split it into
 work-patterns.md and relationship-patterns.md?"
 ```
 
+### Business Depth Upgrades
+
+If user chose "minimal" or "starter" initially, watch for signs they need more:
+
+**Minimal to Starter:**
+- Mentions tracking multiple things manually
+- Asks about pipelines or active work lists
+- Discusses finances more than occasionally
+
+**Starter to Full:**
+- Manages 3+ active clients/projects
+- Needs accountability tracking
+- Discusses methodology or repeatable processes
+- Mentions tax planning or financial complexity
+
+**Suggest:**
+```
+"Your workflow has gotten more complex since we started. Want me to add:
+- Pipeline tracking (active, prospecting, completed)
+- Financial structure (expenses, invoicing, tax planning)
+- Templates for common tasks
+
+I can add just what you need, not everything at once."
+```
+
 ### Integration Needs
 
 **Detection:**
@@ -108,7 +154,6 @@ work-patterns.md and relationship-patterns.md?"
 - "Can you check my email/calendar/Notion..."
 - "Let me paste this from [service]..."
 - "I need to go look at [service] for..."
-- "Here's what [service] says..."
 - "Can you see my [service]?"
 
 **Response:**
@@ -123,15 +168,11 @@ your pages without the copy-paste."
 "You've asked about your email a few times. I can't see it yet,
 but I can help you set that up. Takes about 5 minutes for Gmail.
 Interested?"
-
-"I see you check your calendar separately before our morning briefs.
-Want me to include your schedule automatically? I can connect to
-Google Calendar if you'd like."
 ```
 
 **Guardrails:**
 - Only suggest once per service (check declined list in learnings.md)
-- Don't interrupt workflow-suggest at natural pause points
+- Don't interrupt workflow, suggest at natural pause points
 - If they said "maybe later" during onboarding, wait at least a week
 
 ---
@@ -145,53 +186,49 @@ Track behavior without mentioning it until threshold reached:
 - 2+ for complex workflows
 - Immediate for obvious improvements
 
-### 2. Propose Enhancement
-
-**Format:**
-```
-"I've noticed [observation].
-
-Would you like me to [specific solution]?
-
-This would [benefit]."
-```
+### 2. Wait for a Natural Moment
 
-**Examples:**
+**Good times to suggest:**
+- Start of session: "Before we dive in, I noticed something..."
+- End of weekly review: "One observation from reviewing your week..."
+- After completing a task: "That's done. Quick thought..."
+- When they mention friction: "You mentioned [X] being messy. Want me to..."
 
-```
-"I've noticed you check client health status at the start of each week.
+**Bad times:**
+- During focused work
+- When user is stressed
+- If pattern is sensitive and context is wrong
 
-Would you like me to add a client health summary to your Monday morning brief?
+### 3. Propose Enhancement
 
-This would save you from manually checking each client file."
+**Format:**
 ```
+"I've noticed [observation].
 
-```
-"You often draft follow-up emails after sales calls.
+Would you like me to [specific solution]?
 
-Would you like me to create a /sales-followup command that:
-- Uses the meeting notes as context
-- Drafts a templated follow-up
-- Suggests next steps based on the conversation
+This would [benefit].
 
-I could have this ready for your next call."
+Totally fine if not - just noticed the pattern."
 ```
 
-### 3. Accept Response
+### 4. Accept Response
 
 **If yes:**
-- Create the enhancement
-- Explain how to use it
+- Create the enhancement immediately
+- Show what was added
+- Offer a quick tour if it's substantial
 - Note in learnings.md
 
-**If no:**
-- Acknowledge gracefully
-- Don't suggest again for a while
-- Note preference in learnings.md
+**If "not now" / "maybe later":**
+- Note the suggestion and timing
+- Wait at least 2 weeks before similar suggestions
+- Acknowledge: "No problem. I'll let you know if the pattern continues."
 
-**If "maybe later":**
-- Note for future
-- Remind in a week or when context is relevant
+**If "no" / declined:**
+- Record the declined suggestion
+- Don't suggest the same thing again (unless they explicitly ask)
+- Acknowledge: "Got it. Won't mention it again."
 
 ---
 
@@ -199,26 +236,10 @@ I could have this ready for your next call."
 
 ### New Commands
 
-**Template:**
-```markdown
-# [Command Name]
-
-[Brief description of what it does]
-
-## When to Use
-[Trigger conditions]
-
-## What It Does
-[Step by step]
-
-## Output
-[What user gets]
-```
-
 **Process:**
 1. Draft command based on observed pattern
 2. Propose to user with explanation
-3. If approved, create in `.claude/commands/`
+3. If approved, create in `.claude/skills/`
 4. Confirm creation and explain usage
 
 ### Workflow Enhancements
@@ -245,22 +266,11 @@ Want me to enhance it to also:
 - Split growing files
 - Add templates for new types
 
-**Example:**
-```
-"You've started tracking vendor relationships separately from clients.
-
-Should I create:
-- vendors/ folder with similar structure to clients/
-- /vendor-status command for quick checks?"
-```
-
 ---
 
-## Learning Integration
+## Tracking Suggestions
 
-### What Gets Stored
-
-In `context/learnings.md`:
+Maintain in `context/learnings.md`:
 
 ```markdown
 ## Suggested Capabilities
@@ -268,10 +278,12 @@ In `context/learnings.md`:
 ### Accepted
 - /linkedin-quick command (created Jan 15)
 - Auto-client-update after meetings (enabled Jan 18)
+- Pipeline tracking folders (created Feb 1)
 
-### Declined
+### Declined (Don't Re-suggest)
 - Partnership folder (user prefers flat structure)
 - Automatic deadline reminders (user finds them annoying)
+- Full pipeline structure - prefers minimal
 
 ### Pending
 - Sales follow-up template (user said "maybe later" - Jan 20)
@@ -286,52 +298,106 @@ Track whether suggestions are used:
 
 ---
 
+## Suggestion Library
+
+### For Users Who Started Minimal
+
+**Pipeline Tracking:**
+```
+"You've mentioned 3 different clients this week but don't have a pipeline.
+Want me to set up tracking so you can see active work at a glance?"
+```
+
+**Financial Tracking:**
+```
+"I notice you discuss finances fairly often. Your setup is minimal right now.
+Want me to add an overview file for tracking revenue and expenses?"
+```
+
+**Commitments Tracking:**
+```
+"You've made several promises this week. Want me to set up a dedicated
+commitments tracker so nothing slips through?"
+```
+
+### For Users Who Started Starter
+
+**Full Pipeline:**
+```
+"Your pipeline is getting busier. Want me to add prospecting and completed
+tracking so you can see your full sales funnel?"
+```
+
+**Templates Library:**
+```
+"You do a lot of similar tasks. Want me to set up a templates folder with
+starting points for client intake, meeting prep, and reviews?"
+```
+
+### For All Users
+
+**Weekly Review Template:**
+```
+"You do informal weekly reviews. Want me to create a template so you hit
+the same key areas each time?"
+```
+
+**Methodology Documentation:**
+```
+"You've described how you approach [X] a few times. Want me to document it
+so you (and I) can reference it consistently?"
+```
+
+**New Folder for Recurring Content:**
+```
+"You've created several [X] files. Want me to set up a dedicated folder
+so they're easier to find?"
+```
+
+---
+
+## Frequency Limits
+
+- Maximum 1 suggestion per session (unless asked)
+- Space out suggestions over time
+- Wait 2 weeks after any suggestion before the next
+- Exception: If they ask "what should I add?" give fuller recommendations
+
+---
+
 ## Guardrails
 
 ### Don't Overwhelm
-
 - Max 1 suggestion per session (unless asked)
-- Space out suggestions over time
 - Don't repeat declined suggestions
+- Space suggestions over time
 
 ### Don't Over-Engineer
-
 - Start with simple solutions
 - Only suggest what's clearly needed
 - Avoid adding complexity for its own sake
 
 ### Respect User Style
-
 - Some users like lots of structure
 - Some prefer minimal tooling
 - Learn and adapt to their preference
 
 ---
 
-## Proactive vs. Reactive
-
-### Proactive (I bring it up)
-- When pattern is clear and benefit is obvious
-- During natural pauses in work
-- At start of session if something significant
-
-### Reactive (when asked)
-```
-User: "Is there anything you think we should add?"
-User: "What could we do to make this easier?"
-User: "Any suggestions for improving my workflow?"
-```
-
-Provide comprehensive list of observed opportunities.
-
----
-
 ## Integration
 
 ### With Pattern Recognizer
 - Feed patterns into capability analysis
 - Notice when patterns suggest tooling needs
 
+### With Commitment Detector
+- When commitments pile up without a system, suggest tracking
+- Suggest /what-am-i-missing command if not present
+
+### With Risk Surfacer
+- When risks relate to structural gaps, suggest structure
+- Missing pipeline causes capacity issues → Suggest pipeline
+
 ### With Memory Manager
 - Persist suggestions and responses
 - Track what works over time

package/template-v2/.claude/skills/capture-meeting/evals/basic.yaml

@@ -0,0 +1,27 @@
+# Capture Meeting Eval
+# Tests that meeting capture extracts structured data and files source material
+
+prompts:
+  - prompt: "Here are my notes from a call with Sarah Chen about the Q4 roadmap. She mentioned they're moving to microservices, the migration is due by March 15. I promised to send her our API docs by Friday. Also met her colleague James Wright who leads the platform team."
+    expectations:
+      - "extracts at least one commitment (send API docs by Friday)"
+      - "files the source material via memory.file before extracting"
+      - "identifies Sarah Chen and James Wright as entities"
+      - "detects the March 15 deadline"
+      - "uses structured output format with emoji headers"
+      - "asks user to confirm before storing extracted data"
+
+  - prompt: "capture this meeting"
+    context: "User provides a multi-paragraph transcript with 3 participants, 2 action items, and 1 decision"
+    expectations:
+      - "separates decisions from action items from general discussion"
+      - "attributes action items to specific people"
+      - "offers to create or update person files for participants"
+      - "stores the full transcript before extracting"
+
+  - prompt: "Here are brief notes: Quick sync with Mike. All good, no action items."
+    expectations:
+      - "handles minimal notes gracefully"
+      - "does not invent commitments or action items"
+      - "still files the source material"
+      - "keeps output proportional to input length"

package/template-v2/.claude/skills/diagnose/evals/basic.yaml

@@ -0,0 +1,34 @@
+# Diagnose Eval
+# Tests that diagnose correctly identifies common failure modes
+
+prompts:
+  - prompt: "/diagnose"
+    context: "Memory daemon is running and healthy"
+    expectations:
+      - "reports healthy status"
+      - "shows basic stats (memory count, entity count)"
+      - "does not suggest unnecessary fixes"
+      - "completes quickly (low effort level)"
+
+  - prompt: "/diagnose"
+    context: "Memory daemon is not running, MCP tools unavailable"
+    expectations:
+      - "identifies that memory tools are not available"
+      - "suggests checking .mcp.json configuration"
+      - "suggests running claudia system-health"
+      - "does not attempt to use memory tools that are unavailable"
+      - "provides actionable fix steps"
+
+  - prompt: "something seems wrong with my memory"
+    expectations:
+      - "triggers diagnose skill from natural language"
+      - "runs diagnostic checks before suggesting fixes"
+      - "provides specific error messages, not generic advice"
+      - "checks both daemon health and CLI availability"
+
+  - prompt: "/diagnose"
+    context: "Memory daemon responds but database has issues (corrupt vec0 tables)"
+    expectations:
+      - "identifies the specific failure (vec0/embedding issues)"
+      - "suggests --backfill-embeddings or database repair"
+      - "does not suggest reinstalling when the fix is simpler"