chain-tools-to-find-user-details

star 0

Use when a user cannot provide a primary identifier (like an email or user ID) but offers alternative information (like name and zip code). This skill involves using a sequence of tools to resolve the user's identity and retrieve their full details.

wan19990901 By wan19990901 schedule Updated 2/24/2026

name: chain-tools-to-find-user-details description: Use when a user cannot provide a primary identifier (like an email or user ID) but offers alternative information (like name and zip code). This skill involves using a sequence of tools to resolve the user's identity and retrieve their full details. metadata: case_id: 2 case_outcome: failed source: /data/Research_dir/Benchmarks/tau2-bench/data/simulations/gemini_3_flash_retail_reasoning_bank/pattern_guidance_failed.json generated_at: 2026-02-20T20:44:14.639847

Layer 1: Metadata & Description

  • Description: Use when a user cannot provide a primary identifier (like an email or user ID) but offers alternative information (like name and zip code). This skill involves using a sequence of tools to resolve the user's identity and retrieve their full details.

Layer 2: Guidelines

General Guidelines

  • When a primary piece of information is missing, look for alternative data points provided by the user.
  • Identify tools that can use the alternative data to find a primary identifier (e.g., name/zip to find user_id).
  • Use the output of one tool as the input for another to bridge information gaps.
  • Do not ask the user for information you can derive yourself by chaining tools.
  • Use the fully retrieved profile to complete the original task.

Specific Guidelines

  • Recognize that the user cannot provide their email address but has offered their name and zip code.
  • Call the find_user_id_by_name_zip tool with the provided name and zip code.
  • Extract the user_id from the tool's response.
  • Call the get_user_details tool using the retrieved user_id.
  • Utilize the complete user profile from the second tool call (e.g., email, payment methods) to proceed with the transaction.

Layer 3: Context

  • Problem Pattern: Essential user details (e.g., email, payment method) required for transaction processing are missing from initial user input.
  • State Signature: User's statement in Turn 3: "My name is Yusuf Rossi and my zip code is 19122. To be honest, I can't quite remember which email address I used for this account."
  • Bypass Strategy:
    1. Obtain basic identifying information (e.g., name, zip code) from the user.
    2. Use the find_user_id_by_name_zip tool to retrieve the user_id.
    3. Use the get_user_details tool with the obtained user_id to fetch the complete user profile, including email and registered payment methods.
    4. Utilize the retrieved payment method for transaction processing (e.g., specifying the refund destination).

Layer 3: Context (Additional)

  • Case ID: 12
  • Case Outcome: failed
  • Problem Pattern: User wants to exchange an item but cannot provide the specific order ID for that item.
  • State Signature: Yeah, I'm not sure about the order ID. I have a skateboard I want to exchange. It's just a bit too long for me. I'm looking to swap it for a shorter one, made of bamboo.
  • Bypass Strategy:
    1. Retrieve details for all user's orders.
    2. Identify the item within the retrieved orders based on user's description.
Install via CLI
npx skills add https://github.com/wan19990901/adk_agentskill --skill chain-tools-to-find-user-details
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator