Skip to content
TrustedSkillsbeta
Back to all skills

Typescript Import Style

Checked
jpoutrin·vlatest·backend·MIT

Enforces consistent TypeScript import styles (order, separators, etc.) based on jpoutrin's preferred conventions.

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-import-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.

Scanned
1 file, 158 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 standardizes TypeScript import styles within a project. It automatically formats imports to adhere to a consistent style, improving code readability and maintainability. The skill ensures that all imports follow a predefined pattern, reducing stylistic inconsistencies across different files.

When to use it

  • Refactoring a large codebase: To enforce a uniform import style throughout an existing TypeScript project.
  • New projects: To establish consistent coding standards from the outset.
  • Team collaboration: To ensure all team members adhere to the same import style guidelines.
  • Automated code formatting: Integrate with CI/CD pipelines for automatic import style enforcement.

Key capabilities

  • Standardizes TypeScript imports.
  • Enforces a consistent import style.
  • Improves code readability and maintainability.

Example prompts

  • "Format the imports in src/components/Button.tsx to match project standards."
  • "Apply the standard TypeScript import style to all .ts files in the lib directory."
  • "Reformat all imports according to the configured ruleset."

Tips & gotchas

The skill requires a defined TypeScript project with existing code and potentially, an established import style guide. Ensure your project's configuration (e.g., ESLint or Prettier) is compatible for optimal results.