Skip to content
TrustedSkillsbeta
Back to all skills

Excess Property Checking

Checked
marius-townhouse·vlatest·backend

This tool efficiently checks if a property has excessive features or outbuildings, streamlining planning applications and reducing potential delays.

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 excess-property-checking -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.

Scanned
1 file, 253 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 excess-property-checking skill helps identify and flag TypeScript code that includes properties on objects or interfaces beyond what's explicitly defined. This prevents potential runtime errors caused by unexpected data being assigned to undeclared properties, improving code reliability and maintainability. It focuses specifically on ensuring type safety within TypeScript projects.

When to use it

  • Code Reviews: Use this skill during code reviews to automatically identify instances of excess property assignment that might be overlooked.
  • Refactoring Legacy Code: When refactoring older JavaScript or TypeScript codebases, leverage the skill to enforce stricter typing and prevent unexpected behavior.
  • New Project Initialization: Integrate it into your development workflow for new projects to establish a baseline of type safety from the outset.
  • Automated Linting: Incorporate this skill within automated linting pipelines to continuously monitor code quality.

Key capabilities

  • Flags excess property assignments in TypeScript code.
  • Supports object and interface types.
  • Can be integrated into development workflows.

Example prompts

  • "Analyze this TypeScript file for any instances of excess property assignment."
  • "Review the following code snippet and identify potential type safety issues related to undeclared properties."
  • “Find all occurrences where a property is assigned to an object that isn’t defined in its type.”

Tips & gotchas

This skill requires a TypeScript project environment. Ensure your development tools are configured for TypeScript analysis to get the most accurate results.