agentic/code/addons/aiwg-utils/skills/steward/SKILL.md
Provide provider capability awareness and route commands by answering what the current provider supports natively vs must emulate
npx skillsauth add jmagly/aiwg stewardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
| 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 |
When triggered:
Identify the subcommand:
capabilities — show what a provider supports, optionally filtered by featurefind — show which providers support a capability and how to invoke itDetect provider context (for capabilities without --provider):
CLAUDE_CODE_VERSION env → claude-codeCODEX_API_KEY env → codex.cursor/ project directory → cursoraiwg runtime-info for authoritative detectionRun the appropriate command:
# 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
Interpret and surface routing advice:
aiwg command that emulates the featureSteward 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.
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) |
User: "What does my provider support?"
Extraction: Capabilities request, no provider specified — auto-detect
Action:
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)."
User: "Does my provider support agent teams natively?"
Extraction: Feature check — agent_teams on current provider
Action:
aiwg steward capabilities --feature agent_teams
Response: "agent_teams on claude-code: Native (uses Claude Code's built-in Task tool). No emulation needed."
User: "Which providers support cron natively?"
Extraction: find subcommand for cron capability
Action:
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
User: "Show me the capability matrix for all providers"
Extraction: capabilities --all
Action:
aiwg steward capabilities --all
Response: Formatted table of all 9 providers x all 6 features, with native/emulated/unsupported indicators.
If the user's intent is ambiguous:
data-ai
Report which research-corpus radar sidecars are overdue for refresh. Computes staleness (days since last refresh vs the cadence window) for every radar, sorted most-overdue-first. Runs via `aiwg corpus radar-status`.
data-ai
Aggregate research-corpus radar sidecars into a corpus or per-cluster freshness report — totals, overdue count, per-cluster / per-GRADE / per-trajectory breakdowns, an overdue table, and per-radar rationale snippets. Runs via `aiwg corpus radar-report`.
testing
Scaffold radar/freshness sidecars for research-corpus REFs. Pulls title/authors from the citation sidecar and GRADE from the analysis doc, defaults the refresh cadence from GRADE and the cluster from a corpus-local map, and stamps documentation/radar/REF-XXX-radar.md. Runs via `aiwg corpus radar-init`.
data-ai
Compute an entity's publication trajectory — per-year paper counts, topic drift, hot-streak detection (≥3 consecutive A-grade years), and career phase. Runs via `aiwg corpus profile-temporal`.