I think the main issue is the information hierarchy in this demo
title.. “I built an agent that finds cheap flights for me ft @neatlogs” naturally makes the cheap flight agent feel like the main thing and neatlogs as supporting thing used to make it
then the rest of the video kept reinforcing the same story finding flights, prices, getting alerted, etc
neatlogs abstraction: agent trace -> detect a condition -> alert
if it only becomes obvious once its explained is usually a sign the demo can communicate that part better
@liftplaycode idk wtf is neatlog but seeing this video tells me its no different from schedule in chatgpt?.. if its smth else then its just a bad demo
and you are too ignorant for me to explain anything without criticising that you wouldnt hate
@pathikghugare few thing to take care of.. it creates worktree forked from main to work on and automatically uses cheaper model like sonnet which is really slow
So if you wanna change any of that specifically add while using skill