Skip to content

xhluca/agent-talk / skills/relay

Set up, check, stop, or delete a retalk relay server (retalk-server). Use when the user needs their OWN relay rather than an existing URL. Invoke as `relay setup`, `relay ping`, `relay stop`, or `relay delete`. Uses AskUserQuestion to pick the host (Local / Local+Cloudflare / Hugging Face / GCP) and gather settings.

FileKindSize
SKILL.mdskill md6.0 KB
cloudflare.mdmarkdown2.3 KB
gcp.mdmarkdown4.2 KB
huggingface.mdmarkdown2.5 KB

cloudflare.md

View on GitHub
# relay setup — Cloudflare Tunnel (expose a LOCAL server publicly)

Run `retalk-server` on your own machine (or any box) and give it a public HTTPS
URL via Cloudflare — no open firewall port, no TLS cert, no cloud VM.
`cloudflared` makes an outbound connection to Cloudflare, which forwards public
requests down it to your local server (TLS terminated at Cloudflare's edge; the
server still speaks plain HTTP). Two ways:

- **Quick tunnel** — free, no account, no domain. Random
  `https://<words>.trycloudflare.com` URL that lasts only while `cloudflared`
  runs. Best for a quick or throwaway public relay.
- **Named tunnel** — your own domain on a Cloudflare account; a stable hostname
  that survives restarts. Use for anything lasting.

**The one rule:** `RETALK_SERVER_AUDIENCE` must equal the public `https://…`
Cloudflare URL (not `http://localhost:…`), or every request fails `bad
signature`.

Install `cloudflared` first: https://github.com/cloudflare/cloudflared

## Quick tunnel (free, no account)
1. Start the tunnel on the server's port; copy the URL it prints:

       cloudflared tunnel --url http://localhost:8766
       # -> https://<words>.trycloudflare.com

2. In another terminal, start the server with that URL as its audience:

       RETALK_SERVER_DB=./relay.db RETALK_SERVER_PORT=8766 \
         RETALK_SERVER_AUDIENCE=https://<words>.trycloudflare.com retalk-server

3. Clients use that same URL as `RETALK_RELAY`.

The URL changes each time you restart the quick tunnel.

## Named tunnel (your domain, stable) — preferred for real use
Use a per-tunnel **token** (safer than `cloudflared tunnel login`, which scopes
to your whole Cloudflare zone):

1. Cloudflare Zero Trust dashboard → Networks → Tunnels → Create a tunnel; copy
   the token.
2. `cloudflared tunnel run --token <TOKEN>`
3. On that page, add a public hostname (e.g. `retalk.example.com`) routing to
   `http://localhost:8766`.
4. Start the server:

       RETALK_SERVER_PORT=8766 RETALK_SERVER_AUDIENCE=https://retalk.example.com retalk-server

   Clients use `https://retalk.example.com`.

## Stop / delete
- Stop both processes: stop `retalk-server` and the tunnel (`pkill -f cloudflared`).
- A quick tunnel leaves nothing behind. A named tunnel:
  `cloudflared tunnel delete <name>`, then remove its CNAME from Cloudflare DNS.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall