CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-at-the-boundary

How to find every sibling instance of a reported bug before fixing it. Use whenever a bug report names one file but the defect is a call pattern, hook, duplicated literal, or copy-pasted helper that plausibly exists in other files, apps, or templates.

68

Quality

85%

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

82%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 tight, highly actionable skill body with concrete executable search commands and a clear sequenced workflow. The main gaps are minor: motivational anecdotes that pad the token budget and the absence of an explicit fix-verification feedback loop for batch edits.

Suggestions

Trim or move the "Why this exists" anecdotal user quotes into a one-line rationale; they motivate but do not guide execution.

Add an explicit verification checkpoint after applying the batch fix (e.g., re-run the fingerprint search to confirm no in-scope hits remain, or confirm each edit still passes typecheck/tests).

State the validation step as a feedback loop (verify -> if misses remain, fix and re-verify) to strengthen the batch-operation workflow.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the "Why this exists" section's anecdotal user quotes are motivational padding that could be trimmed without losing actionable value.

4 / 5

Actionability

It provides copy-paste-ready `rg` commands with real flags and patterns, a concrete enumerated workflow, and a filled-in reporting template covering the common search cases.

5 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with an explicit enumerate-before-editing checkpoint ("write the list ... so step 5 is checkable") and ownership-boundary handling, but it lacks a fix-correctness feedback loop (validate -> fix -> retry) for the batch edit.

4 / 5

Progressive Disclosure

Sections are well-organized and self-contained with clearly signaled Related-Skills links; no external reference files are needed, though the inline anecdotal motivation is the kind of content that keeps it just below a perfectly split structure.

4 / 5

Total

17

/

20

Passed

Description

87%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 precise, well-constructed description that clearly states both the action and the triggering conditions, with strong distinctiveness. It is slightly below top on specificity and trigger-term breadth because it describes one core sweep action rather than a suite of distinct actions.

DimensionReasoningScore

Specificity

Names the core concrete action ("find every sibling instance of a reported bug before fixing it") and enumerates specific defect types (call pattern, hook, duplicated literal, copy-pasted helper), but is essentially one action with target elaboration rather than multiple distinct actions, so it sits below the comprehensive 5 anchor.

4 / 5

Completeness

It explicitly answers both what ("find every sibling instance of a reported bug before fixing it") and when ("Use whenever a bug report names one file but the defect is a call pattern, hook, duplicated literal, or copy-pasted helper"), with concrete trigger phrases matching the 5 anchor.

5 / 5

Trigger Term Quality

The "Use whenever a bug report names one file but the defect is a call pattern, hook, duplicated literal, or copy-pasted helper" clause combines natural user terms (bug report, fix) with developer jargon and location terms (files, apps, templates), giving good coverage just shy of the comprehensive synonym level.

4 / 5

Distinctiveness Conflict Risk

The cross-file bug-sweep niche is specific with distinct triggers (sibling instances of a patterned defect) and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
BuilderIO/agent-native
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.