Are you the tech lead or the product exec of your agentic team? Don't underestimate what your agentic team can do for you.
Check out the skills for Claude Code (@ClaudeDevs)
If your agents have task-specific names, you're using agents in place of skills.
"frontend-agent." "database-agent." "testing-agent." Sound familiar?
The only things a subagent adds that a skill can't do are model routing and persistent memory. That's it.
In Claude Code, a skill already has a name, a description, allowed-tools, instructions, and bundled files. A subagent has a name, a description, allowed-tools, a system prompt, and optional skill references. The overlap is almost total.
So when you create an agent called "api-developer" and fill it with Express conventions, Prisma patterns, and Zod validation rules — you didn't build an agent. You built a skill and stuck it in an agent file.
This happens because people model their agents after their human teams. You have a frontend developer, a backend developer, and a QA engineer — so you build three agents. But agents aren't people. They don't need identities.
The only reasons to create distinct agent definitions are the parameters that make them structurally different from one another:
- model routing (Haiku for cheap exploration, Opus for complex reasoning)
- persistent memory (agent-scoped knowledge that compounds across sessions — each named agent builds its own)
That's the unique value of an agent definition. Everything else — domain knowledge, conventions, patterns, procedural expertise — belongs in skills and subdirectory-level CLAUDE.md files.
All you need is one generic agent definition with process instructions (how to recover from crashes, how to journal progress, how to escalate blockers, key learnings to be shared...just like persistent memory).
The skills carry the reusable knowledge and subdirectory CLAUDE.md files bind the right skills to the right part of the codebase.
Same agent lands in apps/api/? The CLAUDE.md there says "load express-api-patterns and prisma-patterns." Same agent lands in apps/web/? Different CLAUDE.md, different skills, different specialist.
The agent didn't change. The context did.
Stop naming agents after job titles. Start using them for what only they can do and make it easier to centralize your team's knowledge and capabilities in skills.
@nocodebackend@AnthropicAI Feel free to ask questions and I will respond and use the questions as a driver to create some concise instructions. I hope this gets you started!
Decided to connect @nocodebackend to @AnthropicAI (Claude Desktop) via their new MCP server approach.
I am now able to access any of my Xano APIs via Claude and ask questions about the data behind my Xano APIs!
@nocodebackend@AnthropicAI I used this video as my starting point. You should reference this to understand the basics. By following his Claude config instructions with my files (updated for your machine directories) you should be off to a good start.
https://t.co/xliUSWEl1h
@nocodebackend@AnthropicAI I did it the lazy way. This link is the zip file for the code. I still need to add some instructions, but didn't want to take longer than I have already.
https://t.co/RPpsbyDKUX
Solving technology transfer from current university research to your commercial SaaS business!
Check out my landing page and tell me what you think.
Signup and submit a research paper and I will return to you a niche SaaS business plan. #buildinpublic
https://t.co/VyjS1OaVt6
R1.61 is here! 🎉 Get ready for a smoother, more powerful building experience with this latest update, packed with highly requested features and improvements. Here's what's included: 👇✨
- 📋 Copy + paste in your function stacks
- 🧪 One-click test generation
- 🔄 Asynchronous functions
- 🔧 Patch function
- 📦 Bulk patch, update, & delete functions
- 🔍 Statement Explorer
Check out the thread for more details. 🧵
New Debugger, Who Dis? 🛠️
Included in yesterday's release was our revamped debugger. 🐞
👉 Experience traditional code debugging vibes in the No-Code world. Debug APIs, diagnose issues and turbocharge your workflow in Xano.
🛑 Set Breakpoints: Pause your run to examine the workflow meticulously.
🚶 Stepping Through: Jump in and out of functions and middleware, or explore nested function stacks to dive even deeper.
👀 New Variable Visibility: Get an overarching view of your variables as they execute.
🔍 Watches: Use JavaScript expressions to hold onto or change the data being created while your function stack is running.
⌨️ Keyboard Shortcuts: Speed up your debugging process with keyboard shortcuts.
Have you checked it out? What do you think?
Introducing the Xano Community Knowledge Base — a hub for valuable content! 🌟
Discover valuable resources within our Knowledge Base, where we've gathered:
📚 Article-style posts on topics like mastering for loops in Xano and a comprehensive OpenAI API Overview.
📹 Engaging videos crafted by the Xano team.
🌟 Content created by you, our talented community members!
📣 Calling All Content Creators — dive into our brand assets and utilize our convenient submission form to showcase your incredible creations in the Knowledge Base, making them accessible to everyone!
🔎 If you are browsing and can't find the content you're looking for? Submit a Video Request so we know what you want to see next!
Explore the Xano Community Knowledge Base here: https://t.co/PIeowh90FE
Let's keep learning and building together! 📚💪
I added a new API call to my custom GPT. I was able to easily get my GPT to save a favorite recipe by just telling to to "save this recipe". It knew to call the POST API I had just configured in the Actions of the GPT configuration 😳 @nocodebackend@ChatGPTapp#AI#GenAI
🚀 Big news! 🌐 Xano continues to take No-Code to new heights with today's announcement. We are excited to share that we've raised a $10M Series A.
With this, we will continue to solve problems for smaller businesses and lead the charge in demonstrating what Enterprise grade No-Code should look like.
Read the full announcement: https://t.co/E9Mlp3ltje
🚀 Entrepreneurship + Build in Public = Recipe for Success! 🔑🌟 Building a startup in the open, sharing your wins and struggles...connects you with a supportive community, attracts customers, and builds trust. Join the #BuildinPublic movement, #Entrepreneurship#Startup
From website building to managing databases, #NoCode is revolutionizing everything, proving it's not just a fad but a formidable opponent to traditional coding.