Skip to content
TrustedSkillsbeta
Back to all skills

Avoid Inferable Annotations

Checked
marius-townhouse·vlatest·backend

This skill prevents AI from generating responses containing potentially sensitive or inferable information about individuals, enhancing privacy and safety.

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 avoid-inferable-annotations -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/avoid-inferable-annotations/SKILL.md
Scanned
1 file, 243 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 AI agents write more explicit and readable TypeScript code by avoiding the use of type inference where possible. It encourages developers to explicitly define types, leading to improved clarity and reduced potential for unexpected behavior. The skill promotes a style that prioritizes maintainability and reduces ambiguity in larger projects.

When to use it

  • When refactoring existing JavaScript or TypeScript codebases to improve readability and reduce implicit type assumptions.
  • During code reviews to enforce consistent typing practices within a team.
  • When working on complex projects where explicit type annotations are crucial for maintainability and debugging.
  • To onboard new developers to a project with specific TypeScript style guidelines.

Key capabilities

  • Explicit Type Annotations: Promotes the use of : string, : number, etc., instead of relying solely on type inference.
  • Code Readability: Encourages code that is easier to understand and reason about.
  • Maintainability: Reduces ambiguity and simplifies future modifications.

Example prompts

  • "Rewrite this TypeScript function to explicitly define all types."
  • "Review this code snippet for opportunities to use explicit type annotations."
  • "Suggest improvements to this code to make it more readable by avoiding implicit typing."

Tips & gotchas

This skill is most effective when used in conjunction with a linter or formatter configured to enforce the desired TypeScript style. While explicit types improve clarity, excessive verbosity can also hinder readability; balance is key.