lee everson eversonl

name: dynamic-task-executor description: Use this agent when you need to delegate a specialized task that requires a specific persona, expertise, or approach that you will define on-the-fly. This agent is ideal for: (1) Tasks that require domain-specific expertise not covered by existing agents, (2) Complex workflows where you need to orchestrate multiple specialized sub-tasks with different personas, (3) Situations where you want to experiment with different expert perspectives on the same problem, (4) Tasks that need custom evaluation criteria or success metrics, (5) Any scenario where you as the parent agent have a clear vision of what needs to be done and how, but need a dedicated executor to carry it out.\n\nExamples:\n- User: "I need to analyze this financial dataset and provide trading recommendations"\n Assistant: "I'm going to use the dynamic-task-executor agent with a quantitative analyst persona to analyze this dataset and generate trading recommendations based on statistical patterns and risk

Setting Up MCP Servers on Windows

A step-by-step guide to setting up Model Context Protocol (MCP) servers for Claude Desktop on Windows.

Prerequisites

Install Node.js (v18.x or later)
- Download from: https://nodejs.org/
- Verify installation by opening Command Prompt (CMD) and running:
```
node --version
npm --version
```

Windows 10 - Using Git Bash With TMUX

Why Not Use WSL?

I tried the WSL and it isn't quite seamless enough for me. I ran in to problems when editing in VSCode and having watchers on my files (ng serve, dotnet watch run, etc.). In addition, I kept running in to problems that only manifest themselves when running in WSL. For example, this issue with doing production builds and the terser plugin has made many a developer rage-quit on using WSL. Just figuring out that it was an issue with the WSL took a lot of time.

That terser plugin issue was never resolved and I ended up having to keep a git bash window open in addition to my WSL console window so I could do production builds. To make matters worse, my npm packages were platform-dependent so I couldn't use the same project folder. So, my procedure was: commit whatever changes to test branch, push to repo, git pull on my "windows" project folder, and do a production build there

	# need to have conda installed
	# these are instructions for macOS
	git clone https://github.com/OpenBMB/ChatDev.git
	conda create -n ChatDev_conda_env python=3.9 -y
	conda activate ChatDev_conda_env
	cd ChatDev
	pip3 install -r requirements.txt
	set OPENAI_API_KEY=your_key
	python run.py --task "[description_of_your_idea]" --name "[project_name]"
	python3 online_log/app.py

	#!/bin/bash

	CYAN="$(tput bold; tput setaf 6)"
	RESET="$(tput sgr0)"

	clear

	if command -v python3 > /dev/null 2>&1; then
	if [ $(python3 -c "print('ye')") = "ye" ]; then
	clear

	<?Php
	//Original version: http://www.uwgb.edu/dutchs/usefuldata/ConvertUTMNoOZ.HTM
	function UTMtoGeog($Easting,$Northing,$UtmZone,$SouthofEquator=false) //Convert UTM Coordinates to Geographic
	{
	//Declarations
	//Symbols as used in USGS PP 1395: Map Projections - A Working Manual
	$k0 = 0.9996;//scale on central meridian
	$a = 6378137.0;//equatorial radius, meters.
	$f = 1/298.2572236;//polar flattening.
	$b = $a*(1-$f);//polar axis.