docs: add weekly digest agent skill blog post#2673
docs: add weekly digest agent skill blog post#2673Lotte-Verheyden wants to merge 2 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📦 Next.js Bundle Analysis for langfuse-docsThis analysis was generated by the Next.js Bundle Analysis action. 🤖 New Page AddedThe following page was added to the bundle from the code in this PR:
|
Made-with: Cursor
dosubot
bot
added
the
size:L
| import { FileTree } from "nextra/components"; | ||
|
|
||
| <BlogHeader | ||
| title="How We Built an Agent to Synthesize our User Inputs" |
There was a problem hiding this comment.
Would call it agent skill
Myb also: How We Built an Agent Skill to Synthesize what Langfuse Users want
| authors={["lotteverheyden"]} | ||
| /> | ||
|
|
||
| At Langfuse, support tickets and GitHub issues go directly to the engineer who owns that area. Meeting transcriptions get shared around. People notice patterns and flag them in Slack. It works, but nobody has time to read across all of it every week. So we built an AI agent skill that does it for us: it reads through our support tickets, GitHub issues, and meeting transcriptions and synthesizes them into a weekly digest of what users are experiencing. |
There was a problem hiding this comment.
Would maybe intro with: At Langfuse user inputs land on our desks through a variety of channels. Support tickets and Github issues go directly to engineers. Meeting notes from customer interactions get shared around. People notice ....
It works, but nobody has time to consolidate what's on our customers mind in one single source of truth every week. So we built an AI Agent ...
|
|
||
| ### Category names carry implicit assumptions | ||
|
|
||
| The third version introduced a "Quick Fixes" category, but AI doesn't know how quick a fix will be. We renamed it to reflect what we *do* know: whether the path forward is clear or needs discussion. Watch for labels that embed assumptions the model can't verify. |
There was a problem hiding this comment.
We could add a 'where we see it going section'
- The skill auto assigning respective engineers
- Incorporating more sources where langfuse is discussed
- The skill based on documentation and codebase proposing approaches on how to deal with it,...
annabellscha
left a comment
annabellscha
left a comment
There was a problem hiding this comment.
Added some comments! But i think its a nice illustrative use case!
2 participants
Adds the blog post "How We Built an Agent Skill to Synthesize 500+ Weekly Support Signals".
The post covers:
TODOs before publishing