Notre avis
Permet d'interagir avec les agents Willy sur Willform Agent : vérifier leur statut, envoyer des prompts, invoquer des outils et récupérer des agents plantés.
Points forts
- Gestion complète des agents (statut, chat, récupération) via une interface unifiée.
- Sélection automatique du namespace lorsqu'il est unique, ce qui simplifie l'utilisation.
- Fonctionne via l'API MCP pour une intégration fine avec les agents.
- Gère les erreurs API courantes avec des suggestions utiles pour l'utilisateur.
Limites
- Nécessite une configuration préalable via /wf-setup et la création d'un namespace.
- Le chat n'est possible que si l'agent est en état 'running'.
- La récupération d'agent a un temps de recharge de 5 minutes et ne fonctionne que pour certains états d'échec.
Utilisez cette compétence pour surveiller, dialoguer ou relancer vos agents Willy dans un namespace donné.
Ne l'utilisez pas si vous n'avez pas encore configuré votre compte Willform ou créé un namespace.
Analyse de sécurité
SûrThe skill uses only allowed tools (Bash, Read, AskUserQuestion) for API interactions via pre-defined scripts. It does not execute destructive commands, exfiltrate data, or bypass safety mechanisms. User prompts are properly escaped before being passed to the API. No security risks identified.
Aucun point d'attention détecté
Exemples
Check the status of my Willy agent in the current namespace.Chat with my Willy agent: tell me a joke.My Willy agent crashed. Please recover it.name: wf-agent description: Interact with Willy AI agents on Willform Agent allowed-tools: Bash, Read, AskUserQuestion user-invocable: true
/wf-agent -- Willy Agent Interaction
Goal
Check Willy agent status, send prompts, invoke tools, and recover crashed agents on Willform Agent.
Language
After loading config, check WF_LANGUAGE (set by wf_load_config). Use English if en or empty, Korean if ko. If not set, ask the user to choose (English/한국어) and save to config.
Instructions
Step 1: Load API config
source "${CLAUDE_PLUGIN_ROOT}/scripts/wf-api.sh" && wf_load_config
If this fails, tell the user to run /wf-setup first and stop.
Step 2: Resolve namespace
Agent operations require a namespaceId. List namespaces and resolve:
ns_response=$(wf_get "/api/namespaces")
- If only one namespace exists, use it automatically
- If multiple exist, ask the user to select one via AskUserQuestion
- If none exist, tell the user to create one first (
/wf-namespace)
Extract the id field from the selected namespace.
Step 3: Determine action
If an argument is provided ($ARGUMENTS):
statusor no argument → show agent statuschat <prompt>→ send a prompt to the agentrecover→ attempt to recover a crashed agent
Otherwise, use AskUserQuestion:
- Agent status — Check if Willy agent is running and healthy
- Chat with agent — Send a prompt to Willy
- Recover agent — Restart a crashed or unresponsive agent
Step 4: Execute action
All agent operations use wf_mcp (MCP JSON-RPC via /api/mcp, no REST equivalent):
Agent status
response=$(wf_mcp "agent_status" "{\"namespaceId\":\"${NAMESPACE_ID}\"}")
The response is a JSON string. Parse and display: status, systemNamespace, cpuCores, memoryGb, lastHealthCheck, errorMessage.
Chat with agent
Ask for the prompt (or use remaining arguments):
ESCAPED_MSG=$(echo "$PROMPT" | jq -Rs '.')
response=$(wf_mcp "agent_chat" "{\"namespaceId\":\"${NAMESPACE_ID}\",\"message\":${ESCAPED_MSG}}")
Display the agent's response text.
Note: Chat requires the agent to be in running state. If the API returns an error about agent not running, suggest recovery or checking status first.
Recover agent
response=$(wf_mcp "agent_recover" "{\"namespaceId\":\"${NAMESPACE_ID}\"}")
Recovery only works when agent status is failed, interrupted, or degraded. There is a 5-minute cooldown between recovery attempts.
After triggering recovery, poll agent status (max 60s) until it reaches running.
Step 5: Report result
Show the action result. For chat, display the agent's response. For status/recover, show current state.
Agent Status Reference:
| Status | Meaning | |--------|---------| | running | Agent is healthy and accepting requests | | starting | Agent is booting up | | failed | Agent crashed, needs recovery | | interrupted | Agent was interrupted, needs recovery | | degraded | Agent partially functional, recovery recommended | | not_provisioned | No agent exists for this namespace |
Error Handling
- If API returns 401, suggest
/wf-setup - If MCP response contains
error, display the error message - If agent status is
not_provisioned, note that the Willy agent has not been created for this namespace yet - If recovery returns 409 (cooldown), tell the user to wait and try again later
- If chat returns 409 (not running), suggest checking status or recovering first
Architecte Docker Compose
DevOps
Concoit des configurations Docker Compose optimisees.
Rapport de Post-Mortem
DevOps
Rédige des rapports post-mortem d'incidents structurés et blameless.
Créateur de Runbooks
DevOps
Crée des runbooks opérationnels clairs pour les procédures DevOps courantes.