Skip to content
TrustedSkillsbeta
Back to all skills

Quality Detect Refactor Markers

Checked
dawiddutoit·vlatest·backend

Identifies code quality issues & suggests refactoring opportunities based on established markers, improving maintainability.

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 dawiddutoit/custom-claude --skill quality-detect-refactor-markers -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

dawiddutoit

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 dawiddutoit/custom-claude at 17b45a90a6.

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

Scanned
4 files, 2,566 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 identifies and flags code quality issues and potential refactoring opportunities within a given codebase. It analyzes the provided code for common anti-patterns, areas of complexity, and suggests improvements to enhance readability and maintainability. The skill aims to improve code quality by pinpointing specific problem areas that require attention.

When to use it

  • Code Review Assistance: Use this skill when reviewing a colleague's code or your own work before merging into a main branch.
  • Legacy Codebase Modernization: Identify and prioritize refactoring efforts in older, more complex projects.
  • Onboarding New Developers: Help new team members quickly understand the codebase’s strengths and weaknesses.
  • Automated Quality Checks: Integrate this skill into CI/CD pipelines to automatically flag potential quality issues during development.

Key capabilities

  • Identifies code smells and anti-patterns
  • Suggests refactoring opportunities
  • Analyzes code complexity
  • Highlights areas for improved readability

Example prompts

  • "Analyze the following Python code for potential improvements: [code snippet]"
  • "Can you identify any areas of high complexity in this JavaScript function? [function code]"
  • "Review this Java class and suggest refactoring strategies to improve its design. [class code]"

Tips & gotchas

The skill's effectiveness depends on the clarity and completeness of the provided code. It is best used with well-formatted, reasonably sized code snippets for optimal analysis.