typescript

TypeScript strict mode with eslint and jest

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/typescript/SKILL.md

Quality

Content

80%

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

This is a dense, highly actionable TypeScript standards reference with complete, executable config for strict mode, eslint, jest, CI, and pre-commit hooks. Its main gaps are the absence of validation/feedback checkpoints in its workflows and a fully inline structure that, at this length, would benefit from split reference files.

Suggestions

Add explicit validation/feedback loops to the pre-commit and CI sequences (e.g., 'if typecheck fails, fix errors and re-run before committing').

Move the larger blocks (full eslint.config.js, GitHub Actions YAML, type patterns) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Clarify the single recommended workflow for applying these standards to a new project so the operational sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code with minimal prose and no explanations of concepts Claude already knows; inline comments ('# Pure business logic', 'Type-safe error handling without exceptions') are brief value-adds. Every section earns its tokens.	3 / 3
Actionability	Provides complete, copy-paste-ready configuration: a full tsconfig.json, package.json scripts, eslint.config.js, a jest test, a GitHub Actions YAML, and husky/lint-staged setup. A few type-pattern snippets use stub function bodies, but the type declarations and config blocks are fully executable.	3 / 3
Workflow Clarity	Sequences exist (the numbered pre-commit list '1. ESLint + Prettier... 2. Type check... 3. Tests...' and ordered CI steps), but there are no validation checkpoints or error-recovery feedback loops. Not a 1 (steps are clearly listed) and not a 3 (no explicit validate-then-fix loops).	2 / 3
Progressive Disclosure	The 247-line body is organized into well-labeled sections but is monolithic: no bundle files exist (references/scripts/assets absent) and content that could be split (full eslint config, CI YAML, type patterns, anti-patterns) is all inline. Not a 1 (organization is clear, not a wall of text) and not a 3 (no one-level-deep references or content split).	2 / 3
	Total	10 / 12 Passed

Description

50%

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 concisely names a specific TypeScript tooling stack but stops there: it declares a configuration topic rather than actions and omits any 'when to use' trigger. It is clear and non-generic, yet incomplete as trigger guidance.

Suggestions

Add concrete action verbs, e.g. 'Configure TypeScript strict mode, enforce linting with eslint, and run jest tests'.

Append an explicit trigger clause, e.g. 'Use when setting up or working on a TypeScript project that needs strict type-checking, eslint, and jest.'

Include natural term variations users say (.ts/.tsx files, tsconfig, linting, type-checking) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and tooling ('TypeScript strict mode with eslint and jest'), which imply linting and testing actions, but lists no concrete action verbs. Not a 1 because the tech stack is specific rather than abstract; not a 3 because no multiple concrete actions are enumerated.	2 / 3
Completeness	The description states what ('TypeScript strict mode with eslint and jest') but provides no 'when' guidance. Per the rubric, a missing explicit 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	'TypeScript', 'strict mode', 'eslint', and 'jest' are natural terms a user would say, but coverage lacks common variations such as '.ts files', 'linting', 'testing', or 'tsconfig'. Not a 1 (terms are natural, not jargon) and not a 3 (incomplete coverage of natural variations).	2 / 3
Distinctiveness Conflict Risk	The strict-mode-plus-eslint-plus-jest combination is somewhat specific, but it could overlap with a generic TypeScript skill, a linting skill, or a testing skill. Not a 3 because there are no distinct trigger phrases.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/typescript/SKILL.md
Commit: bb6195f

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