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).
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The migration assessment path (line 83) requires reading the project's recent fixes and issues, which an outside reporter can submit to a public issue tracker without the agent selecting a specific item first, so it is medium under the recall-first rule even though the rest of the workflow reads only the user's own code and config.
bezmoradi/knackpack
a52ee20
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.