local-approvalsLocal approval system for managing agent permissions. Use CLI to approve/deny requests, view history, and manage auto-approved categories.
Install via ClawdBot CLI:
clawdbot install shaiss/local-approvalsGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 1, 2026
A financial institution uses this skill to manually approve AI agent requests for sensitive operations like fund transfers or report generation before execution. It ensures regulatory compliance by logging all approvals and denials in state.json for audit trails.
In a hospital setting, AI agents handling patient records must get approval for accessing or modifying data. This skill allows administrators to review requests based on category, such as medical history updates, and auto-approve trusted categories after initial vetting.
A tech company employs this skill to manage AI-driven infrastructure changes, like server deployments or configuration updates. Engineers approve requests via CLI, using the --learn option to auto-approve safe categories after validation, reducing manual oversight over time.
An e-commerce platform uses the skill to approve AI agent actions for order cancellations or refunds. Managers review pending requests to prevent errors, with history tracking helping identify patterns and optimize auto-approval lists for routine tasks.
An online learning platform integrates this skill to approve AI-generated content or user submissions. Moderators use the CLI to list and review requests, denying inappropriate categories and resetting auto-approvals if issues arise, ensuring safe educational environments.
Offer this skill as part of a subscription-based AI management platform, charging monthly fees for features like advanced analytics on approval history and priority support. Revenue scales with the number of agents or approval volume managed.
Sell perpetual licenses to large organizations for on-premises deployment, with customization options for integration into existing security systems. Revenue comes from one-time license fees plus annual maintenance and update charges.
Provide consulting services to help businesses implement and customize the skill, including training, workflow design, and integration with other tools. Revenue is generated through project-based fees and ongoing support contracts.
💬 Integration Tip
Integrate this skill by calling core functions like submit_request from other AI agents, and use the CLI for manual oversight; ensure state files are backed up regularly to prevent data loss.
Scored Apr 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).
Host static files on subdomains with optional authentication. Use when you need to serve HTML, images, CSS, JS, or any static content on a dedicated subdomain. Supports file upload, basic auth, quota management, and automatic SSL via Caddy. Commands include sf sites (create/list/delete), sf upload (files/directories), sf files (list/delete).
Download YouTube videos by URL in various resolutions using a pay-per-use API with credit-based authentication and no charge on failed downloads.