analyze-context-router

Analyzes memory retrieval logs to measure routing accuracy, token cost, and false negatives.

Updated May 3, 2026
One-click install
npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill analyze-context-router-spikelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-context-router
Source: https://github.com/spikelab/multiplai-cc-mktplace/tree/main/plugins/multiplai-dev/skills/analyze-context-router
Command: npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill analyze-context-router-spikelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a memory system routes user prompts to stored memory files, there is no built-in way to know whether the routing is accurate, whether relevant context is being missed, or whether retrieval is wasting tokens. This Skill audits the multiplai-context plugin's retrieval logs and turns them into measurable quality metrics. ## Core Features & Use Cases - Quantitative log analysis: Computes volume, routing rates, file distribution, token cost, dedup effectiveness, pre-filter rates, and error rates across daily context-router log files. - Qualitative sampling and false-negative detection: Grades sampled routing decisions as correct, over-broad, or wrong, and checks NONE-routed entries with personal keywords for missed retrievals. - Watermark-based delta tracking: Partitions pre/post-fix data using a watermark file so each report compares current metrics against the previous baseline. - Use Case: After deploying a routing fix to the context-router hook, run this Skill to verify that false negatives dropped and that retrieval size stayed under the 15K byte cap. ## Quick Start Ask the assistant to analyze memory retrieval quality and report how the memory loader has been performing since the last analysis.

Frequently Asked Questions about analyze-context-router

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

FAQPage Schema
How do I analyze memory retrieval logs for routing accuracy?

Run this Skill to parse the context-router-*.log files in your Claude config directory. It computes routing rates, grades sampled routing decisions as correct, over-broad, or wrong, and outputs a structured report with recommendations.

How to detect false negatives in memory retrieval routing?

The Skill samples NONE-routed log entries containing personal keywords such as names, relocation, or job search terms. Each is graded as a correct NONE or a false negative, directly measuring whether personal-context routing is working.

Does this Skill work without the multiplai-context plugin installed?

No. It requires the multiplai-context plugin because it analyzes that plugin's runtime artifacts: the context-router log files, the context-router.py hook, and the memory-catalog.json file. Without those logs there is nothing to analyze.

Why does the analysis warn about too few log events?

If fewer than 50 events exist since the last analysis watermark, the metrics are not statistically meaningful. The Skill warns you and offers to include pre-watermark data with a clear pre-fix and post-fix partition instead.

How does the Skill avoid loading huge log files into context?

It delegates heavy log parsing to a general-purpose agent that returns only aggregated metrics. Raw log content, which can exceed 100K, never enters the main conversation window.