CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript-engineering

Guide writing or changing TypeScript, or JavaScript checked with JSDoc, so its types make real guarantees: learn the project's TypeScript version, tsconfig, runtime and module system first, then validate untrusted data at the boundary instead of casting it, model states with discriminated unions, keep generics that relate something, configure tsconfig and package exports for what actually loads the code, keep declarations in step with runtime behavior, and verify with the project's own type check. Also assesses, on request, whether and how a JavaScript project should adopt TypeScript. Use whenever you create or edit .ts, .tsx, .mts or .cts files, type declarations, a tsconfig, or JSDoc types, even when the user doesn't say TypeScript. It adds no library, upgrade or migration unasked. Not for reviewing code already written (the knackpack:typescript-code-reviewer agent, started only on request), React's own semantics, custom element behavior, or choosing between technologies in general (the research skill).

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 strong, expert-level instruction skill: nearly every line is non-obvious, project-aware guidance with concrete commands, flags, and patterns, organized into a clear learn-apply-verify flow. Its weaknesses are modest: a long single-file body with no reference split, inline time-sensitive version history, and a few places (boundary guards, migration assessment) where an example would make execution more copy-paste ready.

Suggestions

Move the TypeScript version-compatibility details (§1's 6.0/7.0 default changes and removals) into a references/ file such as references/version-compat.md, keeping only 'check the lockfile version; see version-compat.md for what differs' in SKILL.md — this both trims the body and quarantines time-sensitive information that will age.

Split the JavaScript-to-TypeScript adoption assessment (§7) into its own reference file, leaving the five outcome options and 'assess before recommending' framing inline; the assessment checklist and staged incremental plan are a self-contained sub-guide that inflates the main file.

Add one short executable snippet for the two most load-bearing patterns — a field-checking guard for boundary validation (§2) and the discriminated-union-with-never-default idiom (§3) — so the guidance is copy-paste ready rather than describable-only.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basics are re-explained, and nearly every rule carries non-obvious specifics (e.g. 'Number("") is 0, Boolean("false") is true', 'never export a const enum from a library', TS2589 bounding). It is not a 5 because the ~95-line body retains time-sensitive version history inline ('From 7.0 it is the native compiler... 7.0 removed baseUrl, moduleResolution: node10/classic...') rather than isolating it, which the judging guidelines say should penalize conciseness, and a few rules could be tightened. It is well above anchor 3, which requires genuinely unnecessary explanation.

4 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: exact commands ('tsc --noEmit', 'tsc -b', 'tsc --extendedDiagnostics'), exact config values ('module: nodenext', '.js' extensions, 'rewriteRelativeImportExtensions'), and exact patterns ('default: { const unreachable: never = value; … }', 'load<T>(): T' as an anti-pattern, 'K extends PropertyKey'). It falls short of anchor 5 only in minor gaps — e.g. 'write a guard that checks every field the code relies on' and the migration assessment give checklists but no example snippet a model could pattern-match directly.

4 / 5

Workflow Clarity

A clear sequence is present — 'Read before writing' (§1) → applied rules (§2–8) → an explicit verification section (§9) with type-check, lint, run, and report checkpoints. The destructive/batch cap does not apply (the skill forbids fix/format modes and unrequested installs). It misses anchor 5 because there is no explicit error-recovery loop after a failed check (e.g. type-check fails → fix → re-run) and §9's checkpoints are a flat list rather than a gated loop like the anchor's 'Only when valid' pattern.

4 / 5

Progressive Disclosure

The single-file body is well organized: an overarching rules section plus nine clearly titled, numbered sections, and no buried or nested references (there are no bundle files at all). It is not a 5 because at ~95 lines it exceeds the simple-skill range where sections alone suffice, and self-contained blocks — the TypeScript version-compatibility history in §1 and the full JS-adoption assessment methodology in §7 — are natural candidates for one-level-deep references/ files that would keep SKILL.md an overview. It is clearly above anchor 3, whose example is undifferentiated inline API reference.

4 / 5

Total

16

/

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.

An exemplary description: third-person voice, comprehensive concrete capabilities, explicit trigger guidance with file extensions, and explicit exclusions that disambiguate it from adjacent skills. The only nit is that the long exclusion sentence leans on internal agent/skill names, but this does not weaken any scored dimension.

DimensionReasoningScore

Specificity

The description lists many concrete actions — 'learn the project's TypeScript version, tsconfig, runtime and module system first', 'validate untrusted data at the boundary instead of casting it', 'model states with discriminated unions', 'configure tsconfig and package exports', 'keep declarations in step with runtime behavior', 'verify with the project's own type check' — plus a secondary capability (assessing JS-to-TS adoption). This matches the anchor for multiple specific concrete actions with comprehensive coverage; the level-4 anchor ('minor gaps in coverage') understates it since every major facet of the skill is named.

5 / 5

Completeness

It explicitly answers both questions: what ('Guide writing or changing TypeScript... so its types make real guarantees' followed by a concrete action list) and when ('Use whenever you create or edit .ts, .tsx, .mts or .cts files, type declarations, a tsconfig, or JSDoc types'). This mirrors the anchor-5 example's explicit what-plus-when structure with concrete trigger phrases; level 4 ('when could be more explicit') is too low given the enumerated trigger conditions.

5 / 5

Trigger Term Quality

It covers the natural terms a user would actually say: 'TypeScript', '.ts, .tsx, .mts or .cts files', 'type declarations', 'a tsconfig', 'JSDoc types', and 'JavaScript project should adopt TypeScript' — including file extensions and the implicit-trigger case ('even when the user doesn't say TypeScript'). The level-4 anchor ('a few natural terms missing') doesn't apply: primary nouns, file extensions, config artifacts, and the migration phrasing are all present.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (type-level correctness of TypeScript/checked-JS code) and adds explicit negative boundaries — 'Not for reviewing code already written (the knackpack:typescript-code-reviewer agent...), React's own semantics, custom element behavior, or choosing between technologies in general (the research skill)' — which is stronger disambiguation than the anchor-5 example. Distinct triggers (.ts/.tsx/.mts/.cts, tsconfig, JSDoc) keep conflict risk minimal.

5 / 5

Total

20

/

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

bezmoradi/knackpack

Path

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