authorizationBuild secure access control with RBAC, ABAC, permissions, policies, and scope-based authorization.
Install via ClawdBot CLI:
clawdbot install ivangdavila/authorizationGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawic.com/skills/authorizationAudited Apr 17, 2026 · audit v1.0
Generated Mar 20, 2026
A company building a multi-tenant SaaS application needs to control user access across different organizations and roles. This skill helps implement RBAC for organizational hierarchies and ABAC for dynamic context-based rules, ensuring secure access control for features like document editing and team management.
A healthcare provider requires strict access control to patient records based on roles (e.g., doctors, nurses) and dynamic policies (e.g., emergency access). This skill supports scope-based authorization to enforce privacy regulations like HIPAA, allowing permissions such as 'records:view:own' or 'records:edit:team'.
An online retailer needs to manage permissions for staff handling orders, inventory, and customer support. Using this skill, they can design role hierarchies (e.g., admin, manager, support) with clear permission naming like 'orders:update:all' to prevent unauthorized changes and audit access logs.
A team collaboration platform requires fine-grained access control for document sharing and editing based on user relationships. This skill enables ReBAC patterns for social graphs and ABAC for dynamic rules, ensuring users can only edit documents they own or are shared within their team.
Companies offer tiered subscription plans with different access levels (e.g., free, premium, enterprise). This skill helps implement permission-based features, allowing upselling through enhanced roles and policies while maintaining security with server-side verification.
Agencies or freelancers use this skill to build secure authorization systems for clients in industries like finance or healthcare. They charge for design, implementation, and auditing services, leveraging the skill's patterns to reduce development time and ensure compliance.
Developers release the authorization skill as open-source to build community trust, then monetize through paid support, training, or enterprise features. This model attracts users who need reliable access control but require assistance with complex ABAC implementations.
💬 Integration Tip
Start with simple RBAC for basic role hierarchies, then gradually introduce ABAC for dynamic rules; always verify permissions server-side to avoid security vulnerabilities from frontend-only checks.
Scored Jun 19, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Sentry API integration with managed authentication. Monitor errors, issues, and application performance. Use this skill when users want to list issues, retrieve events, manage projects, teams, or releases in Sentry. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Sentry connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Sentry action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Sentry examples; they add no Sentry capability - Sentry is not an event source, a trigger cannot read Sentry data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Download YouTube videos by URL in various resolutions using a pay-per-use API with credit-based authentication and no charge on failed downloads.
OneNote API integration with managed OAuth via Microsoft Graph. Access notebooks, sections, section groups, and pages. Use this skill when users want to create or manage OneNote notebooks, organize notes, or work with page content. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an OneNote connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an OneNote action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with OneNote examples; they add no OneNote capability - OneNote is not an event source, a trigger cannot read OneNote data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).