Skip to content
TrustedSkillsbeta
Back to all skills

Refactor Arch Hotspots

Checked
cantagestudio·vlatest·backend

Identifies and suggests architectural refactoring to address performance bottlenecks in backend codebases.

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-arch-hotspots -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-arch-hotspots/SKILL.md
Scanned
2 files, 70 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 identifies architectural hotspots within a codebase and suggests refactoring strategies. It analyzes code complexity, dependencies, and potential performance bottlenecks to pinpoint areas ripe for improvement. The goal is to enhance maintainability, readability, and overall system efficiency through targeted refactoring.

When to use it

  • Legacy Codebase Overhaul: When dealing with older systems that are difficult to understand or modify.
  • Performance Bottlenecks: To identify sections of code causing slowdowns or resource contention.
  • Technical Debt Reduction: As part of a broader effort to address accumulated technical debt and improve code quality.
  • Onboarding New Developers: To quickly highlight areas needing attention for new team members unfamiliar with the codebase.

Key capabilities

  • Code complexity analysis
  • Dependency graph generation
  • Performance bottleneck identification
  • Refactoring suggestion generation

Example prompts

  • "Analyze this code and identify architectural hotspots." (followed by providing a code snippet)
  • “Suggest refactorings for the 'payment_processing' module to improve performance.”
  • "Generate a dependency graph for the 'user_authentication' component."

Tips & gotchas

The skill requires access to the codebase being analyzed. Results are suggestions; manual review and testing are crucial before implementing any proposed refactoring changes.