Skip to content
TrustedSkillsbeta
Back to all skills

M15 Anti Pattern

Checked
goooice·vlatest·backend

Identifies and flags common writing pitfalls (M15 anti-patterns) to improve clarity, reduce redundancy, and enhance overall communication quality.

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 m15-anti-pattern -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.

Scanned
2 files, 533 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-m15-anti-pattern, identifies and flags common anti-patterns in Rust code. It helps developers recognize inefficient or problematic coding practices that can lead to performance issues or maintainability problems. The skill aims to improve the quality of Rust projects by proactively highlighting areas for refactoring and optimization.

When to use it

  • Code Review: Integrate this skill into your code review process to catch potential anti-patterns early on.
  • Refactoring Existing Code: Use it to identify sections of legacy code that could benefit from restructuring.
  • Learning Rust Best Practices: New Rust developers can leverage the skill to learn and avoid common pitfalls.
  • Performance Optimization: Pinpoint areas in your codebase where anti-patterns are impacting performance.

Key capabilities

  • Anti-pattern detection
  • Rust code analysis
  • Identification of inefficient coding practices
  • Improvement suggestions (implied)

Example prompts

  • "Analyze this Rust code for common anti-patterns."
  • "Find any instances of m15 patterns in this project."
  • "Review this function and suggest improvements to avoid performance bottlenecks."

Tips & gotchas

This skill requires a working environment with Rust installed. The effectiveness depends on the clarity and complexity of the code being analyzed; very complex or obscure code may yield less accurate results.