Skip to content
TrustedSkillsbeta
Back to all skills

Dry Types

Checked
marius-townhouse·vlatest·backend

Dry Types generates diverse, evocative prose snippets mimicking various writing styles – useful for sparking creativity or rapid content drafts.

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 dry-types -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/dry-types/SKILL.md
Scanned
1 file, 317 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 dry-types skill helps ensure your TypeScript code adheres to the "Don't Repeat Yourself" (DRY) principle. It analyzes TypeScript code and identifies opportunities to reduce redundancy, promoting cleaner, more maintainable codebases by suggesting type definitions that can be reused or generalized. This leads to fewer errors and easier updates across projects.

When to use it

  • Refactoring existing TypeScript projects: Identify duplicated type definitions and consolidate them for improved consistency.
  • Creating new TypeScript libraries/packages: Enforce DRY principles from the outset, leading to a more robust and maintainable codebase.
  • Code reviews: Quickly identify potential areas of code duplication related to types during peer review processes.
  • Large projects with many type definitions: Streamline complex type systems by identifying and eliminating redundancies.

Key capabilities

  • Type definition analysis
  • Redundancy detection
  • Suggestion generation for reusable types
  • Codebase-wide scanning

Example prompts

  • "Analyze this TypeScript code for duplicated type definitions."
  • "Suggest ways to consolidate these similar interfaces in my project."
  • "Find opportunities to reuse type definitions within this codebase."

Tips & gotchas

This skill is most effective when applied to larger projects with a significant number of type definitions. It requires access to the TypeScript source code for analysis.