Skip to content
TrustedSkillsbeta
Back to all skills

Hide Unsafe Assertions

Checked
marius-townhouse·vlatest·backend

This skill automatically hides potentially sensitive or risky "unsafe assertion" messages generated by AI, improving safety and privacy.

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 hide-unsafe-assertions -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/hide-unsafe-assertions/SKILL.md
Scanned
1 file, 236 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

The hide-unsafe-assertions skill allows you to suppress TypeScript compiler errors related to "unsafe assertions." It effectively removes the noise of these errors, which often arise when dealing with type uncertainty or potentially incorrect assumptions about data types. This helps focus on more critical issues during development and refactoring while acknowledging the risks associated with suppressed assertion errors. The skill does not resolve the underlying type issues; it merely hides the compiler warnings.

When to use it

  • Rapid prototyping: Quickly iterate on code without being bogged down by assertion errors that might be addressed later.
  • Legacy codebases: Suppressing these errors can make working with older TypeScript projects less painful, especially when full type safety isn't immediately feasible.
  • Experimental features: When exploring new libraries or APIs where types are still evolving and assertions are frequently triggered.
  • Refactoring complex logic: Simplify the compiler output during significant code changes to improve readability.

Key capabilities

  • Suppresses TypeScript "unsafe assertion" errors.
  • Allows for continued development despite potential type issues.
  • Provides a mechanism to temporarily ignore assertion-related warnings.

Example prompts

  • “Hide all unsafe assertions in this file.”
  • “Suppress the unsafe assertion error on line 42 of my_module.ts."
  • "Temporarily disable unsafe assertion checks for this function."

Tips & gotchas

Be mindful that suppressing these errors doesn't fix the underlying type issues. It’s crucial to revisit and address them later to maintain code quality and prevent runtime errors. This skill should be used judiciously, not as a replacement for proper TypeScript typing.