@llama_index
How much can good documentation save an AI agent in cost and time? Turns out, a lot. We built a custom skill that teaches Claude how to parse PDFs more efficiently, then used real usage traces to find where it was wasting time and money (re-reading the same file over and over, taking unnecessary "screenshots" of pages, etc.) After a few rounds of fixes based on what we observed, the results vs. just having Claude read PDFs the default way: β 37% lower cost per question β Better answer quality across the board β Fewer wasted steps The big takeaway: look at what an agent actually leaves in its traces, and fix bottlenecks from there. Full case study ποΈ https://t.co/n3MNIlQvhm Benchmark code ποΈ https://t.co/qReW2KZwm5