runtime-info
Display a comprehensive runtime environment report covering detected provider, available tools, AIWG version, and installed frameworks
What this skill does
# Runtime Info You display a comprehensive runtime environment report — detected provider, available tools and permissions, AIWG version, installed frameworks, and relevant environment variables. Used by the Steward and orchestrators to determine provider routing and capability availability. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "what provider am I on" → runtime-info (provider section) - "do I have bash access" → runtime-info (tools section) - "what version of aiwg is this" → runtime-info (version section) - "what's installed" → runtime-info (frameworks section) - "check my environment" → runtime-info ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Full report | "show runtime info" | Run `aiwg runtime-info` | | Provider check | "which provider is active?" | Run `aiwg runtime-info` → provider field | | Tool availability | "what tools are available?" | Run `aiwg runtime-info` → tools field | | Version check | "what version of AIWG is running?" | Run `aiwg runtime-info` → version field | | Framework check | "which frameworks are installed?" | Run `aiwg runtime-info` → frameworks field | | Environment dump | "show environment variables" | Run `aiwg runtime-info` → env field | ## Behavior When triggered: 1. **Identify what the user wants**: - Full report, or a specific field (provider, tools, version, frameworks, env)? - Is this for routing decisions (Steward context) or user curiosity? 2. **Run the command**: ```bash # Full runtime report aiwg runtime-info # Machine-readable (for orchestration / Steward routing) aiwg runtime-info --json ``` 3. **Extract and present** the relevant section if the user asked about a specific aspect; present the full report otherwise. ## Report Fields The runtime-info report covers: | Field | Description | |-------|-------------| | `provider` | Detected AI platform (claude-code, copilot, cursor, etc.) | | `aiwg_version` | Installed AIWG version (CalVer) | | `node_version` | Node.js runtime version | | `tools` | Available tool permissions (Read, Write, Bash, Glob, Grep, etc.) | | `frameworks` | Installed AIWG frameworks and their versions | | `env` | AIWG-relevant environment variables (AIWG_ROOT, AIWG_CONTEXT_WINDOW, etc.) | | `platform` | OS and architecture | | `cwd` | Current working directory | ## Examples ### Example 1: Full report **User**: "Show runtime info" **Extraction**: Full report, no specific field **Action**: ```bash aiwg runtime-info ``` **Response**: ``` Provider: claude-code AIWG version: 2026.3.15 Node: v22.11.0 Platform: linux/x64 CWD: /mnt/dev-inbox/jmagly/aiwg Tools available: Read, Write, Edit, Bash, Glob, Grep Frameworks installed: sdlc-complete 2026.3.15 aiwg-utils 2026.3.15 Environment: AIWG_ROOT=/mnt/dev-inbox/jmagly/aiwg AIWG_CONTEXT_WINDOW=200000 ``` ### Example 2: Provider routing (Steward context) **User (Steward)**: "Which provider is active so I can route this deployment?" **Extraction**: Provider field only **Action**: ```bash aiwg runtime-info --json ``` **Response**: "Active provider is `claude-code`. Use `aiwg use sdlc --provider claude-code` for deployment." ### Example 3: Tool availability check **User**: "Do I have Bash access in this environment?" **Extraction**: Tools field **Action**: ```bash aiwg runtime-info --json ``` **Response**: "Yes — Bash is listed in available tools. You also have Read, Write, Edit, Glob, and Grep." ### Example 4: Framework inventory **User**: "What frameworks are installed?" **Extraction**: Frameworks field **Action**: ```bash aiwg runtime-info ``` **Response**: "2 frameworks installed: sdlc-complete (2026.3.15), aiwg-utils (2026.3.15). Run `aiwg list` for full framework details." ## Clarification Prompts If the user's intent is ambiguous: - "Are you checking the environment for a specific purpose (e.g., provider routing, tool availability), or would a full report be useful?" ## References - @$AIWG_ROOT/src/cli/handlers/runtime-info.ts — Runtime info handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference (runtime-info section) - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/agent-deployment.md — Provider routing context
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.