Skip to content
TrustedSkillsbeta
Back to all skills

Limit Optional Properties

Checked
marius-townhouse·vlatest·backend

This skill restricts which optional properties are included in a response, ensuring concise and focused outputs for better clarity.

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 limit-optional-properties -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/limit-optional-properties/SKILL.md
Scanned
1 file, 265 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 allows you to limit the properties that can be optional in TypeScript interfaces or types. It enforces stricter type safety by preventing unintended omission of required fields, leading to more robust and predictable code. The skill helps ensure all expected properties are present when creating objects conforming to these types.

When to use it

  • When building complex data structures where missing properties could lead to runtime errors.
  • To enforce consistency across a codebase by preventing developers from accidentally omitting required fields.
  • During refactoring of existing TypeScript codebases to improve type safety and reduce potential bugs.
  • In projects with strict coding standards that require explicit declaration of all properties.

Key capabilities

  • Enforces optional property restrictions in TypeScript interfaces/types.
  • Provides a mechanism for defining required properties within optional structures.
  • Improves code maintainability by reducing ambiguity around optional fields.

Example prompts

  • "Apply the limit-optional-properties skill to this interface: interface User { name?: string; age?: number; }"
  • “Can you ensure that all properties in this type are explicitly defined and not implicitly optional?”
  • "Refactor this TypeScript code to prevent any optional properties from being omitted."

Tips & gotchas

This skill requires a working TypeScript environment. It's most effective when applied during the design or refactoring phase of a project, rather than as a retroactive fix for existing code with inconsistent property definitions.