CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript

Use when authoring or reviewing TypeScript code that requires strict type safety, explicit module contracts, and predictable runtime boundaries.

Quality

63%

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 ./Skills/agent-ops/typescript/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 lean, sectioned body with one executable example and a sequenced procedure, but it is held back by generic boilerplate sections, a single code example for many rules, unspecified validation commands, a broken reference path, and an off-topic stray bullet ("Redact secrets, tokens, credentials, and sensitive data by default.") misplaced under Type Safety.

Suggestions

Fix the reference path from `Infrastructure/references/deep-guidance.md` to `references/deep-guidance.md` and either list or remove the unmentioned bundle files (contract.yaml, evals.yaml, task-profile.json).

Replace "Run the relevant local checks" with a concrete command (e.g., `npx tsc --noEmit` on touched files) so the Validation feedback loop is executable rather than implicit.

Cut the generic Philosophy/Procedure/Anti-patterns boilerplate and the stray "Redact secrets" bullet, and add 1-2 more executable examples covering the remaining rules (e.g., a discriminated union or an IO-boundary guard).

DimensionReasoningScore

Conciseness

Bullets are terse and no basic concepts are over-explained, but the generic Philosophy/Procedure/Anti-patterns boilerplate ("Optimize for clear, verifiable outcomes with the minimum necessary changes"), the redundant Table of Contents, and a "When to use" section duplicating the frontmatter description are unnecessary padding. Mostly efficient with several sections that could be trimmed — anchor 3, not anchor 2 since most lines do earn their place.

3 / 5

Actionability

One complete executable example exists (the `parsePort` function) plus concrete per-rule directives ("Avoid `any`", "Prefer named exports over default exports"), but only one code example covers roughly nine rules, and validation guidance names no command ("Run the relevant local checks"). The gaps exceed anchor 4's "minor gaps"; anchor 3's "some concrete guidance but incomplete" fits.

3 / 5

Workflow Clarity

The Procedure section gives a sequenced three-step flow and Validation specifies fail-fast plus re-run-after-fix behavior, so a feedback loop exists. However, checkpoints are implicit — no concrete check command (e.g., `tsc --noEmit`) is ever named, matching anchor 3's "checkpoints missing or implicit" rather than anchor 4.

3 / 5

Progressive Disclosure

Sections are organized and the deep-guidance reference is well-signaled with a "Read when:" clause, but the path `Infrastructure/references/deep-guidance.md` does not match the actual bundle file `references/deep-guidance.md`, and three of the four files in `references/` (contract.yaml, evals.yaml, task-profile.json) are never mentioned in SKILL.md. Scored against the actual bundle structure, this is "some structure but could be better organized" — anchor 3.

3 / 5

Total

12

/

20

Passed

Description

61%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 reasonably specific, third-person description with an explicit trigger clause and good natural keywords, but it is entirely a when-statement: it never states what the skill concretely does or delivers, leaving completeness as the main weakness.

Suggestions

Lead with a concrete what-statement before the trigger, e.g. "Hardens TypeScript code with explicit return types, discriminated unions, and guarded IO boundaries. Use when authoring or reviewing TypeScript...".

Add commonly-said trigger variations such as ".ts", ".tsx", "type errors", or "type-safe" to improve natural-term coverage.

Name 1-2 concrete deliverables (e.g., "adds explicit types to exported surfaces", "replaces `any` with guards") to lift specificity from attributes to actions.

DimensionReasoningScore

Specificity

The description names the domain and actions ("authoring or reviewing TypeScript code") plus scope attributes ("strict type safety, explicit module contracts, and predictable runtime boundaries"), but these are conditions rather than concrete deliverable actions. It lists domain and 1-2 actions without comprehensive coverage, matching anchor 3 rather than anchor 4's "several specific actions".

3 / 5

Completeness

The description is entirely a "Use when..." trigger clause — the when is explicit, but the what (what the skill actually does or delivers) is only weakly implied through "authoring or reviewing". This matches the shape of anchor 3 (one side clear, the other weak/implicit) rather than anchor 4, which requires both an explicit what and when.

3 / 5

Trigger Term Quality

Natural terms users would say are present — "TypeScript", "type safety", "reviewing", "strict" — with good keyword coverage. It falls short of anchor 5 because common variations like ".ts"/".tsx" extensions, "types", or "type errors" are missing, but coverage is clearly above anchor 3's partial-relevance level.

4 / 5

Distinctiveness Conflict Risk

"TypeScript code that requires strict type safety, explicit module contracts" carves a mostly distinct niche with specific triggers. Minor overlap risk remains with closely related skills (JavaScript authoring, TS linting), keeping it below anchor 5's "clear niche with minimal conflict risk".

4 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/typescript/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.