clickclack
Manage ClickClack's Cloudflare Worker deployment, container lifecycle, and operational verification. Handles app rollouts, DNS routing, and health checks across product surfaces and documentation.
ClickClack handles deployment to Cloudflare Workers, container rollouts, and operational checks for the hosted chat application.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-23
ClickClack handles deployment to Cloudflare Workers, container rollouts, and operational checks for the hosted chat application. Manage ClickClack's Cloudflare Worker deployment, container lifecycle, and operational verification. Handles app rollouts, DNS routing, and health checks across product surfaces and documentation.
Use it when
- ClickClack app verification involves checking Worker endpoint responsiveness, confirming DNS records point to your Cloudflare domain.
- ClickClack production troubleshooting starts with verifying environment variables are correctly set in your Cloudflare Worker configuration.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
steipete/agent-scripts/clickclack · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I deploy ClickClack to Cloudflare Workers?
ClickClack deploys to Cloudflare Workers using wrangler, the official CLI tool. Push your configuration and application code through wrangler deploy, which handles Worker instantiation and routing setup. ClickClack's deployment process integrates with your Cloudflare account, enabling serverless chat infrastructure without managing traditional servers. Refer to ClickClack's ops guide for environment-specific wrangler configuration and authentication tokens.
What steps verify ClickClack app health and DNS configuration?
ClickClack app verification involves checking Worker endpoint responsiveness, confirming DNS records point to your Cloudflare domain, and validating backend connectivity (Supabase PostgreSQL, R2 uploads). Health checks confirm the chat app responds to requests and message routing functions correctly. DNS configuration must resolve your custom domain to the Cloudflare Worker. ClickClack's verification steps include testing message delivery and confirming all infrastructure dependencies are reachable.
How do I troubleshoot ClickClack production issues?
ClickClack production troubleshooting starts with verifying environment variables are correctly set in your Cloudflare Worker configuration. Check Supabase PostgreSQL connectivity, R2 bucket permissions, and Worker logs via the Cloudflare dashboard. Confirm DNS resolution and Worker custom domain routing. Review ClickClack's prod environment setup documentation for common misconfigurations. Test container rollouts incrementally and validate app health after each deployment step.
What is ClickClack's architecture and hosted infrastructure?
ClickClack runs on Cloudflare Workers for serverless compute, Supabase for PostgreSQL data persistence, and Cloudflare R2 for file uploads. The architecture supports self-hosted and managed deployments. Container rollout management handles staged updates across Worker instances. ClickClack's infrastructure is designed for scalability without operational overhead, leveraging Cloudflare's global edge network for low-latency chat delivery.
Where can I find ClickClack documentation and deployment guides?
ClickClack documentation is hosted on GitHub Pages and includes deployment guides, ops procedures, and troubleshooting resources. The product site status page shows infrastructure health. ClickClack's ops guide covers wrangler deploy workflows, container instance management, and environment configuration. Documentation links are available on the main ClickClack site and in the project repository.
How does ClickClack handle container rollouts and updates?
ClickClack container rollout management coordinates staged deployments across Cloudflare Worker instances. Updates are deployed through wrangler, which manages versioning and traffic routing. Rollouts support gradual traffic shifting to minimize disruption. ClickClack's runtime operations include monitoring rollout progress, verifying app health after each stage, and rolling back if issues arise. Container instance management ensures consistent configuration across all deployment targets.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
ClickClack
Use this for ClickClack product/runtime ops, deploys, hosted app checks, and domain questions.
What
- Repo:
~/Projects/clickclack/https://github.com/openclaw/clickclack - Product: self-hostable Slack-style chat for OpenClaw/community/agent workflows.
- Surfaces:
https://clickclack.chatproduct site (Cloudflare Worker custom domain)https://www.clickclack.chat(Worker custom domain, same worker)https://app.clickclack.chathosted app (Worker custom domain)https://docs.clickclack.chatGitHub Pages docs fromdocs/
Prod (Cloudflare, since 2026-07-05)
- Everything is one Cloudflare Worker
clickclackin the OpenClaw account (91b59577e757131d68d55a471fe32aca) fronting a Cloudflare Container. - Worker + container config:
wrangler.jsonc(routes are declarativecustom_domainentries). - Container: Go binary + embedded SPA from
Dockerfile.cloudflare; data in Supabase Postgres (CLICKCLACK_DBsecret) and R2 uploads (clickclack-uploads). - Zone
clickclack.chatide7f93ba1ec24d75ce60c468bbaba5cb5
(truncated - see the full file via the links below)
File tree — 2 files
skills/clickclack/SKILL.md
skills/clickclack/agents/openai.yaml
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Deploy ClickClack to Cloudflare Workers and manage container rollouts”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Mkfast Deploy streamlines deploying mkfast-template and TanStarter projects to Cloudflare Workers by detecting which components you've enabled and generating only the steps you need. It handles template placeholder validation, environment setup, and production safety checks to prevent common deployment pitfalls.
Cloudflare Agentic Inbox is a self-hosted email client powered by AI agents, built entirely on Cloudflare Workers. It combines Email Routing for receiving messages, Durable Objects with SQLite for per-mailbox storage, R2 for attachments, and Workers AI for intelligent email assistance.
Cloudflare Knowledge equips you with patterns and templates for building on the Cloudflare edge platform—Workers, Pages, R2, D1, KV, Durable Objects, and Workers AI. Reference guides cover wrangler configuration, storage service trade-offs, AI model selection, and Zero Trust setup.
Vite Flare Starter clones and configures a complete Cloudflare full-stack template into a standalone, production-ready project. It bundles React 19, Hono on Workers, D1 with Drizzle ORM, better-auth, R2 storage, Workers AI, and TanStack Query—all pre-wired and ready to deploy after running setup.
This skill equips you to build and deploy applications on Cloudflare's edge network using Workers, a serverless platform supporting JavaScript, TypeScript, and WebAssembly. It covers environment bindings, storage services (KV for caching, D1 for SQL, R2 for objects), Durable Objects for stateful coordination, and Wrangler CLI for local development and deployment.
Wrangler is Cloudflare's command-line tool for building and deploying Workers across the edge platform. It handles local development, deployment, and management of Workers alongside bindings for KV storage, R2 buckets, D1 databases, Vectorize indexes, and Workers AI. The skill prioritizes current documentation over cached knowledge to ensure commands and config syntax stay accurate.
More skills Wrangler (unlicensed) · cloudflare-temporary-deploy (MIT)