Skip to content
Back to skills

Install Cortex

ASecurity

Use when installing or repairing Cortex; provisioning its server, configuring a client-only host, choosing syslog/MCP/REST auth or Google OAuth, enabling durable Compose, selecting Codex app-server LLM support, or verifying agent connectivity.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
ai-agentsgodockerdatabase

Works with

  • cli
  • mcp

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add dinglebear-ai/cortex --skill install-cortex --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Install Cortex?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Install Cortex
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dinglebear-ai-install-cortex/badge)](https://www.skillsdirectory.com/skills/dinglebear-ai-install-cortex)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: install-cortex
description: Use when installing or repairing Cortex; provisioning its server, configuring a client-only host, choosing syslog/MCP/REST auth or Google OAuth, enabling durable Compose, selecting Codex app-server LLM support, or verifying agent connectivity.
---

# Install Cortex

Configure one server or a client-only connection; let Cortex own setup.

## Rules

- Inspect role, Cortex/data, ports, Docker, disk/retention, sender networks, clients, and public URL.
- Server asks syslog bind/CIDRs, HTTP bind, separate MCP/REST credentials, OAuth, storage, LLM, and persistence. Syslog has no token auth. Client-only hosts start no receiver/database.
- OAuth requires public URL/Google credentials/admin email. Ask explicitly before retaining `CORTEX_TOKEN` with `CORTEX_AUTH_DISABLE_STATIC_TOKEN_WITH_OAUTH=false`.
- Existing proxy/Tailscale/Compose edits require current official docs, verified backup/checksum, exact changes, and explicit approval.

## Workflow

1. Follow [setup](references/setup.md): acquire/run canonical `install.sh` and let `cortex setup repair` own config.
2. Server: configure tokens/storage; keep HTTP loopback unless needed; restrict syslog with `CORTEX_ALLOWED_SOURCE_CIDRS` and network controls.
3. Start managed Compose and prove `restart: unless-stopped` persistence. Remote HTTPS keeps Cortex auth behind the proxy.
4. Optional `CORTEX_LLM=codex[/MODEL]` uses Codex app-server; verify Codex auth first.
5. Configure selected agent MCP clients, reload them, and prove read-only `status` from a fresh session. Run setup check/doctor/health and report paths/URLs/service state/evidence without secrets.

Files in this skill

  • SKILL.md1.6 KB
  • agents/openai.yaml243 B
  • references/setup.md1.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.