steward
Provide provider capability awareness and route commands by answering what the current provider supports natively vs must emulate
What this skill does
# steward
You provide provider capability awareness and intelligent command routing. You read the canonical capability matrix to answer what the current provider supports natively, what must be emulated, and which command achieves a given goal on the active platform.
## Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "what can this provider do" → capabilities for current provider
- "is X supported here" → feature check for current provider
- "how do I do X" (in provider context) → routing advice
- "what command handles Y" → find subcommand
## Trigger Patterns Reference
| Pattern | Example | Action |
|---------|---------|--------|
| Current provider capabilities | "what does my provider support" | `aiwg steward capabilities` |
| Named provider capabilities | "what does Cursor support" | `aiwg steward capabilities --provider cursor` |
| All providers | "show the full capability matrix" | `aiwg steward capabilities --all` |
| Feature check | "does my provider support agent teams" | `aiwg steward capabilities --feature agent_teams` |
| Routing lookup | "which providers support cron" | `aiwg steward find --capability cron` |
## Behavior
When triggered:
1. **Identify the subcommand**:
- `capabilities` — show what a provider supports, optionally filtered by feature
- `find` — show which providers support a capability and how to invoke it
2. **Detect provider context** (for `capabilities` without `--provider`):
- Check `CLAUDE_CODE_VERSION` env → `claude-code`
- Check `CODEX_API_KEY` env → `codex`
- Check `.cursor/` project directory → `cursor`
- Fall back to `aiwg runtime-info` for authoritative detection
3. **Run the appropriate command**:
```bash
# Current provider capabilities (auto-detected)
aiwg steward capabilities
# Named provider
aiwg steward capabilities --provider copilot
# Check specific feature on current provider
aiwg steward capabilities --feature agent_teams
# Full matrix — all providers, all features
aiwg steward capabilities --all
# Find providers that support a capability
aiwg steward find --capability cron
```
4. **Interpret and surface routing advice**:
- Native support: report the native tool or mechanism
- Emulated support: show the `aiwg` command that emulates the feature
- No support: report clearly and suggest the nearest alternative
## Project-Local Authoring Routing
Steward capability routing is intentionally broader than the provider matrix when the user asks how to create AIWG artifacts for their own project. For project-local authoring intents, do not answer only with `aiwg steward capabilities`.
Route these intents directly:
| User intent | Primary route | Notes |
|---|---|---|
| Create a repo/project-level skill | `aiwg new-bundle <name> --starter skill` or `aiwg new-extension <name> --starter skill` | Creates source under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`; deploy with `aiwg use <name>`. |
| Create a project-level agent | `aiwg new-bundle <name> --starter agent` or SkillSmith/AgentSmith when generating from a prompt | Use project-local bundle layout so the artifact is versioned with the repo. |
| Choose extension/addon/framework/plugin shape | `aiwg discover "project-local customization"` and docs/customization quickstart | Extensions are the usual smallest local customization; addons/frameworks are heavier. |
| Make an agent invoke a custom skill | Create the skill in a project-local bundle, run `aiwg use <name>`, then reload the provider session | Session reload rules still apply. |
Canonical docs: `docs/customization/project-local-quickstart.md`, `docs/project-local/overview.md`, and `docs/project-local/manifest-reference.md`. Mention that project-local artifacts are trusted repo code and should be reviewed before deploy.
## Capability Matrix Source
The authoritative source is `agentic/code/providers/capability-matrix.yaml`. Key features tracked:
| Feature | Description |
|---------|-------------|
| `cron` | Scheduled/recurring task execution |
| `agent_teams` | Native multi-agent team orchestration |
| `tasks` | Background task dispatch |
| `mcp` | Model Context Protocol server support |
| `behaviors` | Hook-based behavior scripts |
| `mission_control` | Multi-session orchestration (`aiwg mc`) |
## Examples
### Example 1: Check current provider
**User**: "What does my provider support?"
**Extraction**: Capabilities request, no provider specified — auto-detect
**Action**:
```bash
aiwg steward capabilities
```
**Response**: "You are on **claude-code**. Native support: agent_teams, tasks, mcp, cron. Emulated via aiwg: behaviors (via hooks), mission_control (via `aiwg mc`)."
### Example 2: Feature-specific check
**User**: "Does my provider support agent teams natively?"
**Extraction**: Feature check — `agent_teams` on current provider
**Action**:
```bash
aiwg steward capabilities --feature agent_teams
```
**Response**: "agent_teams on **claude-code**: Native (uses Claude Code's built-in Task tool). No emulation needed."
### Example 3: Cross-provider lookup
**User**: "Which providers support cron natively?"
**Extraction**: `find` subcommand for `cron` capability
**Action**:
```bash
aiwg steward find --capability cron
```
**Response**:
```
cron support across providers:
claude-code: native
codex: emulated via aiwg-scheduler
copilot: emulated via aiwg-scheduler
cursor: emulated via aiwg-scheduler
factory: native
opencode: emulated via aiwg-scheduler
warp: emulated via aiwg-scheduler
windsurf: emulated via aiwg-scheduler
openclaw: emulated via aiwg-scheduler
```
### Example 4: Full matrix
**User**: "Show me the capability matrix for all providers"
**Extraction**: `capabilities --all`
**Action**:
```bash
aiwg steward capabilities --all
```
**Response**: Formatted table of all 9 providers x all 6 features, with native/emulated/unsupported indicators.
## Clarification Prompts
If the user's intent is ambiguous:
- "Are you asking about the provider you're currently using, or a specific provider?"
- "Should I check all features or a specific one?"
## References
- @$AIWG_ROOT/src/cli/handlers/steward.ts — Steward command handler
- @$AIWG_ROOT/agentic/code/providers/capability-matrix.yaml — Authoritative capability matrix
- @$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.