CtrlK
BlogDocsLog inGet started
Tessl Logo

type-check-baselines

Run, refresh, or recover from RedisInsight's per-project TypeScript error baselines (.tscheck.rec.json). Use when CI reports "baseline is outdated" or "more TS errors than previously recorded", when the user mentions tscheck / type-check / .tscheck.rec.json, when introducing or fixing TS errors, or when reviewing PRs that touch baseline files.

78

Quality

98%

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

96%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 lean, fully executable, and structured around concrete CI/workflow scenarios with clear validation and PR-review checklists. Its only gap is the absence of separate reference files, keeping progressive disclosure just shy of the top anchor.

Suggestions

Consider extracting the per-project baseline mechanics or the plugin-deps/api-build troubleshooting into a short REFERENCE.md so SKILL.md stays a tight overview and progressive disclosure reaches the top anchor.

Add a brief one-line 'verify' step after `npm run tscheck` refresh (e.g. re-run `npm run type-check`) to make the refresh feedback loop fully explicit.

The 'Configs' project row has no baseline file and no tscheck refresh path; a one-line note on how to verify it stays at 0 errors would close a minor actionability gap.

DimensionReasoningScore

Conciseness

Lean body with no padding or explanations of concepts Claude already knows; tables, exact commands, and bare snippets each earn their tokens. Only mild over-explanation appears in the root-bin PATH trap, which is genuinely non-obvious and worth keeping.

5 / 5

Actionability

Provides copy-paste-ready commands (`npm run type-check`, `npm run tscheck`, `npm run tscheck:force`) with concrete project paths, and a worked escape-hatch (`PATH="$PWD/node_modules/.bin:$PATH" npm run tscheck --prefix redisinsight/ui`).

5 / 5

Workflow Clarity

Each CI scenario ('baseline is outdated', 'more TS errors', fresh baseline) is sequenced with explicit validation and feedback guidance (read script output, fix errors, then refresh from root); the PR-review section functions as a checklist with explicit reject/approve criteria.

5 / 5

Progressive Disclosure

Well-organized into clear sections with a strong overview table, but the skill has no bundle files and inlines all detail in a single SKILL.md; there is no one-level-deep reference split, so it sits just below the top anchor rather than matching it.

4 / 5

Total

19

/

20

Passed

Description

100%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 is concrete, trigger-rich, and explicit about both capability and use conditions, hitting the top anchors on every dimension. It avoids fluff and uses appropriate third-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Run, refresh, or recover from ... TypeScript error baselines') tied to a specific artifact (`.tscheck.rec.json`), covering the full operational surface.

5 / 5

Completeness

Explicitly answers both 'what' (run/refresh/recover baselines) and 'when' via a concrete 'Use when ...' clause enumerating CI messages, user terms, and PR scenarios.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('CI reports baseline is outdated', 'more TS errors than previously recorded', 'tscheck / type-check / .tscheck.rec.json', 'reviewing PRs that touch baseline files') with the exact file extension and tool names.

5 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (per-project TS baseline ratchet) with distinct triggers like `.tscheck.rec.json` and `tscheck`, making overlap with other skills minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
redis/RedisInsight
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.