cyrus-setup-endpoint — Claude Code skill: what it does, how to install
Configures a public webhook URL for your Cyrus agent instance using ngrok, Cloudflare Tunnel, or a custom domain. Required for incoming events from Linear, GitHub, and Slack.
npx skills add cyrusagents/cyrus --skill cyrus-setup-endpoint -a claude-codeWhat cyrus-setup-endpoint does
The skill configures public exposure for a local Cyrus server running on port 3456. It guides the user through three connection methods: a free static domain on ngrok, a persistent Cloudflare Tunnel, or an existing HTTPS endpoint. Once chosen, the public address is recorded as CYRUS_BASE_URL inside ~/.cyrus/.env.
Secret handling follows a strict security guardrail. The agent is explicitly forbidden from reading or writing ~/.cyrus/.env with standard file tools, keeping sensitive keys out of the conversation context. Instead, authtokens for ngrok and Cloudflare enter the environment exclusively via Bash stdin or clipboard pipes.
The procedure also sets CYRUS_SERVER_PORT=3456, LINEAR_DIRECT_WEBHOOKS=true, and CYRUS_HOST_EXTERNAL=true if they are missing. These environment flags enable direct webhook signature verification for self-hosted instances. Without the tunnel process running in a separate terminal, Cyrus will not receive incoming notifications.
What it helps with
- expose local Cyrus instance to receive Linear webhooks
- set up persistent ngrok static domain configuration
- configure Cloudflare Tunnel without leaking authtokens into context
- enable direct webhook signature validation for GitHub and Slack
Example prompts for the agent
- Configure Cyrus webhook endpoint using ngrok
- Set up a Cloudflare Tunnel for Cyrus webhooks
- Add my custom HTTPS domain to CYRUS_BASE_URL
How to install cyrus-setup-endpoint
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-endpoint -a claude-code2Manually: put the files in place
~/.claude/skills/cyrus-setup-endpoint/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cyrus-setup-endpoint/
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-endpoint -a codex2Manually: put the files in place
.agents/skills/cyrus-setup-endpoint/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-endpoint -a cursor2Manually: put the files in place
.cursor/skills/cyrus-setup-endpoint/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cyrusagents/cyrus cyrus-setup-endpoint2Manually: put the files in place
.github/skills/cyrus-setup-endpoint/SKILL.md1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-endpoint -a gemini-cli2Platform CLI
gemini skills install https://github.com/cyrusagents/cyrus --path skills/cyrus-setup-endpointManually: put the files in place
.devin/skills/cyrus-setup-endpoint/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-endpoint -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cyrus-setup-endpoint
How to install cyrus-setup-endpoint in Claude Code?
Run npx skills add cyrusagents/cyrus --skill cyrus-setup-endpoint -a claude-code. Alternatively, add the skill file directly into ~/.claude/skills/cyrus-setup-endpoint/SKILL.md.
What does cyrus-setup-endpoint do?
It configures a public HTTPS URL for Cyrus using ngrok, Cloudflare Tunnel, or a custom domain. It writes CYRUS_BASE_URL and port 3456 to ~/.cyrus/.env so external integrations can deliver webhooks.
How does this skill prevent token leaks?
The skill instructs the agent never to read ~/.cyrus/.env into chat context. Secrets such as ngrok authtokens or Cloudflare tokens are piped directly from clipboard or hidden shell prompts via Bash commands.
Source text
SKILL.md · Apache-2.0
---
name: cyrus-setup-endpoint
description: Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
---
**CRITICAL: Never use `Read`, `Edit`, or `Write` tools on `~/.cyrus/.env` or any file inside `~/.cyrus/`. Use only `Bash` commands (`grep`, `printf >>`, etc.) to interact with env files — secrets must never be read into the conversation context.**
# Setup Endpoint
Configures a public URL so Linear (and other integrations) can send webhooks to your Cyrus instance.
## Step 1: Check Existing Configuration
```bash
grep -E '^CYRUS_BASE_URL=' ~/.cyrus/.env 2>/dev/null
```
If `CYRUS_BASE_URL` is already set, inform the user:
> Webhook endpoint already configured: `<value>`
> To reconfigure, remove `CYRUS_BASE_URL` from `~/.cyrus/.env` and re-run this skill.
Skip to Step 4 (write port/webhooks if missing).
## Step 2: Choose Endpoint Method
Ask the user:
> **How will you expose Cyrus to the internet for webhooks?**
>
> 1. **ngrok** (recommended — every free account includes one static domain that persists across restarts)
> 2. **Cloudflare Tunnel** (permanent, requires Cloudflare account)
> 3. **Own URL** (you already have a public URL/domain)
**Important:** ngrok's free tier includes a permanent static domain — do NOT tell the user this is a paid feature or that URLs change on restart. Every free ngrok account gets one static domain at https://dashboard.ngrok.com/domains.
## Step 3: Configure Endpoint
### Option 1: ngrok
#### 3a. Check if ngrok is installed
```bash
which ngrok
```
If not installed, provide install instructions:
**macOS:**
```bash
brew install ngrok
```
**Linux:**
```bash
curl -sSL https://ngrok-agent.s3.amazonaws.com/ngrok-v3-stable-linux-amd64.tgz | sudo tar xvz -C /usr/local/bin
```
#### 3b. Guide ngrok domain setup
Instruct the user:
> ngrok provides a free static domain so your URL doesn't change between restarts.
>
> 1. Sign up or log in at https://dashboard.ngrok.com
> 2. Go to https://dashboard.ngrok.com/domains
> 3. Copy your free static domain (e.g., `your-name-here.ngrok-free.app`)
> 4. Go to https://dashboard.ngrok.com/get-started/your-authtoken and copy your authtoken
Ask the user to provide:
- Their ngrok domain
- Their ngrok authtoken
**CRITICAL: The authtoken is a secret. Use clipboard-to-file commands.**
#### 3c. Write ngrok configuration
Write the ngrok config so it can be started with `ngrok start cyrus`:
```bash
mkdir -p ~/.config/ngrok
```
Then write `~/.config/ngrok/ngrok.yml` (merge with existing if present):
```yaml
version: 3
agent:
authtoken: <token>
endpoints:
- name: cyrus
url: <domain>
upstream:
url: 3456
```
For the authtoken, use a clipboard-to-file approach:
**macOS:**
```bash
# User copies authtoken, then runs:
NGROK_TOKEN=$(pbpaste) && cat > ~/.config/ngrok/ngrok.yml << EOF
version: 3
agent:
authtoken: $NGROK_TOKEN
endpoints:
- name: cyrus
url: <domain>
upstream:
url: 3456
EOF
```
**Universal fallback:**
```bash
read -s -p "Paste your ngrok authtoken: " NGROK_TOKEN && cat > ~/.config/ngrok/ngrok.yml << EOF
version: 3
agent:
authtoken: $NGROK_TOKEN
endpoints:
- name: cyrus
url: <domain>
upstream:
url: 3456
EOF
echo " ✓ Saved"
```
#### 3d. Write CYRUS_BASE_URL
```bash
printf 'CYRUS_BASE_URL=https://%s\n' "<domain>" >> ~/.cyrus/.env
```
Where `<domain>` is the ngrok domain the user provided (e.g., `your-name-here.ngrok-free.app`).
Inform the user:
> To start ngrok, run: `ngrok start cyrus`
> Run this in a separate terminal before starting Cyrus.
### Option 2: Cloudflare Tunnel
Ask the user for:
- Their Cloudflare Tunnel token
- Their tunnel hostname (e.g., `cyrus.yourdomain.com`)
**Token is a secret — use clipboard-to-env:**
**macOS:**
```bash
printf 'CLOUDFLARE_TOKEN=%s\n' "$(pbpaste)" >> ~/.cyrus/.env
```
**Universal fallback:**
```bash
read -s -p "Paste your Cloudflare token: " val && printf 'CLOUDFLARE_TOKEN=%s\n' "$val" >> ~/.cyrus/.env && echo " ✓ Saved"
```
Then write the base URL (not a secret — agent can write directly):
```bash
printf 'CYRUS_BASE_URL=https://<hostname>\n' >> ~/.cyrus/.env
```
### Option 3: Own URL
Ask the user for their URL. Validate it starts with `https://`.
```bash
printf 'CYRUS_BASE_URL=%s\n' "<url>" >> ~/.cyrus/.env
```
## Step 4: Write Common Config
Ensure these are present in `~/.cyrus/.env` (add only if missing):
```bash
grep -q '^CYRUS_SERVER_PORT=' ~/.cyrus/.env 2>/dev/null || printf 'CYRUS_SERVER_PORT=3456\n' >> ~/.cyrus/.env
grep -q '^LINEAR_DIRECT_WEBHOOKS=' ~/.cyrus/.env 2>/dev/null || printf 'LINEAR_DIRECT_WEBHOOKS=true\n' >> ~/.cyrus/.env
grep -q '^CYRUS_HOST_EXTERNAL=' ~/.cyrus/.env 2>/dev/null || printf 'CYRUS_HOST_EXTERNAL=true\n' >> ~/.cyrus/.env
```
`LINEAR_DIRECT_WEBHOOKS=true` enables direct Linear webhook signature verification. `CYRUS_HOST_EXTERNAL=true` enables direct Slack and GitHub webhook signature verification. Both are required for self-hosted setups where webhooks come directly from the services (not forwarded through CYHOST).
## Completion
> ✓ Webhook endpoint configured: `<CYRUS_BASE_URL>`
> ✓ Server port: 3456
> ✓ Direct webhooks: enabled
© cyrusagents · Apache-2.0 · cyrusagents/cyrus