Typescript Detector
CheckedIdentifies TypeScript code blocks within files, extracting relevant information for automated analysis and refactoring.
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 alex-popov-tech/.dotfiles --skill typescript-detector -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
alex-popov-tech
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 alex-popov-tech/.dotfiles at 729394ec7a.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 729394ec7a
- Scanned
- 1 file, 181 lines
About this skill
What it does
The typescript-detector skill identifies whether a given file contains TypeScript code. It can analyze files based on their content to determine if they utilize TypeScript syntax and features, rather than relying solely on file extensions. This allows for accurate detection even when files have incorrect or missing extensions.
When to use it
- Code analysis pipelines: Integrate into build processes to conditionally execute TypeScript-specific tasks (e.g., compilation).
- File type identification: Determine the programming language of a file without relying on its extension, useful for automated tooling.
- Refactoring tools: Identify TypeScript files that need conversion or modification during code refactoring efforts.
- Content filtering: Filter files based on whether they contain TypeScript code for specific operations.
Key capabilities
- Content-based TypeScript detection
- Accurate identification regardless of file extension
- Integration into automated workflows
Example prompts
- "Is this file a Typescript file? [file content]"
- "Analyze the following code and tell me if it's written in TypeScript: [code snippet]"
- "Detect if the provided text contains TypeScript syntax: [text block]"
Tips & gotchas
The skill relies on analyzing the content of a file. Very short or incomplete files might lead to inaccurate results. Ensure sufficient code is provided for reliable detection.