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.
Best use case
dipeo-backend is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using dipeo-backend should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/dipeo-backend/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How dipeo-backend Compares
| Feature / Agent | dipeo-backend | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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**: ```bash 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
test-backend-router
Test implementation of thin router skill for DiPeO backend. Provides decision criteria and documentation anchors for FastAPI server, CLI (dipeo run/results/metrics/compile/export), SQLite schema, and MCP integration in apps/server/. Use when task mentions CLI commands, server endpoints, database queries, or MCP tools.
dipeo-package-maintainer
Router skill for DiPeO runtime Python code (execution handlers, service architecture, domain models, LLM infrastructure). Use when task mentions node handlers, EventBus, ServiceRegistry, Envelope pattern, or domain logic. For simple tasks, handle directly; for complex work, escalate to dipeo-package-maintainer agent.
dipeo-frontend-dev
Router skill for DiPeO frontend (React, visual editor, GraphQL integration, TypeScript types). Use when task mentions React components, diagram editor, GraphQL hooks, or type errors. For simple tasks, handle directly; for complex work, escalate to dipeo-frontend-dev agent.
dipeo-codegen-pipeline
Router skill for DiPeO code generation pipeline (TypeScript specs → IR → Python/GraphQL). Use when task mentions TypeScript models, IR builders, generated code diagnosis, or codegen workflow. For simple tasks, handle directly; for complex work, escalate to dipeo-codegen-pipeline agent.
todo-manage
Manage and organize TODO.md at project root - plan features, track progress, mark tasks complete, and clean up completed items. Use when planning tasks, organizing work, reviewing priorities, or managing the project TODO list. Access via /dipeotodos command.
separate-monolithic-python
Break large Python files (>500 LOC) into smaller, well-organized modules with proper package structure. Use when a Python file is too large, monolithic, or needs refactoring. Triggered by requests mentioning "too large", "separate", "split", "break up", or "refactor" for Python files.
maintain-docs
Update and maintain documentation to reflect current implementation after code changes, refactoring, or new features. Remove temporal language, verify accuracy against code, and keep docs current. Use when updating docs, syncing documentation, removing outdated info, or after implementing features.
import-refactor
Update all import statements, module references, string paths, and config references after moving or renaming files and modules. Handles Python, TypeScript, and JavaScript imports. Use when moving files, renaming modules, restructuring directories, or consolidating code.
skill-generator
Create new Claude Code skills with proper structure and best practices. Use when the user wants to create a new skill, extend Claude's capabilities, or needs help structuring a SKILL.md file.
doc-lookup
Locate and retrieve specific documentation sections from DiPeO's docs/ by heading anchors or keywords. Returns minimal, targeted excerpts instead of full files. Use when you need precise documentation context without loading entire guides.
clean-comments
Remove unnecessary, redundant, or obvious code comments while preserving valuable explanations. Use when cleaning up comments, removing verbose documentation, simplifying inline comments, or preparing code for review.
backend-development
Backend API design, database architecture, microservices patterns, and