How do I install the Nexus skill?

Run npx skillmds add majiayu000/nexus in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nexus safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nexus?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nexus free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nexus by majiayu000 — Agent Skill

Name: Nexus
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Nexus Agent

Nexus is the conversational personal intelligence (PI) agent — a single agentic loop using the Strands Agent SDK, orchestrated by Temporal.

Architecture

UI (WebSocket) → Nexus Gateway (FastAPI) → Temporal Signal
    → Orchestrator Workflow → run_agent_turn Activity
        → Strands Agent (think → act → observe loop)
            → Core Tools (read/write/edit/bash)
            → MCP Tools (memory, skills, fetch)
            → Custom Tools (web_search)
        → Response via Redis PubSub → Gateway → UI

Key Differences from Syndicates

Aspect	Syndicates	Nexus
Pattern	Multi-agent orchestration	Single agentic loop
SDK	Custom framework agents	Strands Agent SDK
Config	`kubani.framework.config` (YAML)	Environment variables
Workflow	Multiple specialized workflows	Entity workflow pattern
Interaction	Event-driven, autonomous	Conversational, user-initiated

Components

Component	Location	Purpose
Orchestrator	`kubani/nexus/orchestrator/`	Temporal worker, activities, workflow
Gateway	`kubani/nexus/gateway/`	FastAPI, WebSocket, Discord bridge
Tools	`kubani/nexus/orchestrator/tools/`	Core and extra tool definitions

Entity Workflow Pattern

The orchestrator uses a long-running Temporal entity workflow:

Receives messages via Temporal signals
Processes each message in a run_agent_turn activity
Uses continue-as-new after 100 iterations to prevent history growth
Maintains conversation state across turns

Key Files

activities.py — run_agent_turn(): Creates Strands Agent, builds system prompt, executes agent loop
workflow.py — Entity workflow with signal handling and continue-as-new
worker.py — Temporal worker entry point
tools/core.py — Core tools (file ops, bash, etc.)
tools/extra_tools.py — MCP client tools (fetch, web_search)

Local Development

# Setup
cd kubani/nexus/orchestrator
cp ../../nexus/.env.example .env  # Edit with credentials

# Run worker locally
source .env && python -m kubani.nexus.orchestrator.worker

# Run gateway (separate terminal)
cd kubani/nexus/gateway
source .env && python -m kubani.nexus.gateway.main

See kubani/nexus/.env.example for all required environment variables.

Configuration

Nexus uses direct environment variables (NOT the kubani config system):

Variable	Purpose
`TEMPORAL_HOST`	Temporal server address
`TEMPORAL_NAMESPACE`	Temporal namespace (usually `nexus`)
`NEXUS_DATABASE_URL`	PostgreSQL connection string
`REDIS_URL`	Redis for pub/sub and caching
`LLM_API_URL`	vLLM API endpoint
`QDRANT_URL`	Vector database
`MCP_MEMORY_URL`	Memory MCP server
`MCP_SKILLS_URL`	Skills MCP server

Building & Deploying

# Build container
earthly +nexus-orchestrator

# Smoke test
docker run --rm --env-file .env <image> python -c "from kubani.nexus.orchestrator.worker import *; print('OK')"

# Deploy via GitOps
# Update image tag in infrastructure/gitops/apps/nexus/orchestrator-deployment.yaml
# Commit and push (Flux auto-deploys)

Testing Changes

Prompt changes: Edit activities.py system prompt, run worker locally, send test message via UI
Tool changes: Edit tools, run worker locally, test tool invocation
Workflow changes: Edit workflow.py, restart worker, verify signal handling
Always follow the 4-stage workflow: local test → integration → container build → deploy

---name: nexusdescription: Nexus conversational PI agent architecture, development, and deployment. Use when working on the Nexus orchestrator, gateway, or tools.--- # Nexus Agent Nexus is the conversational personal intelligence (PI) agent — a single agentic loop using the Strands Agent SDK, orchestrated by Temporal. ## Architecture ``` UI (WebSocket) → Nexus Gateway (FastAPI) → Temporal Signal → Orchestrator Workflow → run_agent_turn Activity → Strands Agent (think → act → observe loop) → Core Tools (read/write/edit/bash) → MCP Tools (memory, skills, fetch) → Custom Tools (web_search) → Response via Redis PubSub → Gateway → UI ``` ### Key Differences from Syndicates | Aspect | Syndicates | Nexus | |--------|-----------|-------| | Pattern | Multi-agent orchestration | Single agentic loop | | SDK | Custom framework agents | Strands Agent SDK | | Config | `kubani.framework.config` (YAML) | Environment variables | | Workflow | Multiple specialized workflows | Entity workflow pattern | | Interaction | Event-driven, autonomous | Conversational, user-initiated | ## Components | Component | Location | Purpose | |-----------|----------|---------| | Orchestrator | `kubani/nexus/orchestrator/` | Temporal worker, activities, workflow | | Gateway | `kubani/nexus/gateway/` | FastAPI, WebSocket, Discord bridge | | Tools | `kubani/nexus/orchestrator/tools/` | Core and extra tool definitions | ### Entity Workflow Pattern The orchestrator uses a long-running Temporal entity workflow: - Receives messages via Temporal signals - Processes each message in a `run_agent_turn` activity - Uses `continue-as-new` after 100 iterations to prevent history growth - Maintains conversation state across turns ### Key Files - `activities.py` — `run_agent_turn()`: Creates Strands Agent, builds system prompt, executes agent loop - `workflow.py` — Entity workflow with signal handling and continue-as-new - `worker.py` — Temporal worker entry point - `tools/core.py` — Core tools (file ops, bash, etc.) - `tools/extra_tools.py` — MCP client tools (fetch, web_search) ## Local Development ```bash # Setup cd kubani/nexus/orchestrator cp ../../nexus/.env.example .env # Edit with credentials # Run worker locally source .env && python -m kubani.nexus.orchestrator.worker # Run gateway (separate terminal) cd kubani/nexus/gateway source .env && python -m kubani.nexus.gateway.main ``` See `kubani/nexus/.env.example` for all required environment variables. ## Configuration Nexus uses direct environment variables (NOT the kubani config system): | Variable | Purpose | |----------|---------| | `TEMPORAL_HOST` | Temporal server address | | `TEMPORAL_NAMESPACE` | Temporal namespace (usually `nexus`) | | `NEXUS_DATABASE_URL` | PostgreSQL connection string | | `REDIS_URL` | Redis for pub/sub and caching | | `LLM_API_URL` | vLLM API endpoint | | `QDRANT_URL` | Vector database | | `MCP_MEMORY_URL` | Memory MCP server | | `MCP_SKILLS_URL` | Skills MCP server | ## Building & Deploying ```bash # Build container earthly +nexus-orchestrator # Smoke test docker run --rm --env-file .env <image> python -c "from kubani.nexus.orchestrator.worker import *; print('OK')" # Deploy via GitOps # Update image tag in infrastructure/gitops/apps/nexus/orchestrator-deployment.yaml # Commit and push (Flux auto-deploys) ``` ## Testing Changes 1. **Prompt changes**: Edit `activities.py` system prompt, run worker locally, send test message via UI 2. **Tool changes**: Edit tools, run worker locally, test tool invocation 3. **Workflow changes**: Edit `workflow.py`, restart worker, verify signal handling 4. **Always follow the 4-stage workflow**: local test → integration → container build → deploy

Frequently asked questions