DiPeO Backend Router

VerifiedCaution

This skill handles simple backend tasks for the DiPeO ecosystem, including FastAPI server, CLI tools, database queries, and MCP integration. Use for read-only tasks, small config tweaks, or documentation lookup; escalate complex multi-file changes to the dipeo-backend agent.

Sby Skills Guide Bot
DevelopmentIntermediate
806/2/2026
Claude Code
#backend#fastapi#cli#mcp#database

Recommended for

Our review

Routes backend development tasks for the DiPeO ecosystem to either direct handling or agent escalation based on complexity.

Strengths

  • Quick triage between simple and complex tasks, saving time.
  • Integrated with doc-lookup scripts for precise context retrieval.
  • Clear escalation paths to other specialized agents (package-maintainer, codegen-pipeline).
  • Well-documented implementation patterns and troubleshooting guides.

Limitations

  • Limited to simple changes (<20 lines, 1-2 files) – complex tasks must be escalated.
  • Requires the user to articulate the task clearly for correct routing.
  • Only covers the DiPeO backend ecosystem (server, CLI, database, MCP).
When to use it

Use this skill when working on the DiPeO backend, whether for reading code, tweaking configs, or performing simple modifications.

When not to use it

Avoid this skill if your task involves frontend, cross-cutting architecture, or complex multi-file changes beyond its scope.

Security analysis

Caution
Quality score85/100

The skill itself is a router that does not contain destructive payloads, but it allows Bash execution and delegates to more powerful agents. The potential for misuse through complex tasks or chained calls warrants caution.

Findings
  • Includes Bash as an allowed tool, which could be used to execute arbitrary commands if task handling is not properly constrained.
  • Escalation to dipeo-backend agent or other skills may introduce broader risks if those downstream components have fewer safeguards.

Examples

CLI help lookup
Show me the current CLI help for the dipeo command.
Database schema explanation
Explain the database schema from /dipeo/infrastructure/execution/state/persistence_manager.py.
Add environment variable to FastAPI server
Add a new environment variable 'LOG_LEVEL' to the FastAPI server configuration and make it configurable via .env file.

name: dipeo-backend description: 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. allowed-tools: Read, 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")
Related skills