Skip to content
TrustedSkillsbeta
Back to all skills

Architecture Review

Checked
oimiragieo·vlatest·backend

Analyzes architectural designs for potential risks, inefficiencies, and adherence to best practices using AI-powered insights.

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 oimiragieo/agent-studio --skill architecture-review -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

oimiragieo

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 oimiragieo/agent-studio at 64b580eab2.

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

Commit
64b580eab2
Manifest
.claude/skills/architecture-review/SKILL.md
Scanned
10 files, 364 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 analyzes architectural designs for potential risks, inefficiencies, and adherence to best practices using AI-powered insights. It systematically evaluates codebases by gathering context (project structure, dependencies, data flow), assessing design principles (SOLID, DRY, YAGNI, Separation of Concerns), checking for anti-patterns (God Class/Module, Spaghetti Code, Circular Dependencies), and evaluating non-functional requirements (Scalability, Maintainability, Security). Finally, it generates a structured review report summarizing findings, strengths, concerns, recommendations, and potential trade-offs.

When to use it

  • When reviewing new architectural designs for a project.
  • To proactively identify potential issues in existing codebases.
  • During code reviews to provide more comprehensive feedback beyond basic syntax or logic errors.
  • To assess the scalability and maintainability of specific service layers (e.g., src/services/).
  • When seeking suggestions for improving architectural patterns and reducing technical debt.

Key capabilities

  • Architecture Context Gathering: Identifies project structure, key components, dependencies, and data flow.
  • Design Principle Evaluation: Checks adherence to SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion), DRY, YAGNI, and Separation of Concerns.
  • Anti-Pattern Detection: Identifies common anti-patterns like God Class/Module, Spaghetti Code, Circular Dependencies, and Leaky Abstractions.
  • Non-Functional Requirement Assessment: Evaluates the architecture against requirements for Scalability, Maintainability, Testability, Security, Performance, and Observability.
  • Report Generation: Creates a structured report with a summary, strengths, concerns (prioritized), recommendations, and trade-offs.

Example prompts

  • "Review the architecture of src/services/ for scalability and maintainability."
  • "Analyze this codebase for SOLID principle violations."
  • "Check this design for common anti-patterns like God Classes or Circular Dependencies."

Tips & gotchas

  • The skill relies on understanding the project's structure, so providing clear context is crucial.
  • Not all identified issues are equally important; prioritize based on your specific needs and constraints.
  • Consider the trade-offs involved in architectural changes – the skill will attempt to highlight these as well.