test-backend-router

Routes queries to retrieve targeted backend documentation sections on demand.

12|2|Updated May 29, 2025
One-click install
npx skills add https://github.com/sorryhyun/DiPeO --skill test-backend-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-backend-router
Source: https://github.com/sorryhyun/DiPeO/tree/main/.claude/skills/test-backend-router
Command: npx skills add https://github.com/sorryhyun/DiPeO --skill test-backend-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of high token usage in AI agents by demonstrating a "thin router" pattern. It proves that documentation can be loaded on-demand, significantly reducing context window size and processing costs compared to automatically injecting full documentation.

Core Features & Use Cases

  • Thin Router Pattern: Provides a proof-of-concept for routing tasks to either the skill itself (for simple, focused tasks) or a full agent (for complex, multi-step work), optimizing resource allocation.
  • On-Demand Documentation: Utilizes doc-lookup to retrieve only the necessary documentation sections for CLI commands, FastAPI server, database, and MCP integration, avoiding large context windows and irrelevant information.
  • Token Efficiency Analysis: Explicitly highlights the substantial token savings (up to 90% reduction) achieved by using this progressive disclosure model compared to traditional automatic documentation injection.
  • Use Case: If you need to understand "what columns are in the executions table," this skill demonstrates how to use doc-lookup to retrieve just that specific database schema section, rather than loading the entire backend documentation, saving tokens and processing time.

Quick Start

Example: Understanding CLI Flags

User request: "How do I add a --json flag to dipeo run?"

Router workflow:

1. Assess: Simple task, need CLI context

2. Load doc-lookup for CLI commands section:

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

Frequently Asked Questions about test-backend-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How can I reduce token usage when loading backend documentation into an AI agent?

Token usage drops dramatically—up to 90%—by loading documentation on-demand instead of injecting full docs automatically. This skill demonstrates a thin router pattern that retrieves only relevant sections through targeted doc-lookup queries, cutting context window size and processing costs.

How do I route simple backend tasks without triggering a full agent workflow?

Use a thin router to assess task complexity and direct simple read-only work—CLI help lookups, schema review, config inspection—directly to a lightweight handler, while escalating multi-file or complex tasks to a full agent, optimizing resource allocation.

What's the best way to find specific database schema information without loading entire documentation?

Use doc-lookup with targeted section queries—for example, query "executions table columns"—to retrieve only the relevant database schema fragment, avoiding irrelevant content and reducing tokens consumed during lookups.

Can I apply on-demand documentation loading to CLI commands and server configuration?

Yes. This skill routes queries to doc-lookup sections covering CLI commands, FastAPI server config, database schema, and MCP tool signatures, retrieving only the documentation anchors needed for each specific question.

When should I use progressive disclosure documentation instead of pre-loading all backend docs?

Progressive disclosure fits workflows with lightweight decision needs and frequent doc-lookup tasks where token efficiency matters. Pre-load only when you need continuous access to broad documentation; otherwise, route queries to specific sections on demand.