Automated summary
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).
Use this skill when working on the DiPeO backend, whether for reading code, tweaking configs, or performing simple modifications.
Avoid this skill if your task involves frontend, cross-cutting architecture, or complex multi-file changes beyond its scope.
Security analysis
CautionThe 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.
- •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
Show me the current CLI help for the dipeo command.Explain the database schema from /dipeo/infrastructure/execution/state/persistence_manager.py.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 guidedocs/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
- Assess task complexity: Simple (handle) vs. complex (escalate)
- If simple: Load relevant section via
Skill(doc-lookup) - Execute: Make changes or provide answer
- If complex: Escalate with
Task(dipeo-backend, "task details")
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/dipeo-backend-router-mm5t89je/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/dipeo-backend-router-mm5t89je' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/dipeo-backend-router-mm5t89je/download' --output '.skill-downloads/dipeo-backend-router-mm5t89je/SKILL.md.part' && mv '.skill-downloads/dipeo-backend-router-mm5t89je/SKILL.md.part' '.skill-downloads/dipeo-backend-router-mm5t89je/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/dipeo-backend-router-mm5t89je/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.