← ClaudeAtlas

agentic-os-standalonelisted

Set up an agentic OS as a standalone Next.js web dashboard — wired to the Claude Agent SDK plus up to 7 live MCP integrations (Circle community, Fireflies meetings, YouTube/VidIQ, Unipile LinkedIn DMs, Apify Twitter/X, Reddit), per-profile views, a button-bar of actions, snapshot-style data refreshes, and an optional Railway deploy with HTTP basic auth and a persistent volume. A real web app — runs locally or live. Use when the user says "set up a standalone agentic OS", "build an MCP-powered web dashboard", "spin up my AI ops dashboard", "deploy an AI dashboard to Railway", "give me a web version of the dashboard", or asks to personalize a web dashboard previously created with this skill.
naveedharri/benai-skills · ★ 46 · AI & Automation · score 74
Install: claude install-skill naveedharri/benai-skills
# Agentic OS — Standalone web dashboard Packages a Next.js 14 dashboard wired to the Claude Agent SDK + up to 7 platform integrations, plus an optional Railway deployment path. The template ships as `references/standalone/template.tar.gz` (packed because the Next.js dynamic-route folders use `[name]`/`[id]` paths that some plugin installers reject — extract it before use, see Step 3) and contains no secrets. Substitutions and live credential probes are the skill's job. The dashboard's conceptual model: a per-profile dashboard, a button-bar of actions, and snapshot-style data refreshes — backed by JSON snapshots and deployable as a real web app. > Want a markdown-native dashboard inside an existing Obsidian vault with no server instead? That's the Obsidian route — use the `agentic-os-obsidian` skill. ## Audience The user is a **founder, operator, or marketer** — NOT a developer. Keep language plain. Never say "MCP", "snapshot prompt", "stdio transport", "TypeScript type" out loud. Say "platform", "data refresh", "your YouTube channel", "the dashboard's settings file". Internally you still operate on those technical concepts. The user just shouldn't have to read jargon. ## What you produce By the end the user has: 1. A new project folder at the path they chose, customized for their org and team. 2. Every integration they wanted connected AND probed (a real test call landed). 3. The dashboard running locally on http://localhost:3015, OR live on a Railway URL with HTTP b