actually make changes here because I'm seeing opportunities to improve. Real prompt I just wrote that might be helpful for you guys to see how I work with agents. This is in my fleet repo where I manage all of this content. I want to make a few more small changes. I've made more since my last prompt, so refamiliarize yourself before editing. The HTML communication skill is a bit overloaded. I want to break it in two, similar to the file PR and babysit PR skills, cuz I worked with this instance in this thread for that in the past. The descriptions for both should be really simple, focused on when to trigger and not what it is. One should be postplan read for reading content from postplan URLs. The other should be HTML communication for communicating to the user via HTML. When to use section should not exist in the post plan scale, only the HTML communication one. It should also be more minimal. Make your changes. Don't commit or push to any machines yet. I'll tell you when. This is just because I'm using soul and I want to make sure it doesn't overdo so I tell it where to stop. When you give the model a stop point, life gets much better. Remember earlier when I said to go fix the feature with settle,