Skip to content
TrustedSkillsbeta
Back to all skills

Refactor Scan Tech Debt

Checked
cantagestudio·vlatest·backend

Identifies and prioritizes technical debt in backend codebases, suggesting refactoring opportunities for improved maintainability.

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 cantagestudio/cosmicatlaspacker --skill refactor-scan-tech-debt -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

cantagestudio

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 cantagestudio/cosmicatlaspacker at 686ead8da4.

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

Commit
686ead8da4
Manifest
.claude/skills/refactor-scan-tech-debt/SKILL.md
Scanned
2 files, 64 lines
Copies in repo
2 — all of them scanned
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 analyzes codebases to identify and flag potential technical debt. It provides insights into areas needing refactoring, helping developers prioritize improvements and maintain a clean, efficient codebase. The tool aims to surface patterns indicative of poor design or inefficient implementation that could impact future development velocity.

When to use it

  • Legacy Codebase Assessment: Quickly understand the scope of technical debt in an older project before starting major work.
  • Code Review Augmentation: Integrate into code review workflows to proactively identify and address potential issues.
  • Refactoring Prioritization: Determine which areas of a codebase would benefit most from refactoring efforts based on severity and impact.
  • Onboarding New Developers: Provide new team members with an overview of the technical landscape and areas for improvement.

Key capabilities

  • Technical debt identification
  • Codebase analysis
  • Refactoring suggestions

Example prompts

  • "Analyze this codebase (link to repository) and identify potential technical debt."
  • "Generate a report highlighting areas in this project that need refactoring."
  • "Scan this file (file path) for code smells and suggest improvements."

Tips & gotchas

The accuracy of the analysis depends on the quality and complexity of the codebase. Be prepared to review and validate the findings, as automated tools may occasionally produce false positives.