Add Typescript Best Practices
CheckedHelps with TypeScript, best practices as part of developing backend services and APIs workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add glennguilloux/context-engineering-kit --skill add-typescript-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
glennguilloux
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned glennguilloux/context-engineering-kit at 245278227a.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 245278227a
- Scanned
- 2 files, 83 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill helps you incorporate TypeScript best practices into your projects. It can analyze existing code, suggest improvements based on established patterns, and automatically apply formatting rules to ensure consistency. The tool aims to improve code quality, readability, and maintainability by enforcing common TypeScript conventions.
When to use it
- Refactoring Legacy Code: Improve the type safety and structure of older JavaScript projects gradually converted to TypeScript.
- New Project Setup: Quickly establish a consistent coding style from the beginning of a new TypeScript project.
- Code Review Assistance: Automate some aspects of code review, focusing on adherence to TypeScript best practices.
- Team Onboarding: Ensure all team members follow the same TypeScript conventions and patterns.
Key capabilities
- Code analysis for type safety improvements
- Automated formatting based on established TypeScript patterns
- Suggestion of refactoring opportunities
- Enforcement of consistent coding style
Example prompts
- "Analyze this code snippet and suggest any TypeScript best practice improvements: [code]"
- "Format this file according to common TypeScript conventions: [file path]"
- "What are the potential type safety issues in this function? [function definition]"
Tips & gotchas
This skill assumes a basic understanding of TypeScript. While it can suggest improvements, reviewing and understanding those suggestions is crucial for ensuring correctness and avoiding unintended consequences.