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
Install
steipete/agent-scripts/clickclack · repository language: Shell
git clone https://github.com/steipete/agent-scripts
cp -r agent-scripts/skills/clickclack ~/.claude/skills/clickclackFrequently 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)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
skills/clickclack/SKILL.md
skills/clickclack/agents/openai.yaml