← All IntelClip / AI AgentsNobody reads the docs, so the skill became the advertised path
From Skill issue: Lessons from skilling up coding agents to use Langfuse - Marc Klingen, Clickhouse · ≈18:51
A vendor reorganizing its docs around 'ask your coding agent' — and extending skills past setup into the eval lifecycle, like clustering feedback across 100 executions via the CLI.
What’s in it
- A vendor reorganizing its docs around 'ask your coding agent' — and extending skills past setup into the eval lifecycle, like clustering feedback across 100 executions via the CLI.
Clip transcript
give us feedback um because that would be really interesting. Um and uh like uh we do lots of lots of calls with people from the community every week, and uh like like uh I think it's not a surprise that I think nobody reads documentation themselves, and everyone is just like, "Yeah, just add this to my like I just want this to work. Like just add it." Um so, yeah, the skill is the primary way of how things get done. This is also like now the advertised way across all of our documentation um that you just should ask your coding agent to do whatever you try to do right now. Um I'm very excited that works really well, uh but also I'm I'm excited to see what what comes next. Um for us as a project roadmap-wise, we see the skill right now like our users use this when getting started with the project, but also um uh to drive a lot of automation around the like evaluation life cycle of oh I now want to create like an element as a judge that's aligned with user preferences or um like I got user feedback on 100 different executions, what do they have in common? And you just then fetch this via the CLI. So many of these workflows that people needed to do manually now coding agents do for them.
Comments
Sign in to comment.
Loading comments…