Architecture

How Skilder is built, how it runs your roles and skills, and how it protects your data.

Read this section if you are evaluating Skilder for your own stack. It answers where your data sits, what runs your code, and who can reach it.

None of it is required reading to use Skilder. Start with Basics for that.

The components, the boundaries between them, and what crosses each one.

What happens when an agent calls a tool, and what a script can reach.

Identity, permissions, encryption, hosting and the audit record.

Auto-Learning

Turn observed agent usage into improvements to your roles and skills.

Platform overview

The components Skilder is built from and the boundaries between them.