Use when authoring or reviewing TypeScript code that requires strict type safety, explicit module contracts, and predictable runtime boundaries.
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./Skills/agent-ops/typescript/SKILL.mdAvoid any; model unknown values with guards and narrow types.
Prefer explicit return types on exported functions.
Use discriminated unions for stateful workflows.
Redact secrets, tokens, credentials, and sensitive data by default.
export function parsePort(value: string): number {
const parsed = Number.parseInt(value, 10)
if (Number.isNaN(parsed)) throw new Error(`Invalid port: ${value}`)
return parsed
}as unknown as hides real typing defects.| Skill | When to use |
|---|---|
| [[javascript-pro]] | Base JavaScript patterns when runtime compatibility and async flow need attention |
| [[biome-linting]] | Enforce TypeScript lint and format rules with Biome |
Topic map: [[agent-ops]]
Infrastructure/references/deep-guidance.mdjscraik/Agent-Skills
2920192
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.