girlbossrush/authentik-agent-marketplace/concepts

authentik concepts and documentation

Purpose

New admins routinely conflate authentik's objects: Applications with Providers, Sources with Providers, Flows with Stages. Those mix-ups lead to misconfigured logins. This skill explains what each object is, how it connects to the others, and where the authoritative docs live, so the user has the right mental model before they touch configuration.

When to invoke

• "What's the difference between an Application and a Provider?"
• "What is a Flow? How does it relate to Stages and Policies?"
• "Is Google a Source or a Provider in authentik?"
• "What's an Outpost and when do I need one?"
• "Where are the docs for SCIM provisioning?"
• The user describes an outcome but doesn't know which object builds it.

Not this skill: building or changing an actual object. Once the user understands the concept and wants to act, route to the specific skill that owns that object.

From outcome to object

A user rarely says "Provider." Translate what they want into what to build, then hand off to that skill:

Finding the docs

authentik changes between releases — prefer the live docs over memory: use the authentik docs base URL from your session context (or the authentik-code-mode MCP's docs tool, which returns the version-accurate URL), then fetch <docs>/llms.txt (integrations: <integrations>/llms.txt), follow the index to the right page, and fetch its .md.