Skip to content
TrustedSkillsbeta
Back to all skills

Evolving Types

Checked
marius-townhouse·vlatest·backend

This skill dynamically adjusts Pokémon types based on your team’s needs and the opponent's, maximizing strategic advantages in battles.

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 evolving-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/evolving-types/SKILL.md
Scanned
1 file, 261 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 evolving-types skill allows an AI agent to understand and manipulate TypeScript types that change over time. It can track the evolution of a type definition across different versions or branches, enabling more accurate code analysis and refactoring. Specifically, it facilitates understanding how type definitions have changed, allowing for better migration strategies and compatibility checks. This capability is particularly useful when dealing with complex projects where types are frequently updated.

When to use it

  • Code Migration: When upgrading a TypeScript project from one version to another, the skill can help identify breaking changes in type definitions.
  • Refactoring Large Codebases: Understand how modifications to a core type affect dependent code across a large project.
  • Branch Comparison: Analyze differences in type definitions between different branches of a codebase for collaborative development.
  • Dependency Management: Determine compatibility issues arising from changes in third-party TypeScript libraries' types.

Key capabilities

  • Type evolution tracking
  • Version comparison
  • Branch analysis
  • Compatibility checks

Example prompts

  • "Show me how the User type has changed between versions 3.0 and 4.0."
  • "Compare the Product type in the 'main' branch with the 'feature/new-api' branch."
  • "What are the breaking changes introduced to the ApiResponse type?"

Tips & gotchas

The skill requires access to a version control system (like Git) and accurate TypeScript code repositories. The accuracy of results depends on the completeness and correctness of the available type definitions.