You don’t need a skill. Just tell it to BLUF (bottom line up front) and ASD-STE100.
And stop using Opus 9 Pro Max XHigh 10.0 for everything. If you choose a hyper-thinking model for asking the weather you can’t but expect yapping.
And stop using Opus 9 Pro Max XHigh 10.0 for everything. If you choose a hyper-thinking model for asking the weather you can’t but expect yapping.
I also don't know how much to trust the model, but I've had the model tell me specifically that certain aspects of ASD-STE100 are unactionable and will just create more noise.
The OP's own skill even leads with something in a very similar vein:
> These rules apply to every response for the rest of the session, not only this one. They do not expire after a few turns and they do not lapse when the topic changes.
My understanding is that phrases like this are at best a _very_ weak signal to the model. It's simply contradictory to how the model works at a level that can't be overridden by injecting tokens.
I placed those instructions in setting > personal instructions, in my global CLAUDE.md, and in each project’s CLAUDE.md. I also use the concise output style in CC. If I choose a high thinking model it will start deviating in long sessions, then I just remind it in my next message:
“Remember ASD-STE100 style.
[rest of my message]”
BLUF sticks a lot easier than STE to be honest… but Claude knows what STE is, and using the “ASD-STE100 style” locution avoids the compliance issue (it’s true that strict ASD-STE100 compliance isn’t really possible, nor desired)