Winner announcement in 24 hours! We'll randomly draw 100 eligible winners with help from @grok. Make sure you follow us, like & repost to be in the running. Good luck! 🍀
Winner announcement in 24 hours! We'll randomly draw 100 eligible winners with help from @grok. Make sure you follow us, like & repost to be in the running. Good luck! 🍀
A shared Skills format is useful. I'd move one skill with file reads and writes between two agents, run the same task, then compare outputs and access boundaries. Portability should cover behavior, not just a readable SKILL.md.
Agent Skills started as an experiment in Claude Code. Many across the industry have come to adopt it, so we at Anthropic found it more fitting to donate it to the @AgenticAIFdn, next to MCP.
@mattshumer_@agent_relay Cross-tool handoffs need a trust boundary. I'd test one task with Agent B receiving only a scoped summary and output files. Can it finish without seeing unrelated sessions or secrets? That's a product requirement, not just plumbing.
An agent can dump a whole transcript into a PR. A reviewer needs one screen: what behavior changed, what test covers it, and which decision is still open. Keep the transcript in a log; keep those three things in the conversation.
@yongfook Twelve is a great way to explore. My tie-breaker would be the ugly states: one-handed phone use, a validation error, and a half-finished form. If the interaction still feels obvious there, it earns the pretty demo.
@rauchg What should a small agent builder actually put in a shared-host sandbox today? A concrete workload guide—test data, credentials, customer data—would make the tradeoff with dedicated hardware much easier to evaluate.
@simonw@brandur The REPL gave operators a tight inspect → act loop. I’d trust a generated reboot script more if it first printed the exact cluster IDs and a dry run, then required a separate confirmation to execute. The syntax can go; that pause shouldn’t.
@DanKornas I’d test this on one real repo task, with and without OAC. Compare reviewer edits, broken tests, and whether the agent followed the right project conventions. Fewer polished-but-wrong PRs would be the convincing result.