CtrlK
BlogDocsLog inGet started
Tessl Logo

typescript-security

Secure server-side TypeScript input, auth tokens, and injection boundaries. Use for API/request validation, sanitization, secrets, and sensitive configuration; defer client-only React form validation and generic linting.

62

Quality

75%

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 ./.github/skills/typescript/typescript-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

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

The body is a well-organized, concrete security checklist with named libraries, inline patterns, anti-patterns, and a verification step, but it is held back by a duplicated reference link, deferred executable examples, no real sequenced workflow, and dangling sub-references in REFERENCE.md.

Suggestions

Remove the duplicated REFERENCE.md reference (keep one well-signaled link with its content description) and either complete or delete the near-empty 'Canonical response anchors' section to tighten conciseness.

Add one or two complete, copy-paste-ready code blocks in the body (e.g., a Zod safeParse route handler and an Argon2id hash/verify pair) so actionable guidance does not depend solely on the reference file.

Fix progressive disclosure by either creating the missing references/authentication.md and references/security-headers.md or removing their links from REFERENCE.md so no referenced path dangles.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet guidance without concept over-explanation, but the REFERENCE.md link is duplicated (lines 27 and 54-56) and the trailing 'Canonical response anchors' section holds only a single bullet, so it could be tightened.

2 / 3

Actionability

Concrete named libraries and inline patterns appear (Zod/safeParse, DOMPurify, pool.query('... WHERE id = $1', [id]), execFileSync('git', ['arg1', arg2]), Argon2id, RS256), but full executable copy-paste blocks are deferred to the reference and several bullets are directive rather than complete code.

2 / 3

Workflow Clarity

Content is organized by topic with one Verification checkpoint (call getDiagnostics after typing schemas/guards), but there is no multi-step sequence or validate->fix->retry feedback loop, so it sits at the score-2 anchor.

2 / 3

Progressive Disclosure

The body signals REFERENCE.md one level deep with a content description, but REFERENCE.md itself references authentication.md and security-headers.md which do not exist in references/, leaving dangling referenced paths that undermine navigation.

2 / 3

Total

8

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, specific description that clearly states capabilities, provides an explicit 'Use for' trigger with deferral guidance, and carves out a distinct server-side TypeScript security niche. It is concise and uses third-person imperative voice throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Secure server-side TypeScript input, auth tokens, and injection boundaries'; 'API/request validation, sanitization, secrets, and sensitive configuration') rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what ('Secure server-side TypeScript input, auth tokens, and injection boundaries') and when via an explicit 'Use for...' clause, plus deferral guidance, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Includes natural terms users would say ('validation, sanitization, secrets, auth tokens, injection') with good coverage; not merely score 2 because it spans several common variations a user would actually voice.

3 / 3

Distinctiveness Conflict Risk

The 'server-side TypeScript' niche plus the explicit 'defer client-only React form validation and generic linting' exclusion makes conflict with adjacent skills unlikely, matching the clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.