@CameronMThacker@vercel IMO, I think the approach works great for scoped problem sets, e.g., pass on to a subagent.
Scaling is a valid question.
My thoughts are that the main problem is "untriggered Skills". Fix that, and you have a better comparison
https://t.co/vHfd8L1Y8Z
A bit of an apples-to-oranges comparison to compare untriggered Skills vs compressed Agents(dot)md file
If the Skills aren't triggered, they don't exist (to the model)
Nothing to compare (in terms of execution)
The sound comparison would be to fix the Skills trigger, then compare deterministic executions across both
And in the future, the tooling around Skills needs evals. Evals for Skill triggers
@intellectronica@trq212@sughanthans1 100%. For engineers, the “aha” lands even harder when Skills are remote + composable (not trapped on one's machine).
Demo idea: load a Skill into a Vercel AI SDK / LangChain (TS) agent and run it from anywhere.
@gary_qz@vercel It comes to triggering a Skill. Same way you have evals for good ol' prompts.
If your Skills aren't triggered, they effectively don't exist.
A better comparison would be to fix the Skill triggers (use evals or other means), then compare against a deterministic workflow
Nicely done.
nitpick: In the Creating Hedera Agent Kit Plugins Skill, you'll get better results by writing out the exact scripts.
Rather than "Install dependencies: Set up a TypeScript project with hedera-agent-kit and @hashgraph/sdk"
Basically, the scripts from https://t.co/SBBoN5okqL
A bit of an apples-to-oranges comparison to compare untriggered Skills vs compressed Agents(dot)md file
If the Skills aren't triggered, they don't exist (to the model)
Nothing to compare (in terms of execution)
The sound comparison would be to fix the Skills trigger, then compare deterministic executions across both
And in the future, the tooling around Skills needs evals. Evals for Skill triggers
@0xcgn@steipete One of the best rules I've found is to add something like:
"When in doubt, ask questions and await my approval before continuing. Do not assume. Simply ask me, and I'll confirm what to do"
Helps with brainstorming before rushing off to confidently create wrong solutions
@cursor_ai Would’ve been great to include a quick example of how these traces would render in common observability tooling (e.g., spans/attributes in OTEL, a sample timeline in a trace UI).
The spec is “UI agnostic,” but a reference visualisation would help adoption.
A bit of an apples-to-oranges comparison to compare untriggered Skills vs compressed Agents(dot)md file
If the Skills aren't triggered, they don't exist (to the model)
Nothing to compare (in terms of execution)
The sound comparison would be to fix the Skills trigger, then compare deterministic executions across both
And in the future, the tooling around Skills needs evals. Evals for Skill triggers
We're experimenting with ways to keep AI agents in sync with the exact framework versions in your projects. Skills, 𝙲𝙻𝙰𝚄𝙳𝙴.𝚖𝚍, and more.
But one approach scored 100% on our Next.js evals:
https://t.co/8ACw9BgudB
🔥 This is exactly what I needed!
Vercel AI SDK + Agent Skills = game changer for building smarter AI agents 🚀
Perfect for anyone building:
- Custom chatbots
- AI automation tools
- Specialized agent workflows
The thread breakdown is 🔥 - check it out 👇
#AI#Vercel #AgenticAI #WebDev
We're proposing an approach to make discovering agent skills easier by using the .well-known URI standard + a index of associated files for agents to pull down.
There's tools (like add-skill) to add skills, but you have to find them first.
RFC: https://t.co/9Qrf0aXJ5D
But what happens under the hood?
Your agents immediately:
- Get access to runtime virtual machines
- Run complex scripts and read Skills on-demand
- Leverage a rich file API to mint download links
All without managing any infrastructure
(4/5)