retrieval-system-audit

Audit and improve MCP server retrieval across live service operations and skills.

8|6|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/stellar-experimental/stellar-raven --skill retrieval-system-audit-stellar-experimental
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrieval-system-audit
Source: https://github.com/stellar-experimental/stellar-raven/tree/main/.agents/skills/retrieval-system-audit
Command: npx skills add https://github.com/stellar-experimental/stellar-raven --skill retrieval-system-audit-stellar-experimental

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Retrieval quality in an MCP server degrades silently when catalog descriptions, response shapes, search rankings, and golden evaluation answers drift from live service behavior. This Skill provides a disciplined, evidence-gated audit workflow so changes to the stellar-raven-codemode retrieval system are measured against real endpoint calls instead of intuition. ## Core Features & Use Cases - Surface Inventory: Builds a ledger of every exposed operation and skill, comparing the committed manifest, generated specification, adapters, live catalog, and fresh-client MCP descriptions. - Live Probing: Probes read-only operations with representative inputs, classifying responses as data, soft-empty, or error, and recording schema differences without storing secrets or raw bodies. - Experiment Gating: Requires pre-registered hypotheses, symmetric controls, cost caps, and independent adversarial review before any paid evaluation run or product change ships. - Use Case: An engineer suspects search ranking regressed after a catalog description edit. The Skill walks them through pinning a baseline, tracing retrieval decisions, running A/B evals with identical case identifiers, and shipping only changes that survive two unrelated targets. ## Quick Start Use the retrieval-system-audit skill to inventory every exposed operation, probe live response contracts, and pre-register an experiment for the suspected search ranking regression.

Frequently Asked Questions about retrieval-system-audit

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

FAQPage Schema
How do I audit MCP server search and retrieval quality?

Start by inventorying every exposed operation against the committed manifest, generated spec, and live catalog. Then probe read-only endpoints with representative inputs, trace search scoring and execute grounding, and map evaluation coverage before proposing any change.

How to run A/B evaluations for retrieval changes safely?

Pre-register one hypothesis per candidate with symmetric controls, identical case identifiers, runner code, and judge tuples. Require independent adversarial review before any paid run, enforce a hard cost cap, and reject candidates after any blocking regression.

Can the audit call paid or side-effecting service operations?

No. The audit explicitly forbids calling paid or side-effecting operations during inventory work. Probes are classified as read-only, paid, side-effecting, secret-bearing, or unsafe, and only safe read-only operations are called.

When should golden evaluation answers be changed?

Golden questions and answers change only through the dedicated golden-truth workflow, never as part of a product fix. Volatile or disputed claims must be triangulated with independent source classes before any golden update.

What evidence is required before shipping a retrieval improvement?

A shipped change needs reviewed correctness, causal evidence from controlled experiments, stable retrieval of required sources, complete cost accounting, and no security or exposure regression. Aggregate scores cannot override a blocking regression.