Umbraco Auth Provider
CheckedSecurely integrates Umbraco websites with external authentication providers via a streamlined AI-powered configuration process.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add umbraco/umbraco-cms-backoffice-skills --skill umbraco-auth-provider -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
umbraco
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned umbraco/umbraco-cms-backoffice-skills at 78b551bf9c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 78b551bf9c
- Scanned
- 1 file, 220 lines
About this skill
What it does
This skill enables Umbraco websites to securely integrate with external authentication providers, such as Google, Microsoft, or GitHub, for backoffice login (OAuth/SSO). It provides the user interface component – a login button – within the Umbraco backoffice. Crucially, this skill handles only the frontend presentation and behavior; the backend authentication provider configuration must be set up separately in C#.
When to use it
- You want to allow your Umbraco backoffice users to log in using their existing accounts from external providers (e.g., Google Workspace).
- You need to implement Single Sign-On (SSO) for the Umbraco backoffice.
- You are integrating a custom OAuth authentication provider with your Umbraco website.
Key capabilities
- Provides UI components (login buttons) for external authentication.
- Supports common providers like Google, Microsoft, and GitHub.
- Allows for custom OAuth provider integration.
- Generates frontend files including manifests and optional custom elements.
Example prompts
- "Create an Umbraco Auth Provider manifest to enable login with GitHub."
- "Generate the necessary files for a custom authentication provider named 'MyAuthProvider'."
- "Show me an example of a manifest file for integrating Google Workspace login into the Umbraco backoffice."
Tips & gotchas
- Backend Configuration Required: This skill only handles the frontend. You must configure the corresponding C# authentication provider in your Umbraco backend first. Refer to the External Login Providers documentation for details.
- Manifest File: The skill generates a manifest file (umbraco-package.json). This file defines the provider's name, alias, and appearance within the Umbraco backoffice.