Skip to content
TrustedSkillsbeta
Back to all skills

Typescript Style

Checked
jpoutrin·vlatest·backend·MIT

Generates clean, well-documented TypeScript code adhering to jpoutrin's preferred style for robust backend development.

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 jpoutrin/product-forge --skill typescript-style -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

jpoutrin

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 jpoutrin/product-forge at 0ebe7aea08.

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

Commit
0ebe7aea08
Manifest
plugins/frontend-experts/skills/typescript-style/SKILL.md
Scanned
1 file, 76 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, typescript-style, enforces consistent code style and formatting within TypeScript projects. It automatically applies rules to ensure adherence to a predefined style guide, improving readability and maintainability of codebase. The skill aims to reduce stylistic debates among developers and streamline the development process.

When to use it

  • New TypeScript Projects: To establish a consistent coding standard from the outset.
  • Existing Codebases Needing Refactoring: To standardize code style across a large project.
  • Team Collaboration: To ensure all team members adhere to the same formatting rules.
  • Automated Linting & Formatting: Integrate into CI/CD pipelines for automated code quality checks.

Key capabilities

  • Enforces TypeScript coding style guidelines.
  • Automatic code formatting.
  • Improves code readability and maintainability.
  • Reduces stylistic debates within development teams.

Example prompts

  • "Apply the typescript-style rules to this file: src/components/Button.tsx."
  • "Format this TypeScript code snippet according to the project's style guide."
  • "Check if this code adheres to the configured TypeScript style guidelines and report any violations."

Tips & gotchas

  • Requires a TypeScript project with existing codebase or new files.
  • The specific rules enforced depend on the underlying configuration used by the skill (e.g., ESLint, Prettier).