CtrlK
BlogDocsLog inGet started
Tessl Logo

tsconfigs

Locate and modify TypeScript configuration in RedisInsight. Use when adding path aliases, introducing a new TS area, debugging webpack/ts-node/ESLint path resolution, or the user asks about tsconfig, path mappings, or where TypeScript is configured.

72

Quality

88%

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

90%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 knowledge skill with concrete file paths, code, and procedures that assumes Claude's competence. Adding a validation step to the alias-adding workflow and optionally splitting exhaustive detail into a reference file would push it to the top anchor.

Suggestions

Add a verification step to 'Adding a path alias' (e.g. run `npm run type-check:ui`/`type-check:api` to confirm the alias resolves) so the workflow has an explicit validation checkpoint.

Consider a short 'Verify' note after the new-top-level-folder steps noting that ESLint/`parserOptions.project: true` will now resolve, giving feedback if the tsconfig is malformed.

If the layout table or per-area strict-mode details grow, move the exhaustive per-tsconfig breakdown into a reference file linked one level deep to keep SKILL.md an overview.

DimensionReasoningScore

Conciseness

Lean and dense: a layout table, minimal code snippets, and tight prose with no padding or re-explanation of basic TypeScript/build concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides concrete, executable guidance with exact file paths, package.json script names, copy-ready code blocks, and a 'Common tasks' section with step-by-step procedures covering the main cases.

5 / 5

Workflow Clarity

Sequences for adding aliases and new folders are clear, but the workflows lack an explicit validation checkpoint (e.g. run type-check to confirm aliases resolve) before moving on, leaving a minor validation gap.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized sections, a table, and headers; no nested references and content is appropriately inline, but no external references are used to offload detail, so it sits just below the clear-overview-with-one-level-refs anchor.

4 / 5

Total

18

/

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 strong, third-person description that clearly states both what the skill does and when to invoke it, scoped to a distinct niche. Minor additional synonyms would round out trigger coverage but it is already comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('TypeScript configuration in RedisInsight') and several concrete actions (adding path aliases, introducing a new TS area, debugging webpack/ts-node/ESLint path resolution); not quite comprehensive since 'locate and modify' is somewhat general, so a 4 rather than 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Locate and modify TypeScript configuration in RedisInsight') and 'when' ('Use when adding path aliases, introducing a new TS area, debugging...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('path aliases', 'tsconfig', 'path mappings', 'where TypeScript is configured', 'webpack/ts-node/ESLint path resolution'); a few natural synonyms (e.g. 'tsconfig.json', 'paths') are implied but not exhaustive, so just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to RedisInsight's per-area tsconfig setup with distinct, niche-specific triggers; minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

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.