CtrlK
BlogDocsLog inGet started
Tessl Logo

baume-code-correlator

This skill should be used when the user asks "where is this API endpoint implemented", "find the code for this route", "which file handles this endpoint", "map API findings to code", or needs to correlate OpenAPI spec paths with source code locations. Also use when creating fix plans for code-first API projects (NestJS, Fastify, Express) after running baume-review, or when user mentions "find my NestJS controller", "locate Fastify route handler", "Express route definition".

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and actionable with a clear seven-step correlation workflow, concrete framework detection, and useful output schemas. Its main weaknesses are a missing validation checkpoint for the batch correlation operation (capping workflow clarity) and a referenced diff-templates.md file that is absent from the bundle.

Suggestions

Add an explicit validation/verification step before Step 7 (e.g., confirm each codeLocation's confidence and re-check unresolved 'notFound' operations before writing the correlation output), since this is a batch operation.

Resolve the [diff-templates.md](diff-templates.md) reference: either add the file to a references/ bundle or remove the link and inline only the essential templates.

De-duplicate the baume-correlate description between the 'Preferred Approach' section and the 'MCP Tools Reference' section to tighten token usage.

DimensionReasoningScore

Conciseness

The body is largely lean and action-oriented, but the baume-correlate tool is described twice (in 'Preferred Approach' and again in 'MCP Tools Reference'), a minor redundancy that could be trimmed; it stays above the 'mostly efficient but includes unnecessary explanation' anchor at 3.

4 / 5

Actionability

Provides concrete framework-detection rules, agent-spawn templates, a fix-type-to-diff table, and full JSON output schemas, but several blocks use placeholders ({review-id-from-baume-review}, {absolute-path-to-project}) rather than copy-paste-ready commands, leaving minor gaps versus fully executable at 5.

4 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced, but this is a batch operation (correlating all findings, spawning up to 5 agents) with no explicit validation/verification checkpoint before writing output, so the batch-operations cap of 3 applies even though the sequence alone would rate higher.

3 / 5

Progressive Disclosure

Good section structure with clearly signaled one-level-deep references (e.g. [diff-templates.md](diff-templates.md)), but that referenced file is not present in any bundle directory, a minor organization gap that keeps it below the clean-navigation anchor at 5.

4 / 5

Total

15

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete capabilities, provides rich natural trigger phrases including framework synonyms, and explicitly covers both what the skill does and when to use it with minimal conflict risk. Minor specificity gaps (no file extensions or output artifact naming) keep it just short of a perfect specificity score.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('correlate OpenAPI spec paths with source code locations', 'map API findings to code', 'creating fix plans for code-first API projects') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the comprehensive list at 5.

4 / 5

Completeness

Explicitly answers both 'what' (correlate/map API findings to code, create fix plans) and 'when' via a clear 'Use when...' clause with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say ('where is this API endpoint implemented', 'find the code for this route', 'which file handles this endpoint') plus framework synonyms (NestJS, Fastify, Express), matching the comprehensive-coverage anchor; it does not fit below since common variations are well covered.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (correlating Baume review findings to source code in code-first API projects) with framework-specific triggers, giving minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
getlarge/claude-api-care-plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.