CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript-typechecker

Run TypeScript typechecking across the workspace using `pnpm run typecheck`.

Quality

76%

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 ./.agents/skills/typescript-typechecker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 body is a lean, well-sequenced workflow for a simple single-purpose skill: an exact command, a clear fix-and-re-run validation loop, and clean section organization with no padding beyond a couple of mildly redundant lines. Main improvement room is in fully specifying steps 2-4 (e.g., what to look for in output) and trimming the redundant intro line.

DimensionReasoningScore

Conciseness

The body is short with no concept explanations and concrete steps, but has minor trimmable instances: the opening line "Use this skill when you need to run static type analysis and compilation checks across the workspace" duplicates the "When to Use" section, and "Report results to the user" states a default behavior. This matches 'efficient; minor instances of over-explanation' rather than 5's 'every token earns its place', and is far from 3's unnecessary explanations.

4 / 5

Actionability

Step 1 gives the exact copy-paste-ready command `pnpm run typecheck`, and steps 2-3 give concrete direction (identify files/line numbers, fix mismatches, re-run), matching 'mostly executable guidance; concrete commands with minor gaps'. It is not 5 because steps 2-4 are guidance rather than fully specified actions (e.g., no example of interpreting compiler output or what a 'clean' run looks like), and not 3 because nothing is pseudocode or missing key details for execution.

4 / 5

Workflow Clarity

The four steps are clearly sequenced (run → analyze → fix → report) and include an explicit validation feedback loop: "Fix any reported type mismatches or syntax issues, and re-run the typecheck to ensure clean output", matching the anchor for clear sequence with explicit validation and error-recovery loops. It is not 4 because the re-run-until-clean checkpoint is explicit rather than a minor gap; the operation is also non-destructive, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (none exist in the bundle), and is organized into clear "When to Use" and "Steps" sections — matching the guideline that simple, short skills with well-organized sections and no need for external files score 5. There is no inlined content that belongs in a separate file, so it is not 3 or 4.

5 / 5

Total

18

/

20

Passed

Description

57%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 one concrete, executable action with an exact command and occupies a distinct niche, but it is minimal: no 'when to use' guidance and thin trigger-term coverage (missing 'type errors', 'compile', '.ts'). Adding an explicit 'Use when...' clause with natural trigger phrases would raise completeness and trigger-term quality substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when modifying .ts/.tsx files, when the user mentions type errors or compile errors, or before committing TypeScript changes."

Include natural synonyms and file extensions users would actually say — "type errors", "compilation errors", ".ts/.tsx files" — alongside "typecheck".

Optionally state the follow-on capability (analyze errors and fix mismatches) so the 'what' covers more than just invoking the command.

DimensionReasoningScore

Specificity

"Run TypeScript typechecking across the workspace using `pnpm run typecheck`" names the domain (TypeScript typechecking) and one concrete action with the exact command, matching the anchor for 1-2 concrete actions that are not comprehensive. It is not 4 because it lists only a single action (running the check) and omits related capabilities like analyzing output or fixing errors; it is not 2 because the command makes the action concrete rather than generic.

3 / 5

Completeness

It clearly answers 'what' (runs workspace-wide TypeScript typechecking via a specific command) but contains no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3. It is not 4 because the 'when' is entirely absent rather than just under-specified, and not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

The description includes "TypeScript", "typechecking", and "pnpm" — some relevant keywords — but misses common variations users would naturally say such as "type errors", "compile errors", or ".ts files", matching the anchor for some relevant keywords missing common variations. It is not 4 because keyword coverage is narrow (essentially one concept plus the tool name), and not 2 because "typecheck"/"TypeScript" are genuine natural terms rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

"Run TypeScript typechecking across the workspace using `pnpm run typecheck`" occupies a clear niche — TypeScript static type checking in a pnpm workspace — with a distinct, specific trigger that is unlikely to fire for unrelated skills. It is not 4 because the niche and command are more precisely delimited than the 'minor overlap with closely related skills' anchor (e.g., PDF and Word documents); no closely related skill would plausibly be triggered by this wording.

5 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/typescript-typechecker/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.