check-compiler-errors

Run compile and type-check commands and report failures

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The content is a concise, well-structured simple skill with a clear feedback loop, but its actionability is held back by vagueness around how to locate and run the repo's compile/type-check commands.

Suggestions

Add concrete guidance for discovering the commands, e.g. check package.json scripts, Makefile, pyproject.toml, or CI config before running.

Optionally include one short example command invocation or a snippet showing how to group errors by file and category.

Clarify what "blocked" means in step 4 so the stopping condition is unambiguous (e.g., cannot resolve without changing dependencies or upstream code).

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept-explaining fluff and no padding; each section (Trigger, Workflow, Output) earns its place and assumes Claude's competence, matching the score-3 "lean and efficient" anchor.	3 / 3
Actionability	Steps instruct rather than merely describe, but "Run the repo's compile and type-check commands" gives no specifics on how to discover those commands and offers no examples, fitting score-2 "some concrete guidance but incomplete".	2 / 3
Workflow Clarity	The four-step sequence is clear and includes an explicit feedback loop ("Re-run checks until clean or blocked") with a termination condition, the score-3 marker for error-recovery loops.	3 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into clearly labeled sections, which per the simple-skills guideline lets progressive disclosure score 3 on well-organized sections alone.	3 / 3
	Total	11 / 12 Passed

Description

60%

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 concrete and names real actions, but it omits an explicit trigger/"Use when" clause and lacks common trigger-term variations, which limits its completeness and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when compile or type-check failures block local validation or CI."

Broaden trigger terms to natural variations users say: "compile errors", "build errors", "type errors", "lint", or "CI is red".

Sharpen distinctiveness by naming the triggering context (e.g. failing local validation or CI builds) so it does not collide with general test/lint skills.

Dimension	Reasoning	Score
Specificity	"Run compile and type-check commands and report failures" lists multiple concrete actions (compile, type-check, report), matching the score-3 anchor that rewards several specific actions rather than the score-2 "some actions" level.	3 / 3
Completeness	It clearly answers what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "compile", "type-check", and "failures" are natural, but common variations users say (build, compile errors, type errors, lint, CI) are missing, so it sits at the score-2 "some relevant keywords but missing common variations" level.	2 / 3
Distinctiveness Conflict Risk	The compile/type-check niche is somewhat specific but lacks a sharp explicit trigger and could overlap with run-tests, lint, or fix-build-errors skills, fitting the score-2 "could still overlap" anchor.	2 / 3
	Total	9 / 12 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
Commit: 0452e08

Reviewed: 14 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.