fcakyon/claude-codex-settings / plugins/reusable-app-components/skills/opendesk-support
opendesk-support
VerifiedThis skill should be used when user asks to "add OpenDesk support chat", "migrate from Tawk", "theme a support widget", "configure an OpenDesk AI bot", "sync chatbot knowledge", or "inspect OpenDesk chats through API or MCP". Covers self-hosted deployment, signed identity, product workspaces, AI answers, knowledge automation and support operations.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| assets/OpenDeskSupport.tsx | other | 916 B |
| assets/support-github.yml | config | 604 B |
| assets/support-openship.yml | config | 579 B |
| assets/support-widget.ts | script | 2.9 KB |
| references/deployment.md | markdown | 3.0 KB |
| references/integration.md | markdown | 3.2 KB |
| references/knowledge-and-theme.md | markdown | 6.8 KB |
| references/operations.md | markdown | 4.2 KB |
| scripts/sync-support.mjs | script | 3.4 KB |
references/deployment.md
View on GitHub# Self-hosted deployment
Inspect the existing fork, branch, Compose files, deployed commit and environment ownership first. Preserve persistent volumes and credentials across releases. Prefer the project's existing automatic deployment path after its required checks pass.
The current Akyon Labs installation uses `fcakyon/opendesk`, branch `fatih/openship`, with `openship.json`, `compose.openship.yml` and a Caddy HTTP proxy in `deploy/openship/`. The public host is `desk.akyonlabs.com` and OpenShip project is `proj_lhIHdT91C4ODHH60`. Read current configuration before reusing these values elsewhere.
## Service boundaries
OpenDesk has a Go application with embedded NATS, an Elixir/Phoenix realtime gateway, and PostgreSQL with pgvector. Its upstream `compose.external-proxy.yml` is an override, not a standalone deployment file. The OpenShip fork has a dedicated standalone Compose file to avoid importing optional upstream profiles unintentionally.
Route `/socket` and `/socket/*` to realtime port 4000 and other requests to the app port 8080. The small proxy exposes port 80 to OpenShip, which owns public TLS and Cloudflare DNS. Preserve the trusted proxy chain and verify visitor IP handling against the actual topology. Do not copy `TRUSTED_PROXY_HOPS` blindly to a different chain.
Keep database credentials, `AUTH_SECRET`, `CREDENTIALS_KEY`, NATS credentials, realtime secrets and provider keys in server secrets. Back up `CREDENTIALS_KEY` with PostgreSQL and retained uploads. Losing it can make stored credentials unreadable. Pass the AI key only to the backend service that calls the provider.
For OpenShip, follow the instance's existing deployment and DNS conventions. Verify the configured branch, automatic deploy setting, workflow gate, service health, deployed commit, certificate, domain target port, widget asset and realtime connection. Environment changes need the platform's service apply or a redeploy. A successful build alone does not verify the running service.
## Branding
As verified on the Akyon Labs fork on 2026-11-08, the embedded widget's "Powered by opendesk" footer was hardcoded, with no built-in white-label toggle. The fork removes its footer markup, styles and locale strings. Inspect the current SDK for a supported option before carrying that patch through an upgrade. Preserve license notices. Widget footer removal is distinct from dashboard branding. On `fcakyon/opendesk` (`fatih/openship`), setting widget `show_team: false` also withholds personal teammate names and avatars from visitor messages, teasers and chat follow-up emails so human replies continue under the brand logo and title.
## Release checks
Use the normal autodeploy branch and inspect CI and service logs without exposing environment values. Check health, login, the public widget script, a real chat, AI provider response, human handoff and workspace isolation. Confirm browser assets and responses contain no management or provider credentials. Remove test origins, synthetic test conversations and temporary browser sessions after verification.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |