Automated summary
Interact with Willy AI agents on Willform Agent: check status, send prompts, invoke tools, and recover crashed agents.
Strengths
- Comprehensive agent management (status, chat, recovery) through a unified interface.
- Automatic namespace selection when only one exists, simplifying usage.
- Operates via the MCP API for fine-grained agent interaction.
- Handles common API errors with helpful user suggestions.
Limitations
- Requires prior setup via /wf-setup and creation of a namespace.
- Chat is only possible when the agent is in 'running' state.
- Agent recovery has a 5-minute cooldown and only works for specific failure states.
Use this skill to monitor, converse with, or restart your Willy agents within a given namespace.
Do not use if you have not yet configured your Willform account or created a namespace.
Security analysis
SafeThe 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.
No concerns found
How this analysis is madeExamples
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/willy-agent-interaction-mmk3nicr/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/willy-agent-interaction-mmk3nicr' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/willy-agent-interaction-mmk3nicr/download' --output '.skill-downloads/willy-agent-interaction-mmk3nicr/SKILL.md.part' && mv '.skill-downloads/willy-agent-interaction-mmk3nicr/SKILL.md.part' '.skill-downloads/willy-agent-interaction-mmk3nicr/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash, Read, AskUserQuestion
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/willy-agent-interaction-mmk3nicr/SKILL.md' && test -s '.skill-downloads/willy-agent-interaction-mmk3nicr/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/wf-agent' && cp -R '.skill-downloads/willy-agent-interaction-mmk3nicr' '.claude/skills/wf-agent'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/willy-agent-interaction-mmk3nicr'openskills read 'willy-agent-interaction-mmk3nicr'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/willy-agent-interaction-mmk3nicr/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.