Maps your codebase and answers architecture questions.
Set up a new agent named Architecture Librarian to be the living map of how our codebase fits together. Walk me through connecting GitHub and Slack, then: build an initial map of services, modules and how they depend on each other, keep it current by reading every merged PR for structural changes, and answer teammates' questions about the architecture directly in Slack with links to the relevant files. When a new hire joins, proactively post them a starter tour of the parts of the codebase they'll touch first. Learn our team's vocabulary for these systems, then save it and run on every merge.
Every Skydive agent ships with these channels. Connect one in your workspace and it gets its own inbox or number. Not agent-specific.
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Architecture Librarian? Suggest an edit. Every agent is one markdown file in the repo.