htpasswdGenerate htpasswd entries for Apache/Nginx basic auth password management. Use when creating credentials, managing password files, or verifying users.
Install via ClawdBot CLI:
clawdbot install bytesagain-lab/htpasswdGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://bytesagain.comAudited Apr 16, 2026 · audit v1.0
Generated Mar 21, 2026
System administrators and DevOps engineers use this skill to quickly generate htpasswd files for Apache or Nginx web servers. It enables secure access control for internal tools, staging environments, or protected directories by creating and managing user credentials without manual file editing.
Development teams employ the skill to manage access to shared development or testing servers. It allows adding or removing team members efficiently, ensuring only authorized personnel can access sensitive environments, and supports auditing via user listing to track permissions.
Security professionals utilize the skill to verify password hashes and list users in htpasswd files during security audits. It helps ensure compliance with policies by checking hash algorithms and identifying weak credentials, facilitating regular reviews of authentication mechanisms.
Cloud engineers integrate the skill into deployment scripts to automate the creation of htpasswd files for containerized applications or cloud instances. It streamlines setup in CI/CD pipelines, enabling dynamic user management for services like Kubernetes dashboards or API gateways.
Offer the skill as a free, open-source tool to build a user base, then generate revenue through paid support contracts, custom integrations, or enterprise features. This model attracts developers and organizations needing reliable assistance for security-critical tasks.
Develop a cloud-based service that wraps the skill, providing a web interface for managing htpasswd files across multiple servers. Revenue comes from subscription tiers based on user count, advanced analytics, and integration with other security tools.
Package the skill as part of a larger DevOps or security toolkit, selling it to companies as an add-on for automation platforms. Revenue is generated through bundle sales, where it enhances value by simplifying authentication workflows in existing ecosystems.
💬 Integration Tip
Integrate this skill into shell scripts or CI/CD pipelines using environment variables like HTPASSWD_ALGO to customize hash algorithms, ensuring compatibility with existing infrastructure tools.
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.