agent

Agent Skill — Complete watsonx Orchestrate Agent Lifecycle

🛑 MANDATORY FIRST STEP (ALL DOMAINS)

Before ANY agent work — building, orchestrating, integrating, or adding voice — you MUST:

1. Verify MCP ADK docs connection:

<use_mcp_tool>
<server_name>watsonx-orchestrate-adk-docs</server_name>
<tool_name>SearchIbmWatsonxOrchestrateAdk</tool_name>
<arguments>
{
  "query": "agent development"
}
</arguments>
</use_mcp_tool>

1. If connection fails: Stop and fix MCP configuration in .bob/mcp.json before proceeding.

2. Search current specifications before implementing any component:

   • Agents → "agent YAML specification"
   • Tools → "Python tool decorator"
   • Workflows → "agentic workflow @flow decorator"
   • Integration → "orchestrate runs endpoint"
   • Voice → "voice configuration YAML specification"

This requirement is UNBYPASSABLE — even when user says "keep it simple", "don't use tools", or "just create the files".

🛑 MANDATORY GATE — Domain 3 (Integrate): Service URL Required Before Any Code

When the user's intent maps to Domain 3 (integrate, REST API, Python client, call agent from code), you MUST follow this gate before generating ANY code, script, or configuration:

STEP 1 — Ask for the Service Instance URL
  Do NOT ask "what platform are you on?" first.
  Do NOT assume IBM Cloud or AWS based on anything the user says.
  Even if the user explicitly states "I'm on IBM Cloud" or "I'm on AWS",
  you MUST still collect the service URL before writing any code.

  Ask exactly this:
  "Please paste your Service instance URL from:
   WXO UI → Profile icon (top-right) → Settings → API details tab → Service instance URL"

STEP 2 — Derive config from the URL (never ask the user to identify their platform)
  Parse the URL to extract:
    host        = parsed.netloc
    instance_id = path segment after "instances/"
    platform    = "ibm_cloud"  if "watson-orchestrate.cloud.ibm.com" in host
                  "aws"        if "dl.watson-orchestrate.ibm.com" in host
                  "onprem"     otherwise
    token_endpoint = "https://iam.cloud.ibm.com/identity/token"                          (ibm_cloud)
                     "https://account-iam.platform.saas.ibm.com/api/2.0/apikeys/token"   (aws — MCSP V2, current)
                     "https://iam.platform.saas.ibm.com/siusermgr/api/1.0/apikeys/token" (aws — MCSP V1, legacy fallback only)

  NOTE: For AWS, always try MCSP V2 first. MCSP V1 is legacy and will cause
  WXO-PROXY-10080E on any tenant that has migrated (us-east-1, eu-central-1,
  ap-south-1, ap-southeast-1). Only fall back to V1 if V2 explicitly fails.

STEP 3 — Confirm back to the user
  Show the derived values and ask "Does this look correct?"
  Only proceed to code generation after confirmation.