Skip to content
TrustedSkillsbeta
Back to all skills

M15 Anti Pattern

Checked
zhanghandong·vlatest·backend

Identifies and flags common M15 design patterns in code, improving maintainability and reducing potential issues.

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 actionbook/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

zhanghandong

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 zhanghandong/rust-skills at 5c40d3ad78.

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

Commit
5c40d3ad78
Manifest
skills/m15-anti-pattern/SKILL.md
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

The m15-anti-pattern skill helps identify and avoid common anti-patterns in software development, particularly within Rust projects. It analyzes code structures, design choices, and implementation strategies to flag practices that may lead to inefficiencies, bugs, or maintenance challenges.

When to use it

  • During code reviews to catch problematic patterns before they are merged into the main branch.
  • When refactoring legacy code to ensure adherence to best practices.
  • Before deploying a new feature to verify that no harmful design choices were made.
  • As part of an automated CI/CD pipeline to enforce coding standards and quality.

Key capabilities

  • Detects overuse of global state or singletons in Rust applications.
  • Identifies unnecessary complexity in function signatures or module structures.
  • Highlights improper error handling patterns that may lead to silent failures.
  • Warns against unsafe code practices that violate Rust's safety guarantees.

Example prompts

  • "Analyze this Rust module for anti-patterns."
  • "Check the use of unsafe blocks in this file for potential issues."
  • "Review the function signature and suggest improvements."

Tips & gotchas

  • This skill works best when used alongside a linter or static analysis tool for comprehensive code quality checks.
  • It may not catch all anti-patterns, especially those that are context-specific or require domain knowledge to identify.