check-compiler-errors

Run compile and type-check commands and report failures

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cursor-team-kit/skills/check-compiler-errors/SKILL.md

Quality

Content

71%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 concise, well-structured, and has a sensible feedback loop, but it stays at a high level of abstraction without concrete commands or examples. Providing the actual compile/type-check invocation patterns would materially improve actionability.

Suggestions

Add concrete example commands for running compile and type-check (e.g. specific build/lint/tsc invocations) so Claude can act immediately.

Insert an explicit validation checkpoint between fixing issues and re-running checks (e.g. confirm the edited file compiles in isolation first).

Give one or two example error-summary formats to make the "Summarize errors by file and type" step concrete.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Steps like "Run the repo's compile and type-check commands" and "Fix the highest-confidence issues first" are high-level hints with no concrete commands or examples, so execution details are missing.	2 / 5
Workflow Clarity	The four-step sequence is clear and includes a re-run feedback loop ("Re-run checks until clean or blocked"), but explicit validation checkpoints between fix and re-run are only implicit.	4 / 5
Progressive Disclosure	Under 50 lines with clean Trigger/Workflow/Output sections and no need for external references, matching the simple-skill exception for a 5.	5 / 5
	Total	16 / 20 Passed

Description

53%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 states a clear capability (run compile/type-check commands and report failures) in third person and with relevant trigger terms, but it omits any explicit "Use when..." guidance for when Claude should invoke it. Adding a trigger clause would lift completeness and distinctiveness.

Suggestions

Add a 'Use when compile or type-check failures are blocking local validation or CI' clause to satisfy the 'when' half of completeness.

Include natural synonyms such as 'build errors' and 'type errors' to broaden trigger-term coverage.

Tighten the what/when pairing so the description explicitly distinguishes this skill from generic build or lint skills.

Dimension	Reasoning	Score
Specificity	Names the domain (compile/type-check) and two concrete actions ("Run compile and type-check commands" and "report failures"), but coverage is not comprehensive enough for a 4.	3 / 5
Completeness	The "what" is clear (run compile/type-check commands, report failures) but there is no "Use when..." or equivalent trigger clause, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"compile", "type-check", and "failures" are natural terms a user would say, but synonyms (e.g. "build") and file extensions are missing, so it stops at 3.	3 / 5
Distinctiveness Conflict Risk	The compile/type-check niche is mostly distinct with only minor overlap risk against generic build/lint skills; not quite a 5 because it lacks explicit distinguishing trigger phrases.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Path: cursor-team-kit/skills/check-compiler-errors/SKILL.md
Commit: 51a96e0

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.