Skip to content
TrustedSkillsbeta
Back to all skills

Input Sanitisation

Checked
cleanexpo·vlatest·security·MIT

This skill cleans user inputs to prevent vulnerabilities like injection attacks, ensuring safer and more reliable AI interactions.

Install on your platform

This skill no longer installs under the name input-sanitisation. cleanexpo/nodejs-starter-v1 is deleted or private, so it cannot be installed from.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

cleanexpo

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 cleanexpo/nodejs-starter-v1 at 7b45925bd4.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 333 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 sanitizes user input to prevent malicious code injection and ensure data integrity. It removes or escapes potentially harmful characters, making applications more secure against attacks like cross-site scripting (XSS) and SQL injection. The skill aims to produce safe and reliable data for further processing.

When to use it

  • Processing User Form Data: Before storing user input from web forms in a database.
  • Handling API Requests: Sanitizing data received from external APIs before using it within your application.
  • Generating Dynamic Content: Cleaning up user-provided content for display on websites or in applications.
  • Building Chatbots: Ensuring chatbot inputs are safe and free of potentially harmful commands.

Key capabilities

  • Removes or escapes malicious characters.
  • Prevents XSS attacks.
  • Mitigates SQL injection vulnerabilities.
  • Ensures data integrity.

Example prompts

  • "Sanitize this user input: <script>alert('XSS')</script>"
  • "Clean the following string for safe display: '; DROP TABLE users; --"
  • “Remove any HTML tags from this text.”

Tips & gotchas

The effectiveness of sanitization depends on the specific types of attacks you're trying to prevent. Consider carefully which characters need to be removed or escaped based on your application’s context and data usage.