shuttles-mcp-strategy

star 0

Strategic guidelines for utilizing the Shuttles MCP ecosystem (radar-ast, debug-probe, doc-scribe, cargo-db). Focuses on token conservation, local hardware usage, and precise technical execution.

nqhuy44 By nqhuy44 schedule Updated 3/9/2026

name: Shuttles MCP Strategy description: Strategic guidelines for utilizing the Shuttles MCP ecosystem (radar-ast, debug-probe, doc-scribe, cargo-db). Focuses on token conservation, local hardware usage, and precise technical execution.

Shuttles MCP Strategy Guide

This skill directs the AI on how to interact with the Shuttles MCP ecosystem efficiently.

Core Directives

1. The "Structural First" Rule

Never read a file completely if it is larger than 100 lines. Use structural tools first:

  • Markdown: Use doc-scribe.get_markdown_toc to find relevant sections.
  • Python/Code: Use radar-ast.get_file_skeleton to map out class and function definitions.
  • Directories: Use radar-ast.get_dir_tree (max depth 2-3) to understand context.

2. The QA-Deck Mandate (NEW)

Mandatory use of qa-deck.run_test_compact for all testing. Native terminal execution for tests is PROHIBITED to save tokens.

Specialized Server Skills

For detailed instructions on each server, refer to their dedicated skills:

2. The "Token-Offload" Mandate [REQUIRES LOCAL GPU/Ollama]

Whenever a task requires a summary, explanation, or docstring generation, always prefer the *_local tools. This uses the local RTX 3060 to save Cloud AI input/output tokens.

  • radar-ast.summarize_logic_local
  • doc-scribe.summarize_doc_local
  • doc-scribe.generate_inline_docs
  • debug-probe.analyze_crash_local
  • qa-deck.diagnose_failure_local

3. The "Patch-Only" Protocol

For large configuration or documentation files, never perform a full-file rewrite.

  • Use doc-scribe.patch_doc_section to target specific headings.
  • If a Code Patch tool exists (e.g., in radar-ast), use it for specific line replacement.

4. The TOON (Token Optimized Output Notation) Protocol

Mandatory for all tabular or list-based data. When transmitting data to Gemini:

  • Never use verbose JSON objects for rows: [{"id": 1, "val": "A"}, {"id": 2, "val": "B"}].
  • Always use TOON format (Array of Arrays): [["id", "val"], [1, "A"], [2, "B"]].
  • Use compact separators (no spaces) to minimize token footprint.

Tool Selection Matrix

Objective Server Primary Tool Avoid
Exploring Project radar-ast get_dir_tree list_dir (recursive)
Reading Large File radar-ast get_file_skeleton view_file (full)
Updating Docs doc-scribe patch_doc_section write_to_file (rewrite)
DB Research cargo-db get_schema / find_join_path Manual SQL exploration
Running Tests qa-deck run_test_compact run_command / native test output
DB Research cargo-db get_schema / find_join_path Manual SQL exploration

When NOT to use MCP Tools

  • Small Files: If ls shows the file is small, view_file is faster.
  • Known Paths: Don't use get_dir_tree if you already have the file link in your workspace or history.
  • Static Documentation: If docs/ARCHITECTURE.md exists, read it before querying radar-ast.
Install via CLI
npx skills add https://github.com/nqhuy44/shuttles --skill shuttles-mcp-strategy
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator