The 🤖 Android team just released three things that are a great example of what your team or company can build too: - Android Skills - Android CLI - Android Knowledge Base developer.android.com/tools/agents/
Post
Skills are just normal agent skills, which most of us know by now. We even did a @fragmentedpodcast.com episode on the topic: fragmentedpodcast.com/episodes/304/ These skills inject the right context directly into the agent and help steer it when it’s working on specific tasks.
The Android CLI is basically the bridge between the non-deterministic world and the deterministic one. Once you have an agent guided by skills, the CLI gives it a reliable way to actually do the things. It exposes tools in a simple, structured way so agents can use them effectively.
0 reposts1 like
Then there’s the knowledge base. It gives the agent fresh context from Android documentation in a way that’s easy to search and retrieve. Instead of fumbling through webpages and 3rd party tools, the agent can pull in the right context when it needs it newsletter.iurysouza.dev/p/fixing-age...
Now, you put these pieces together and you get an agent that can understand and work with Android much better than before. My pro tip is that you can take that same idea and apply it to your own team or company. You probably already have custom scripts and tools, docs, and ways of doing things.
✍️ Harness Engineering: newsletter.iurysouza.dev/p/the-feed-s... ✍️ Knowledge Bases: newsletter.iurysouza.dev/p/fixing-age... 🎙️ Agent Skills: fragmentedpodcast.com/episodes/304/ 🎙️ Harness Engineering: fragmentedpodcast.com/episodes/307/