CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/baume/skills/baume-code-correlator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

A concrete, well-sequenced correlation procedure with strong MCP call signatures and framework detection rules, weakened by duplicated MCP descriptions, placeholder-laden examples, a broken reference to a missing diff-templates.md, and no validation/feedback loop for its batch correlation operation.

Suggestions

Add a validation step to the workflow: after compiling extended findings, verify codeLocations against the source (e.g., confirm the snippet at file:line matches the operation) and re-run the locator or mark confidence 'low' for misses, addressing the batch-operation feedback-loop cap on workflow_clarity.

Ship the referenced diff-templates.md in references/ (or inline the per-fix-type diff templates) so the '...' placeholders in the ExtendedFinding and suggestedDiffs examples and the broken link are resolved.

Trim the MCP benefit bullets in 'Preferred Approach' and drop the duplicate baume-correlate/baume-review descriptions from 'MCP Tools Reference' (keep only the call signatures), tightening conciseness and removing padding.

DimensionReasoningScore

Conciseness

Mostly efficient procedural steps and concrete examples, but noticeably padded in places: the MCP tool's benefit bullets ('Uses MCP sampling for accurate code location', 'Batch processes all findings efficiently') are marketing-style filler, and baume-correlate is described twice (once in 'Preferred Approach', again in 'MCP Tools Reference'). Fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Concrete, mostly executable guidance throughout: exact MCP call signatures with parameter values, package.json-based framework detection rules, an agent-spawn prompt template, a full ExtendedFinding JSON schema, and a fix-type-to-diff table. Falls short of 5 because key examples contain placeholders ('"..."' in fix/specDiff fields, '{date}-{spec-name}' output names) and the diff templates that would complete them live in a referenced file that is not in the bundle.

4 / 5

Workflow Clarity

The 7-step sequence (gather inputs → extract operations → detect framework → locate code → compile → diff → output) is clearly ordered with inputs and outputs per step. However, this is a batch operation over all findings with no explicit validation or verification checkpoint (nothing verifies located file:line hits, handles low-confidence matches, or retries notFound operations), and the rubric caps batch workflows without validation at 3 — above 3 would require feedback loops like re-checking 'medium'/'low' confidence locations.

3 / 5

Progressive Disclosure

Section headers are clear and the File Locations table aids navigation, but the bundle contains no references/ directory, so the body's only content link, '[diff-templates.md](diff-templates.md)', is dangling and the deterministic-fix templates it promises are absent. Content that could live in separate files (the ~35-line ExtendedFinding JSON schema, the MCP tools reference for sibling tools) is inlined, matching 'some structure but could be better organized; references present but not clearly signaled'.

3 / 5

Total

13

/

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.

A strong description that explicitly covers what the skill does and when to use it, with rich natural trigger phrases including framework-specific synonyms and clear separation from related tools. Minor room to expand the what-side capability list beyond correlation and fix-plan creation.

DimensionReasoningScore

Specificity

Concrete actions are named: 'correlate OpenAPI spec paths with source code locations', 'creating fix plans for code-first API projects (NestJS, Fastify, Express)', 'map API findings to code'. Lists several specific actions with minor gaps — the what-side is compressed relative to the extensive trigger phrases, and voice stays third-person ('This skill should be used'), so no voice penalty. Not 5 because the capability coverage is thinner and more implied than the comprehensive multi-action exemplar.

4 / 5

Completeness

Explicitly answers what ('correlate OpenAPI spec paths with source code locations', 'creating fix plans for code-first API projects') and when ('This skill should be used when the user asks...' followed by concrete quoted trigger phrases and framework-specific variants). Clearly matches the both-what-and-when-with-concrete-trigger-phrases anchor; the 4 anchor's 'when could be more explicit' does not apply given the extensive quoted triggers.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say, including synonyms and framework variations: "where is this API endpoint implemented", "find the code for this route", "which file handles this endpoint", "find my NestJS controller", "locate Fastify route handler", "Express route definition", plus 'map API findings to code'. Matches the comprehensive-coverage-with-synonyms anchor exactly.

5 / 5

Distinctiveness Conflict Risk

Clear niche with minimal conflict risk: Baume review correlation, OpenAPI spec paths, and named frameworks (NestJS/Fastify/Express) plus tool-specific terms ('after running baume-review') make it highly distinguishable from generic code-search or API-review skills. Not 4 because the triggers are specific enough that overlap with a sibling 'baume-review' skill is explicitly disambiguated ('after running baume-review').

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.

Validation — 15 / 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

Path

plugins/baume/skills/baume-code-correlator/SKILL.md

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.