Skip to content
TrustedSkillsbeta
Back to all skills

M13 Domain Error

Checked
goooice·vlatest·backend

This skill identifies and flags potential domain errors within M13 data, ensuring accuracy and preventing misleading results.

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 goooice/rust-skills --skill m13-domain-error -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

goooice

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 goooice/rust-skills at 57af2e8da9.

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

Commit
57af2e8da9
Manifest
skills/m13-domain-error/SKILL.md
Scanned
1 file, 173 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, goooice-m13-domain-error, provides functionality related to domain error handling within a Rust environment. It likely focuses on identifying and managing errors that arise when dealing with domain names or similar structured data. The specific implementation details are not provided in the source content.

When to use it

  • When you need to validate domain names for correctness before processing them further.
  • In applications where incorrect domain name formatting could lead to security vulnerabilities.
  • During development and testing of systems that rely on accurate domain data.
  • To improve the robustness of your application by gracefully handling invalid or malformed domain inputs.

Key capabilities

  • Domain error identification
  • Rust-specific implementation (likely)
  • Error management within a Rust environment

Example prompts

  • "Check if this is a valid domain: example.com"
  • "What errors would arise from the domain 'invalid..domain'"
  • “Validate and sanitize this domain string for use in an API call.”

Tips & gotchas

This skill requires a Rust development environment to utilize effectively. The specific error handling strategies employed are not detailed, so thorough testing is recommended when integrating it into your projects.