@soleri/forge 9.10.0 → 9.12.1

package/dist/skills/soleri-build-skill/SKILL.md

@@ -0,0 +1,210 @@
+---
+name: soleri-build-skill
+description: >
+  Use when creating a new skill, updating an existing skill, or scaffolding a skill
+  template for a Soleri agent. Triggers on "create a skill", "new skill", "build skill",
+  "add a skill", "write a skill", "skill template", "scaffold skill".
+---
+
+# Build Skill — Create Skills for Soleri Agents
+
+Create well-structured skills that follow Soleri conventions. Skills are SKILL.md files in the forge that get synced to agents as slash commands.
+
+## Skill Anatomy
+
+Skills live in two places:
+
+| Location                                           | Purpose                    |
+| -------------------------------------------------- | -------------------------- |
+| `packages/forge/src/skills/soleri-{name}/SKILL.md` | Source — ships with Soleri |
+| `~/.claude/skills/{agent}-soleri-{name}/SKILL.md`  | Runtime — synced per agent |
+
+### File Structure
+
+```yaml
+---
+name: soleri-{skill-name}
+description: >
+  Use when the user says "trigger1", "trigger2", "trigger3",
+  or wants to [brief purpose]. [One sentence about what the skill does].
+---
+
+# Skill Title — Short Purpose
+
+[Core workflow instructions with numbered steps]
+
+## Agent Tools Reference
+
+| Op | When to Use |
+|----|-------------|
+| `search_intelligent` | Check vault before starting |
+| `capture_knowledge` | Persist patterns worth remembering |
+```
+
+## Creation Process
+
+### Step 1: Search Vault for Prior Art
+
+Before creating anything, check if a similar skill or pattern exists:
+
+```
+YOUR_AGENT_core op:search_intelligent
+  params: { query: "<skill topic>" }
+```
+
+List existing skills to avoid duplication:
+
+```bash
+ls packages/forge/src/skills/
+```
+
+### Step 2: Check Trigger Keywords
+
+Every skill needs 4-8 unique trigger phrases in the `description:` field. Before choosing triggers, check ALL existing skills to avoid overlap:
+
+```bash
+grep -h "description:" packages/forge/src/skills/soleri-*/SKILL.md
+```
+
+Rules:
+
+- No trigger phrase may appear in more than one skill
+- Use quoted phrases: `"exact trigger words"`
+- Cover the full intent range — think about how users naturally ask for this
+- Avoid generic words that overlap with other skills (e.g., "review" is used by deep-review)
+
+### Step 3: Design the Workflow
+
+Identify 3-5 concrete scenarios. Ask the user if unclear:
+
+- "What exact phrases should trigger this skill?"
+- "Walk me through one example end-to-end"
+- "What should this skill NOT do?"
+
+### Step 4: Wire In Engine Ops
+
+Every Soleri skill should use the engine where applicable. Use the `YOUR_AGENT_core` placeholder — it gets replaced with the agent's actual facade name at sync time.
+
+Common integration points:
+
+| When                 | Op                            | Why                               |
+| -------------------- | ----------------------------- | --------------------------------- |
+| Before starting work | `search_intelligent`          | Check vault for prior art         |
+| Before starting work | `memory_search`               | Check session history             |
+| During execution     | `brain_recommend`             | Get brain recommendations         |
+| After completion     | `capture_knowledge`           | Persist patterns learned          |
+| After completion     | `capture_quick`               | Fast capture for simple learnings |
+| Quality checks       | `admin_health`                | Verify system health              |
+| Iteration tracking   | `loop_start` / `loop_iterate` | Track multi-step work             |
+
+### Available Facades
+
+All ops use the `YOUR_AGENT_core` placeholder:
+
+| Domain                 | Key Ops                                                                                             |
+| ---------------------- | --------------------------------------------------------------------------------------------------- |
+| Vault search & capture | `search_intelligent`, `search`, `capture_knowledge`, `capture_quick`, `vault_tags`, `vault_domains` |
+| Admin & health         | `admin_health`, `admin_diagnostic`, `admin_tool_list`, `admin_vault_analytics`                      |
+| Curator & quality      | `curator_health_audit`, `curator_detect_duplicates`, `curator_contradictions`, `curator_groom_all`  |
+| Brain & learning       | `brain_stats`, `brain_strengths`, `brain_recommend`, `brain_build_intelligence`                     |
+| Memory & sessions      | `memory_search`, `memory_stats`, `session_capture`, `memory_cross_project_search`                   |
+| Planning               | `create_plan`, `approve_plan`, `plan_split`, `plan_reconcile`, `plan_complete_lifecycle`            |
+| Loops & validation     | `loop_start`, `loop_iterate`, `loop_complete`, `loop_status`                                        |
+
+### Step 5: Write the Skill
+
+Follow these rules:
+
+**Naming:**
+
+- Folder: `packages/forge/src/skills/soleri-{name}/SKILL.md`
+- `name:` field must be `soleri-{name}` — matching the folder
+- All Soleri skills use the `soleri-` prefix
+
+**Frontmatter:**
+
+- `description:` must include specific trigger phrases in quotes
+- Use `>` for multi-line YAML folded scalar descriptions
+
+**Body (target 1,500-2,000 words):**
+
+- Imperative form ("Search the vault", not "You should search")
+- Numbered steps with concrete op examples including params
+- Agent Tools Reference table at the end
+- Common Mistakes section if applicable
+
+**Op References:**
+
+- Always use `YOUR_AGENT_core op:xxx` — never hardcode agent names
+- Include example params where helpful
+- Only reference ops that actually exist (verify with `admin_tool_list`)
+
+### Step 6: Validate
+
+Checklist before committing:
+
+- [ ] Folder is `soleri-{name}/SKILL.md` in `packages/forge/src/skills/`
+- [ ] `name:` matches folder name
+- [ ] `description:` has 4-8 specific trigger phrases in quotes
+- [ ] No trigger overlap with existing skills
+- [ ] All ops use `YOUR_AGENT_core` placeholder
+- [ ] No hardcoded agent names (`ernesto_core`, `salvador_core`, etc.)
+- [ ] Imperative writing style throughout
+- [ ] Agent Tools Reference table at the end
+- [ ] Under 3,000 words (ideally 1,500-2,000)
+- [ ] TypeScript compiles: `npx tsc --noEmit` in packages/forge
+
+### Step 7: Copy to Reference Agent
+
+If the skill should appear in the reference agent:
+
+```bash
+cp -r packages/forge/src/skills/soleri-{name} examples/reference-agent/skills/
+```
+
+### Step 8: Register in Scaffold Pipeline
+
+Add the skill to `SKILLS_REGISTRY` in `packages/forge/src/scaffold-filetree.ts` and `SKILL_CATEGORIES` in `packages/forge/src/compose-claude-md.ts` so it gets included in new scaffolds.
+
+### Step 9: Capture the Decision
+
+```
+YOUR_AGENT_core op:capture_knowledge
+  params: {
+    title: "New skill: soleri-{name} — {purpose}",
+    description: "Created skill for {what it does}. Triggers: {triggers}.",
+    type: "workflow",
+    domain: "tooling",
+    tags: ["skill", "workflow", "{domain}"]
+  }
+```
+
+## Updating Existing Skills
+
+1. Read the current file first
+2. Search vault for related patterns or feedback
+3. Make targeted changes — don't rewrite the whole skill
+4. Verify all ops still use `YOUR_AGENT_core` placeholder
+5. Update `description:` if triggers changed
+6. Check for trigger overlap after changes
+7. Update reference agent copy if it exists
+
+## Common Mistakes
+
+- **Vague descriptions** — "Use for project management" vs "Use when creating GitHub issues or tracking milestones"
+- **Trigger overlap** — Using "review" when `soleri-deep-review` already owns it
+- **Hardcoded agent names** — `ernesto_core` instead of `YOUR_AGENT_core`
+- **Missing engine wiring** — A skill that never checks the vault is a missed opportunity
+- **Second person** — "You should search" instead of "Search the vault"
+- **Too long** — Over 3,000 words bloats context. Extract details into separate files if needed
+- **No prefix** — Forgetting the `soleri-` prefix on the folder and name
+
+## Agent Tools Reference
+
+| Op                   | When to Use                            |
+| -------------------- | -------------------------------------- |
+| `search_intelligent` | Check for existing skills and patterns |
+| `capture_knowledge`  | Capture skill creation decision        |
+| `admin_tool_list`    | Verify available ops                   |
+| `vault_domains`      | Check domain categories                |
+| `memory_search`      | Find related past work                 |

package/dist/skills/{code-patrol → soleri-code-patrol}/SKILL.md

@@ -1,6 +1,10 @@
 ---
-name: code-patrol
-description: Use when reviewing code against the project's own captured patterns, anti-patterns, and conventions — not generic lint rules but institutional knowledge.
+name: soleri-code-patrol
+description: >
+  Use when the user says "check against patterns", "pattern compliance",
+  "convention check", "review against vault", or "institutional review".
+  Reviews code against the project's own captured patterns and conventions.
+  For general code quality review (smells, architecture), use deep-review instead.
 ---
 
 # Code Patrol — Review Code Against Your Own Knowledge

package/{src/skills/context-resume → dist/skills/soleri-context-resume}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: context-resume
+name: soleri-context-resume
 description: >
-  Use when the user says "where did I leave off", "what was I working on", "catch me up",
-  "resume", "continue where we stopped", or is starting a new session and needs to reconstruct
-  working context from memory, plans, and sessions.
+  Use when the user says "where did I leave off", "what was I working on",
+  "catch me up", "resume session", or "continue where we stopped".
+  Reconstructs working context from memory, plans, and sessions.
 ---
 
 # Context Resume — Pick Up Where You Left Off

package/{src/skills/deep-review → dist/skills/soleri-deep-review}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: deep-review
+name: soleri-deep-review
 description: >
-  Use for in-depth code review beyond linting — architecture fitness, code smells, solution quality,
-  optimization opportunities. Triggers on "deep review", "review this code", "is this well architected",
-  "code smells", "review this module", "architecture review", "is this the right approach",
-  "optimization review". Works on any codebase. For vault-specific knowledge quality, use vault-smells instead.
+  Use when the user says "deep review", "code smells", "architecture review",
+  "is this well architected", or "optimization review". Multi-pass code review
+  analyzing structural health, smells, and solution quality. For reviewing
+  against the project's own vault patterns and conventions, use code-patrol instead.
 ---
 
 # Deep Review — Architecture, Smells & Solution Quality

package/dist/skills/{deliver-and-ship → soleri-deliver-and-ship}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: deliver-and-ship
+name: soleri-deliver-and-ship
 description: >
-  Use when the user says "ship it", "ready to deploy", "package", "release",
-  "pre-PR check", "delivery checklist", "is this ready", "final review", or mentions
-  shipping, deploying, packaging, or releasing work. Runs pre-delivery quality gates
-  to ensure nothing ships without passing stability, knowledge capture, and code quality checks.
+  Use when the user says "ship it", "pre-PR check", "delivery checklist", "is this ready",
+  "final review", or "ready to deploy". Runs pre-delivery quality gates
+  to ensure nothing ships without passing stability and code quality checks.
+  For mid-workflow verification (not shipping), use verification-before-completion instead.
 ---
 
 # Deliver & Ship — Quality Gate Runner

package/{src/skills/discovery-phase → dist/skills/soleri-discovery-phase}/SKILL.md

@@ -1,10 +1,9 @@
 ---
-name: discovery-phase
+name: soleri-discovery-phase
 description: >
-  Use for structured exploration before committing to a plan — "I don't know where to start",
-  "what are our options", "investigate", "research this", "explore options", "discovery". Ideal
-  when requirements are unclear, entering a new domain, or facing architectural decisions. Produces
-  a discovery document with options, tradeoffs, and a recommendation.
+  Use when the user says "I don't know where to start", "investigate",
+  "research this", "explore the problem", or "discovery". Structured exploration
+  before committing to a plan, producing options with tradeoffs.
 ---
 
 # Discovery Phase
@@ -19,12 +18,13 @@ Do NOT create a plan, write code, or take any implementation action until the di
 
 1. **Define the question** — restate what we're exploring as one specific, answerable sentence
 2. **Search vault for prior art** — `YOUR_AGENT_core op:search_intelligent params: { query: "<question>", mode: "scan" }`. Also `op:memory_search` with `crossProject: true`.
-3. **Explore codebase** — read relevant files, configs, architecture, recent commits
-4. **Identify constraints** — hard (must-haves) vs soft (nice-to-haves), unknowns that block a decision
-5. **Draft 2-4 options** — each with pros, cons, risk, and effort (S/M/L)
-6. **Recommend** — pick one, state the primary reason, note what would change the answer
-7. **Capture to vault** — persist the discovery finding
-8. **Transition** — hand off to brainstorming or writing-plans skill
+3. **Get brain recommendations** — `YOUR_AGENT_core op:brain_recommend params: { query: "<discovery topic>" }`. Get brain recommendations for similar past explorations.
+4. **Explore codebase** — read relevant files, configs, architecture, recent commits
+5. **Identify constraints** — hard (must-haves) vs soft (nice-to-haves), unknowns that block a decision
+6. **Draft 2-4 options** — each with pros, cons, risk, and effort (S/M/L)
+7. **Recommend** — pick one, state the primary reason, note what would change the answer
+8. **Capture to vault** — persist the discovery finding
+9. **Transition** — hand off to brainstorming or writing-plans skill
 
 ## Option Format
 
@@ -61,9 +61,10 @@ Save to `docs/discoveries/YYYY-MM-DD-<topic>.md` and commit. Then transition to
 
 ## Quick Reference
 
-| Op                   | When to Use                        |
-| -------------------- | ---------------------------------- |
-| `search_intelligent` | Search vault for prior art         |
-| `memory_search`      | Check session history and projects |
-| `capture_knowledge`  | Persist discovery finding          |
-| `route_intent`       | Classify what comes after          |
+| Op                   | When to Use                                         |
+| -------------------- | --------------------------------------------------- |
+| `search_intelligent` | Search vault for prior art                          |
+| `memory_search`      | Check session history and projects                  |
+| `brain_recommend`    | Brain recommendations for similar past explorations |
+| `capture_knowledge`  | Persist discovery finding                           |
+| `route_intent`       | Classify what comes after                           |

package/dist/skills/soleri-dream/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: soleri-dream
+description: >
+  Use when the user says "dream", "consolidate memory", "clean up memory",
+  "memory cleanup", or "dream status". Runs automatic memory consolidation
+  — dedup, archive stale entries, resolve contradictions.
+---
+
+# /dream — Automatic Memory Consolidation
+
+Runs a full "dream" pass over the vault: dedup, archive stale entries, resolve
+contradictions, and produce a summary report. Inspired by how REM sleep
+consolidates biological memory.
+
+**Announce at start:** "Running a dream pass — consolidating vault memory."
+
+## Quick Commands
+
+| Command         | What it does                                              |
+| --------------- | --------------------------------------------------------- |
+| `/dream`        | Run a full dream pass (forces, bypasses gate)             |
+| `/dream status` | Show dream state: last dream, sessions since, eligibility |
+
+## Orchestration
+
+### Step 1: Check Dream Status
+
+```
+YOUR_AGENT_dream op:dream_status
+```
+
+Report current state to user as a table:
+
+| Field                         | Value                    |
+| ----------------------------- | ------------------------ |
+| **Sessions since last dream** | {sessionsSinceLastDream} |
+| **Last dream**                | {lastDreamAt or "Never"} |
+| **Total dreams**              | {totalDreams}            |
+| **Gate eligible**             | {gateEligible}           |
+
+### Step 2: Run Dream
+
+If user explicitly asked to dream (manual `/dream`), force it:
+
+```
+YOUR_AGENT_dream op:dream_run
+  params: { force: true }
+```
+
+If auto-triggered (session start), respect the gate:
+
+```
+YOUR_AGENT_dream op:dream_run
+  params: { force: false }
+```
+
+If the response contains `skipped: true`, inform the user:
+"Dream skipped — {reason}. Use `/dream` to force a run."
+
+### Step 3: Present Dream Report
+
+Format the dream report as a table:
+
+| Metric                     | Value                 |
+| -------------------------- | --------------------- |
+| **Duration**               | {durationMs}ms        |
+| **Duplicates found**       | {duplicatesFound}     |
+| **Stale entries archived** | {staleArchived}       |
+| **Contradictions found**   | {contradictionsFound} |
+| **Total dreams**           | {totalDreams}         |
+| **Timestamp**              | {timestamp}           |
+
+### Step 4: Rebuild Brain Intelligence
+
+```
+YOUR_AGENT_core op:brain_build_intelligence
+```
+
+Rebuild brain intelligence with the freshly consolidated vault data.
+
+### Step 5: Capture to Memory
+
+```
+YOUR_AGENT_memory op:session_capture
+  params: {
+    summary: "Dream pass completed: {duplicatesFound} duplicates, {staleArchived} stale archived, {contradictionsFound} contradictions found"
+  }
+```
+
+## Gate Logic
+
+Auto-dream triggers automatically on session start when BOTH conditions are met:
+
+- **5+ sessions** since last dream
+- **24+ hours** since last dream
+
+Manual `/dream` always runs immediately (force=true).
+
+## Background
+
+Inspired by Claude Code's AutoDream feature and the neuroscience of REM sleep.
+During sleep, the brain consolidates short-term memories into long-term storage,
+prunes irrelevant connections, and resolves conflicts. The /dream skill does
+the same for the vault.

package/dist/skills/{env-setup → soleri-env-setup}/SKILL.md

@@ -1,12 +1,9 @@
 ---
-name: env-setup
+name: soleri-env-setup
 description: >
-  Use when a developer needs to set up, fix, or restore a local development environment.
-  Triggers on post-clone setup, project onboarding, first-time running a repo, pulled changes
-  that broke the build, missing or misconfigured dependencies, MODULE_NOT_FOUND or Cannot find
-  module errors, gyp ERR or native module build failures, missing .env files or unknown required
-  environment variables, database setup, Docker compose issues, or connection refused during
-  local dev. Covers Node.js, Python, Rust, Go, Ruby, PHP, and Docker-based projects.
+  Use when the user says "setup environment", "post-clone setup", "broken build",
+  "missing dependencies", or "MODULE_NOT_FOUND". Detects what a project needs,
+  diagnoses what's missing, and produces an actionable setup checklist.
 ---
 
 # Environment Setup
@@ -26,6 +23,16 @@ Scan the project root for configuration files, detect the tech stack and depende
 - Docker/container environment not starting
 - Missing `.env` file or environment variables
 
+## Check Vault for Known Setup Patterns
+
+```
+YOUR_AGENT_core op:search_intelligent
+  params: { query: "<tech stack> setup gotchas" }
+
+YOUR_AGENT_core op:memory_search
+  params: { query: "environment setup <project>" }
+```
+
 ## Detection Phase
 
 Scan the project root and identify:
@@ -149,3 +156,20 @@ If monorepo detected (turbo.json, nx.json, pnpm-workspace.yaml):
 - **Missing runtime version** — subtle bugs from wrong Node/Python version.
 - **Docker not running** — cryptic "connection refused" errors.
 - **Stale dependencies** — after `git pull`, always re-install if lockfile changed.
+
+## Capture Setup Learnings
+
+If any non-obvious steps or workarounds were needed:
+
+```
+YOUR_AGENT_core op:capture_knowledge
+  params: { title: "<gotcha>", description: "<what happened and the fix>", type: "anti-pattern", tags: ["env-setup", "<tech-stack>"] }
+```
+
+## Agent Tools Reference
+
+| Op                   | When to Use                        |
+| -------------------- | ---------------------------------- |
+| `search_intelligent` | Check vault before starting        |
+| `memory_search`      | Find similar past experiences      |
+| `capture_knowledge`  | Persist patterns worth remembering |

package/dist/skills/{executing-plans → soleri-executing-plans}/SKILL.md

@@ -1,10 +1,9 @@
 ---
-name: executing-plans
+name: soleri-executing-plans
 description: >
-  Use when the user says "execute my plan", "run the plan", "start executing", "implement the
-  plan step by step", or has a written plan to execute sequentially with review checkpoints.
-  Tasks run one at a time in order. If tasks are independent and can run in parallel, use
-  parallel-execute instead.
+  Use when the user says "execute my plan", "run the plan", "start executing",
+  or "implement the plan". Executes tasks sequentially with review checkpoints.
+  For parallel execution, use parallel-execute instead.
 ---
 
 # Executing Plans

package/{src/skills/finishing-a-development-branch → dist/skills/soleri-finishing-a-development-branch}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: finishing-a-development-branch
+name: soleri-finishing-a-development-branch
 description: >
-  Use when the user says "finish branch", "merge branch", "ready to merge", "PR ready",
-  "close branch", "submit PR", or wants to finalize a development branch for merge into
-  the base branch.
+  Use when the user says "finish branch", "ready to merge", "PR ready",
+  "submit PR", or "close branch". Handles pre-merge checks, PR creation,
+  merge strategy, and branch cleanup.
 ---
 
 # Finishing a Development Branch
@@ -12,6 +12,18 @@ Pre-merge checks, PR creation, merge strategy, and branch cleanup.
 
 **Announce at start:** "I'm using the finishing-a-development-branch skill to prepare this branch for merge."
 
+## Vault Context
+
+Search for merge patterns and known conflict areas:
+
+```
+YOUR_AGENT_core op:search_intelligent
+  params: { query: "merge patterns <branch domain>" }
+
+YOUR_AGENT_core op:memory_search
+  params: { query: "merge conflicts" }
+```
+
 ## Step 1: Pre-Merge Checklist
 
 Run all checks before creating a PR. Stop on any failure.
@@ -57,6 +69,15 @@ If the base branch has diverged:
 
 Never force-push a rebased branch that others are working on.
 
+### Capture Merge Learnings
+
+If tricky conflicts were resolved:
+
+```
+YOUR_AGENT_core op:capture_knowledge
+  params: { title: "<conflict pattern>", description: "<resolution strategy>", type: "pattern", tags: ["git", "merge", "conflict-resolution"] }
+```
+
 ## Step 5: Branch Cleanup
 
 After merge is confirmed:
@@ -65,6 +86,8 @@ After merge is confirmed:
 2. `git branch -d <branch>` — delete local branch
 3. If remote branch not auto-deleted: `git push origin --delete <branch>`
 
+**This step is mandatory, not optional.** Stale branches accumulate fast.
+
 ## Anti-Patterns
 
 - **Force-pushing to shared branches** — destroys others' history; only force-push personal branches
@@ -74,3 +97,11 @@ After merge is confirmed:
 - **Leaving stale branches** — delete after merge; stale branches create confusion
 
 **Related skills:** executing-plans, verification-before-completion
+
+## Agent Tools Reference
+
+| Op                   | When to Use                        |
+| -------------------- | ---------------------------------- |
+| `search_intelligent` | Check vault before starting        |
+| `memory_search`      | Find similar past experiences      |
+| `capture_knowledge`  | Persist patterns worth remembering |

package/dist/skills/{fix-and-learn → soleri-fix-and-learn}/SKILL.md

@@ -1,10 +1,9 @@
 ---
-name: fix-and-learn
+name: soleri-fix-and-learn
 description: >
-  Use AFTER a root cause has been identified (typically via systematic-debugging) to execute
-  the fix and capture the learning in the vault. Triggers on "fix it", "apply the fix",
-  "patch this and remember". Do NOT use as the first response to a bug — use
-  systematic-debugging first to find root cause.
+  Use when the user says "fix it", "apply the fix", "patch this and remember",
+  or "fix and capture". Executes a fix AFTER root cause is identified and
+  captures the learning in the vault. Use systematic-debugging first.
 ---
 
 # Fix & Learn — Debug, Repair, Capture

package/{src/skills/health-check → dist/skills/soleri-health-check}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: health-check
+name: soleri-health-check
 description: >
-  Use when the user asks "check health", "system status", "how healthy is the vault",
-  "knowledge quality", "run diagnostics", "vault health report", or wants a read-only health
-  assessment of the knowledge base — scoring, reporting, finding issues. Does NOT modify vault
-  entries. To actively clean, merge, or deduplicate, use vault-curate instead.
+  Use when the user says "system health", "agent health", "run diagnostics",
+  "system status", or "check health". Read-only health assessment of the
+  knowledge base — scoring, reporting, finding issues. For deep quality
+  analysis (contradictions, stale patterns, knowledge debt), use vault-smells instead.
 ---
 
 # Health Check — Knowledge Base Maintenance

package/{src/skills/knowledge-harvest → dist/skills/soleri-knowledge-harvest}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: knowledge-harvest
+name: soleri-knowledge-harvest
 description: >
-  Use to EXTRACT multiple patterns from a source — code, docs, PRs, articles. Triggers on
-  "learn from this", "harvest knowledge", "ingest this document", "extract patterns from".
-  The agent reads the source and identifies what to capture. For saving a single known item,
-  use vault-capture instead.
+  Use when the user says "learn from this", "harvest knowledge", "ingest this",
+  or "extract patterns from". Extracts multiple patterns from a source like
+  code, docs, PRs, or articles into the vault. For saving a single known
+  pattern, use vault-capture instead.
 ---
 
 # Knowledge Harvest — Extract Patterns From Anything

package/dist/skills/{mcp-doctor → soleri-mcp-doctor}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: mcp-doctor
+name: soleri-mcp-doctor
 description: >
-  Use when MCP servers fail to connect, tools are missing, or the user says "check MCP",
-  "MCP not working", "server not connecting", "tools missing", "heal MCP", "fix MCP",
-  "mcp doctor", "mcp status". Diagnoses and repairs MCP server connectivity issues.
+  Use when the user says "MCP not working", "tools missing", "fix MCP",
+  "mcp doctor", or "server not connecting". Diagnoses and repairs MCP server
+  connectivity issues.
 ---
 
 # MCP Doctor — Diagnose and Heal MCP Connections