By name: api-index description: >- Intent router for F5 XC REST API operations. When the user's request involves the platform API but does not clearly match a specific skill trigger, this skill determines the correct skill to invoke. API operations delegate to the api-operator subagent; configuration analysis delegates to the config-analyzer subagent. Both keep large JSON payloads out of the main session. user-invocable: false
API Index — Intent Router
Routes API-related requests to the correct skill and ensures
all API operations are delegated to the api-operator
subagent.
Critical: Subagent Delegation
Never run large curl/API sequences in the main session.
API JSON responses can be verbose. All API operations must
be delegated to the api-operator agent:
Agent(
subagent_type="platform:api-operator",
description="<short task description>",
prompt="<task details with env var references>"
)
The agent reads the skill reference files itself and executes autonomously. The main session only receives the result.
Routing Table
| User Intent | Target Skill |
|---|---|
| "check token", "validate token" | api-auth |
| "list namespaces" | api-auth (uses namespace list for validation) |
| "list", "get", "create", "update", "delete" + resource | api-operations |
| "deploy", "set up", "provision" + resource | api-operations (workflow mode) |
| "cURL", "API call" + custom request | Direct delegation to api-operator |
| User provides JSON config + asks question about it | config-analysis |
| "analyze", "review", "audit", "explain", "inspect" + config/JSON | config-analysis |
| "is [feature] enabled/disabled", "what mode", "security posture" | config-analysis |
| "how to change/enable/disable/add/remove" + config context | config-analysis |
| "what does this config do", "show me the settings" | config-analysis |
How to Route
- Parse the user's request for intent keywords
- Match against the routing table
- Distinguish CRUD from analysis: If the user's message
contains a JSON configuration blob (or references one shared
earlier) AND the intent is interrogative (asking about the
config rather than requesting a platform operation), route to
config-analysis. CRUD requests target the platform ("create this LB", "delete that pool"). Analysis requests target a provided config ("is WAF enabled on this?", "explain this config", "what violations are disabled?"). - Spawn the appropriate agent with the matched task
- Relay the agent's result to the user
Available Skills (read by the agent)
- api-auth — API token validation and certificate auth
- api-operations — Spec-aware CRUD for 98 resource types across 38 domains, with endpoint paths, payload templates, dependency ordering, and multi-step workflow compositions
- config-analysis — Configuration analysis and advisory Q&A. Analyzes customer JSON configurations against the same resource profiles as api-operations. Answers questions about security posture, feature enablement, mode settings, and best practices.
Future Skills (not yet implemented)
api-bulk— Batch operations across namespacesapi-export— Export configuration as JSON/YAML