ntk

Route user requests to adaptive multi-agent execution depths with selective context compression.

35|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/kobolingfeng/ntk --skill ntk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ntk
Source: https://github.com/kobolingfeng/ntk/tree/main
Command: npx skills add https://github.com/kobolingfeng/ntk --skill ntk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NTK solves the problem of excessive LLM context and cost by routing each request to the minimum-depth multi-agent pipeline needed for the task’s complexity, while compressing and selectively sharing information across agents.

Core Features & Use Cases

  • Adaptive complexity routing: Automatically selects the execution depth (direct → light → standard → full) to avoid over-processing simple tasks.
  • Need-to-know information sharing: Reduces token waste by only providing each agent the minimal context it needs, rather than broadcasting full history.
  • Information compression with backtracking (Tee): Compresses gathered information and can recover original text if verification fails, improving reliability without always paying full-context costs.
  • MCP-first integration: Exposes capabilities as an MCP server so you can call NTK from MCP-compatible AI clients (VS Code Copilot, Claude Desktop, OpenClaw, etc.).
  • Dual-model cost isolation: Uses a strong model only for the highest-depth planning stage, while low-depth execution relies on a cheaper model tier.

Use case: When you ask for a simple function or translation, NTK stays in direct mode; when you ask for architecture design, it escalates to full mode with planning, verification, and compressed research steps.

Quick Start

Install NTK, create/edit a .env file with your OpenAI-compatible API endpoint credentials, then start the MCP server and call ntk_run from your MCP client.

Frequently Asked Questions about ntk

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

FAQPage Schema
How do I reduce LLM token costs when running multi-agent pipelines for code generation?

Multi-agent pipelines reduce LLM token costs by applying adaptive complexity routing to select the minimum execution depth needed. This prevents over-processing simple code generation tasks by sharing only need-to-know context between agents instead of full history.

Can I integrate multi-agent execution with an MCP server in VS Code Copilot or Claude Desktop?

Yes, you can integrate multi-agent execution with an MCP server in VS Code Copilot or Claude Desktop. The system exposes adaptive routing capabilities as an MCP server, allowing you to call execution directly from any MCP-compatible AI client.

What is adaptive complexity routing for LLM tasks and how does it work?

Adaptive complexity routing for LLM tasks automatically selects execution depth—direct, light, standard, or full—based on request complexity. It escalates simple requests to full mode with planning and verification only when needed, avoiding unnecessary token usage for basic queries.

How do I set up dual-model isolation to optimize LLM costs across planner and executor agents?

To set up dual-model isolation for LLM cost optimization, configure a strong model exclusively for the highest-depth planning stage, while delegating low-depth execution to a cheaper model tier. You establish this by providing OpenAI-compatible API endpoint credentials in your environment setup.

Does information compression with backtracking help prevent hallucinations in complex system architecture design?

Information compression with backtracking helps prevent hallucinations in system architecture design by compressing gathered information and recovering original text if verification fails. This improves reliability without always paying full-context token costs during multi-stage pipelines.

What are the limitations of using need-to-know context sharing for multi-agent log comprehension?

A limitation of need-to-know context sharing for multi-agent log comprehension is that agents receive only minimal context rather than full history. If selective compression removes critical details, tee recovery backtracking is required to restore original text for accurate verification.