Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 38 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Write the Python code to initialize your AutoGen agents (e.g., UserProxyAgent, AssistantAgent with Claude Opus 4.1). Implement two custom AutoGen tools: one for fetching simulated CRE market data (e.g., `get_market_data(location, property_type)`) and another for performing basic financial calculations (e.g., `calculate_roi(cost, revenue)`). Ensure Claude Opus 4.1 is properly configured for the AssistantAgent and that tools are callable within the agent's context.
```python
import autogen
# Configure Claude Opus 4.1
config_list_claude = [
{
"model": "claude-3-opus-20240229", # or equivalent API name for Claude Opus 4.1 via Azure/Anthropic
"api_key": "YOUR_CLAUDE_API_KEY"
}
]
# Define custom tools
def get_market_data(location: str, property_type: str) -> str:
# Simulate API call
if location == "Austin, TX" and property_type == "retail":
return "Simulated Austin retail data: avg_yield=0.05, growth_potential=0.03"
return "No data found for specified parameters."
def calculate_roi(cost: float, revenue: float) -> float:
return (revenue - cost) / cost
# Create agents
# analyst_agent = autogen.AssistantAgent(
# name="Analyst",
# llm_config={"config_list": config_list_claude},
# system_message="You are a commercial real estate analyst. Use tools to gather data and perform calculations."
# )
# user_proxy = autogen.UserProxyAgent(
# name="User_Proxy",
# human_input_mode="NEVER",
# max_consecutive_auto_reply=10,
# is_termination_msg=lambda x: "FINISH" in x.get("content", ""),
# code_execution_config={"work_dir": "coding", "use_docker": False},
# tool_code_extraction_config={"tool_code_block_tag": "tool_code"}
# )
# user_proxy.register_for_execution(get_market_data)
# user_proxy.register_for_llm(get_market_data)
# user_proxy.register_for_execution(calculate_roi)
# user_proxy.register_for_llm(calculate_roi)
# (Initialize GroupChat and run conversation)
```Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Hold the task contract and output shape stable so generated implementations remain comparable.
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt already mixes executable detail with instructions, so the safest path is to tune examples and interfaces before you rewrite the overall scaffold.
Multi-Agent System for Commercial Real Estate Analysis
Develop a sophisticated multi-agent system using AutoGen to act as an expert commercial real estate (CRE) analyst for institutional investors. The system will comprise specialized agents (e.g., a 'Data Fetcher', an 'Economic Analyst', a 'Valuation Specialist', a 'Report Generator') that collaborate autonomously to research, analyze, and synthesize insights on CRE investment opportunities. This challenge emphasizes complex agent-to-agent communication, tool orchestration, and the generation of comprehensive, data-driven reports. The agents should be able to query external (simulated) CRE data APIs, perform financial modeling, and provide reasoned investment recommendations. Focus on designing robust communication protocols between agents to resolve conflicts and refine analyses. The solution must also incorporate an observability framework to trace the multi-agent deliberation process and provide a user-friendly interface for querying the system and visualizing its output.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.