Skip to content
TrustedSkillsbeta
Back to all skills

Ts Check Jsdoc Experiment

Checked
marius-townhouse·vlatest·writing

This skill automatically checks JavaScript files for JSDoc comments and TypeScript compatibility, ensuring code quality and documentation consistency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add marius-townhouse/effective-typescript-skills --skill ts-check-jsdoc-experiment -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

marius-townhouse

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 marius-townhouse/effective-typescript-skills at d754db2077.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d754db2077
Manifest
skills/ts-check-jsdoc-experiment/SKILL.md
Scanned
1 file, 51 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps you experiment with and understand the ts-check tool alongside JSDoc annotations in TypeScript projects. It allows for validating your code against a configuration file, ensuring type safety and catching potential errors early on. The focus is on integrating these tools to improve code quality and maintainability within TypeScript development workflows.

When to use it

  • Type checking during development: Integrate ts-check into your build process or editor for real-time feedback on JSDoc usage.
  • Validating existing TypeScript projects: Assess the type correctness of a project already using JSDoc annotations.
  • Learning and experimentation: Explore how to configure and utilize ts-check effectively with different JSDoc styles.
  • Enforcing code style: Ensure consistent use of JSDoc for improved readability and collaboration.

Key capabilities

  • Configuration file validation (ts-check)
  • JSDoc annotation analysis
  • Type checking based on annotations
  • Integration with TypeScript projects

Example prompts

  • "Run ts-check against my project's source code."
  • "Analyze this JSDoc and suggest improvements for type safety."
  • "Generate a basic ts-check configuration file for my project."

Tips & gotchas

  • Requires Node.js and npm to be installed.
  • Familiarity with TypeScript and JSDoc is recommended for effective use.