Diagnose retrieved-but-unused agent skills through Ratel MCP
Compare skill retrievals with actual invocations through Ratel MCP, inspect the queries behind unused matches, and return an evidence-backed catalog diagnosis.
npx skills add agentskillexchange/skills --skill diagnose-retrieved-but-unused-agent-skills-ratel-mcp
Invoke this workflow when an operator needs to explain why an agent repeatedly retrieves a skill but never invokes it. Inputs are an existing self-hosted Ratel project, its recorded retrieval and invocation events, a project API key, and the exact runtime skill names. The output is a reviewable diagnosis linking unused matches to the user queries that retrieved them.
What this skill actually does
Connect an MCP client to POST <BASE_URL>/api/mcp with the project’s bearer key. Start with get_project_overview to confirm project identity and whether telemetry exists. Call get_improvement_signals to find retrieved-but-unused skills, then pass each exact skillName to list_search_queries_for_skill. Compare the returned queries with the intended skill purpose. Record mismatched intent, unknown catalog names, empty results, row limits and truncation as evidence gaps.
The scope boundary is read-only catalog diagnosis using those three MCP operations. Return suggested description changes for operator review; do not update skills, publish overrides, enable experimental evaluation features or claim that low invocation proves poor task quality. Generic trace dashboards cover latency and cost, while this workflow joins skill identity with retrieval intent and actual usage. An empty telemetry sample supports no quality conclusion. Query text may contain user data, so keep the evidence report within the operator’s approved project scope. The upstream worked example and operation definitions document this sequence.