dipeo-backend

Router skill for DiPeO backend ecosystem (server/ and cli/): FastAPI server, CLI tools, database, MCP integration. Use when task mentions CLI commands, server endpoints, database queries, or MCP tools. For simple tasks, handle directly; for complex work, escalate to dipeo-backend agent.

⭐13stars🔀2forks📁View on GitHub🕐Updated Dec 31, 2025⬇️3downloads

When & Why to Use This Skill

The DiPeO Backend Router is a specialized Claude skill designed to streamline development within the DiPeO backend ecosystem, covering FastAPI servers, CLI tools, and database management. It acts as an intelligent orchestrator that handles lightweight tasks—such as code reviews, documentation lookups, and minor configuration tweaks—directly, while automatically escalating complex architectural changes or multi-file features to the dedicated dipeo-backend agent. By integrating Model Context Protocol (MCP) support and providing structured access to backend implementation patterns, it optimizes the workflow for developers managing complex server-side infrastructures.

Use Cases

  • Directly debugging and patching FastAPI server endpoints or CLI tool configurations for small-scale fixes (<20 lines).
  • Performing read-only tasks such as inspecting database schemas, reviewing environment variables, and analyzing system logs.
  • Managing and troubleshooting Model Context Protocol (MCP) integrations, including setup and connection with external AI platforms.
  • Orchestrating backend development workflows by deciding whether to execute a task immediately or escalate to a specialized agent based on task complexity.
  • Quickly retrieving technical documentation and implementation patterns for CLI commands and database persistence managers.
namedipeo-backend
descriptionRouter skill for DiPeO backend ecosystem (server/ and cli/): FastAPI server, CLI tools, database, MCP integration. Use when task mentions CLI commands, server endpoints, database queries, or MCP tools. For simple tasks, handle directly; for complex work, escalate to dipeo-backend agent.
allowed-toolsRead, Grep, Glob, Bash, Skill

DiPeO Backend Router

Domain: Backend ecosystem including FastAPI server (server/), CLI tools (cli/), message store, and MCP integration. Database schema initialization is in /dipeo/infrastructure/execution/state/persistence_manager.py (package-maintainer domain).

Quick Decision: Skill or Agent?

✅ Handle Directly (This Skill)

  • Simple changes: <20 lines, 1-2 files
  • Read-only tasks: Understanding code, reviewing configs, debugging logs
  • Documentation lookup: CLI help, API signatures, database schema
  • Small config tweaks: Environment variables, command flags

❌ Escalate to Agent

  • Complex features: Multi-file changes, new CLI commands, database migrations
  • Architecture changes: New API endpoints, MCP tool implementation
  • Cross-cutting concerns: Affects CLI + database + execution engine
  • Uncertain scope: Not sure how many files will change

Agent: Task(dipeo-backend, "your detailed task description")

Documentation Sections (Load On-Demand)

Use Skill(doc-lookup) with these anchors when you need detailed context:

Core Responsibilities:

  • docs/agents/backend-development.md#core-responsibilities - CLI, FastAPI server, database, MCP server

Implementation Patterns:

  • docs/agents/backend-development.md#common-patterns - CLI, background execution, database, MCP patterns

Troubleshooting:

  • docs/agents/backend-development.md#troubleshooting - Server, CLI, database, MCP issues

MCP Integration:

  • docs/features/mcp-server-integration.md#quick-start - Setup and usage guide
  • docs/features/chatgpt-mcp-integration.md#quick-start - ChatGPT connection

Example doc-lookup call:

python .claude/skills/doc-lookup/scripts/section_search.py \
  --query "cli-commands" \
  --paths docs/agents/backend-development.md \
  --top 1

Escalation to Other Agents

To dipeo-package-maintainer: Execution handlers, service architecture, domain models, LLM infrastructure To dipeo-codegen-pipeline: GraphQL schema changes, generated type issues, TypeScript specs

Typical Workflow

  1. Assess task complexity: Simple (handle) vs. complex (escalate)
  2. If simple: Load relevant section via Skill(doc-lookup)
  3. Execute: Make changes or provide answer
  4. If complex: Escalate with Task(dipeo-backend, "task details")