by bOpen

[ PORTABLE SKILL ]

device-authorization

This skill should be used when the user asks to "implement device auth", "add device authorization", "authenticate desktop app", "authenticate CLI tool", "device code flow", "RFC 8628", "poll for token", "get user info after device auth", or mentions authenticating apps that can't handle browser redirects. Provides step-by-step guidance for device authorization with Sigma Identity.

PART OF

sigma-auth →

Install the complete plugin to include its agents, hooks, commands, and runtime context.

Claude pluginCodex pluginGrok BuildOpenCode + portable skills

PUBLISHER: b-open-io
RELATIONSHIP: authored
VERSION: 0.1.0
BENCHMARK: unknown

[ INSTALL ]

Install device-authorization

Fastest path: hand this line to the coding agent doing the setup. It reads this page and installs the sigma-auth plugin, which ships this skill with everything it relies on.

PROMPTPASTE INTO YOUR AGENT

Click anywhere on the prompt to copy.

[ MANUAL SETUP ]

Choose a runtime, then follow its setup steps. This installs the complete sigma-auth plugin.

COMPLETE PLUGIN

View an example

Example installation for sigma-auth

Example session using the verified commands above.

CLAUDE CODE

EXAMPLE SESSION~/dev/project

/plugin install sigma-auth@b-open-io

Plugin(sigma-auth)Installed sigma-auth for Claude Code

Claude Code is ready to use.

[ ADVANCED ] INSTALL ONLY THIS SKILL

The portable SKILL.md on its own, without the plugin’s hooks, agents, commands, and companion skills. Use it only when you intentionally want the narrower path.

Skills CLI

Grok Bot

[ PROVENANCE ]

Trace it to the source.

DISTRIBUTED SOURCE: skills/device-authorization/SKILL.md ↗
UPSTREAM SOURCE: No separate upstream declared
DISTRIBUTED DIGEST: sha256:5029f28cc0bdc81a23c75852d77906aecb089378966fcf4fe21ce1c627fc76fb
LOCK HASH: Not applicable

Companion skills

No required companion skills are declared.

Agents using this skill

Siggy

Use this agent when the user asks about implementing Sigma Auth, Bitcoin authentication, BAP identity, Better Auth plugins, or using @sigma-auth/better-auth-plugin. Expert in OAuth 2.1, PKCE, WebAuthn, session management, and blockchain-native authentication patterns. <example> Context: User wants to add Sigma Identity auth to their Next.js app user: "How do I add Sigma Auth to my app?" assistant: "I'll use the sigma-auth-guide agent to help you implement Sigma Identity authentication with the Better Auth plugin." <commentary> User is asking about implementing Sigma Auth - this agent has comprehensive knowledge of the @sigma-auth/better-auth-plugin package. </commentary> </example> <example> Context: User has OAuth callback errors user: "I'm getting 'invalid state parameter' when signing in" assistant: "I'll use the sigma-auth-guide agent to diagnose the OAuth callback issue." <commentary> OAuth/PKCE troubleshooting is core to this agent's expertise. </commentary> </example> <example> Context: User wants to understand BAP identity user: "What is BAP and how does it work with Sigma Identity?" assistant: "I'll use the sigma-auth-guide agent to explain BAP (Bitcoin Attestation Protocol) and its integration." <commentary> BAP identity protocol is a core component of Sigma Identity authentication. </commentary> </example> <example> Context: User needs to verify user identity with Bitcoin signatures user: "How do I verify a user's Bitcoin signature in my API?" assistant: "I'll use the sigma-auth-guide agent for Bitcoin signature verification patterns." <commentary> Bitcoin signature auth is central to Sigma Identity's approach. </commentary> </example>

[ SOCIAL SHARE ]

Share this skill.

Pass the canonical page to a teammate or keep it close for later.

SHARE TO X LINKEDIN