oh damn, can you share what the skill is actually doing for you like on a daily basis: is it creating clusters, scoring known issues, or finding new patterns? and what data points are you giving it to if any w the messages?

usually a boundary for us is usually where a skill/claude analysis needs to maintain/make changes/pass it to an agent as a workflow

for the pricing we're still learning and building as many custom features/requirements as possible bec we wanna make sure we deliver way more value than what we charge today.

Classification of types of user frustrations and sentiment analysis, content trends, engagement and gap analysis, as well as then looking at changes from the previous week. We also look at how certain queries turn into actions in the system (eg: which users take actions we offer them). We run it once a week, rather than every day, and it provides an exec-facing overview, as well as areas for support to dig further in to. While it's some good work, as far as I'm aware it's almost all just a text prompt and a connection into Langfuse.

okay nice, also is it safe to assume you do once a fortnight releases then? like look at the last week's data then use it for product decisions the coming week?

also have you updated/made any changes to this skill that has improved it significantly?

and anything you hate/wish it had as of today? wanna learn if there's any painpoints around this? is it keeping the skill updated, getting useful signal from the clusters, or turning the findings into something the rest of the team can actually act on?