aiwg-doctor
Run a comprehensive health check on the AIWG installation and workspace with pass/fail diagnostics and remediation steps
What this skill does
# AIWG Doctor You run a comprehensive health check on the AIWG installation and workspace, reporting pass/fail for each diagnostic with remediation steps for any failures. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "is aiwg healthy" → run `aiwg doctor` - "something is broken" → run `aiwg doctor` to isolate the issue - "aiwg isn't working" → run `aiwg doctor` - "check my aiwg setup" → run `aiwg doctor` - "run diagnostics" → run `aiwg doctor` - "aiwg broken" → run `aiwg doctor` ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Health check | "check health" / "is aiwg healthy" | Run `aiwg doctor` | | Diagnostic request | "diagnose" / "run diagnostics" | Run `aiwg doctor` | | Broken install | "aiwg isn't working" | Run `aiwg doctor` | | Setup validation | "check my aiwg setup" | Run `aiwg doctor` | | Troubleshooting | "troubleshoot installation" | Run `aiwg doctor` | | Verbose check | "run full diagnostics" | Run `aiwg doctor --verbose` | ## Behavior When triggered: 1. **Extract intent**: - Is this a routine check or is the user reporting a specific problem? - Did the user mention a symptom (e.g. "commands not found", "frameworks missing")? If so, note it to help interpret the doctor output. - Does the user want verbose output? 2. **Run the appropriate command**: ```bash # Standard health check aiwg doctor # Verbose output (additional detail per check) aiwg doctor --verbose ``` The doctor command (`tools/cli/doctor.mjs`) validates: - npm package is installed and executable - `.aiwg/frameworks/registry.json` exists and is valid JSON - Framework files are deployed to the active platform directories (e.g. `.claude/agents/`, `.claude/commands/`) - Node.js version meets minimum requirements - Required tools are available (`git`, `node`, `npm`) - Channel configuration is consistent 3. **Report the result** — present a summary of checks passed and failed. For each failure, include the remediation step from the doctor output. Common remediations: - Missing registry: run `aiwg use sdlc` (or the appropriate framework) - Stale deployment: run `aiwg sync` or `aiwg update` - Missing Node.js: direct user to https://nodejs.org - CLI not found: run `npm install -g aiwg` ## Examples ### Example 1: Routine health check **User**: "Check AIWG health" **Extraction**: Routine health check, no specific symptom **Action**: ```bash aiwg doctor ``` **Response**: "All checks passed. npm package v2026.3.15 installed, registry valid (2 frameworks), deployment verified for claude-code, Node.js v20.11.0 compatible." ### Example 2: Broken install investigation **User**: "AIWG commands aren't showing up in Claude" **Extraction**: User reports missing commands — deployment check is the likely culprit **Action**: ```bash aiwg doctor ``` **Response**: "Doctor found 1 issue: framework files are not deployed to `.claude/commands/`. Run `aiwg sync` to redeploy, then restart your Claude session." ### Example 3: Post-install validation **User**: "I just installed AIWG — is everything set up correctly?" **Extraction**: New install, full validation requested **Action**: ```bash aiwg doctor ``` **Response**: "Installation looks good. One note: no frameworks are deployed yet. Run `aiwg use sdlc` to deploy the SDLC framework, or `aiwg use all` to deploy everything." ### Example 4: Verbose diagnostics **User**: "Run full diagnostics on AIWG" **Extraction**: Verbose check requested **Action**: ```bash aiwg doctor --verbose ``` **Response**: "Verbose diagnostics complete. [Output summary with per-check detail, paths, and versions.]" ## Clarification Prompts If the user mentions a specific symptom before triggering doctor: - "I'll run `aiwg doctor` to check your installation. Can you describe what you were trying to do when it broke?" ## References - @$AIWG_ROOT/src/cli/handlers/utilities.ts — Doctor command handler (doctorHandler) - @$AIWG_ROOT/tools/cli/doctor.mjs — Health check implementation - @$AIWG_ROOT/docs/cli-reference.md — CLI reference
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.