Skip to content
TrustedSkillsbeta
Back to all skills

Architecture Review

Checked
srstomp·vlatest·backend·MIT

Analyzes architectural designs for potential issues, suggesting improvements based on best practices and srstomp's expertise.

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 srstomp/pokayokay --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

srstomp

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 srstomp/pokayokay at ef6a34d63b.

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

Commit
ef6a34d63b
Manifest
plugins/pokayokay/skills/architecture-review/SKILL.md
Scanned
7 files, 3,103 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 project architectures to identify potential issues and suggest improvements based on established best practices. It focuses on key principles like clear boundaries, colocation of related code, and incremental migration strategies. The skill maps existing structures, identifies problems (such as circular dependencies or leaky abstractions), and proposes target architectures with actionable migration plans.

When to use it

  • When onboarding new developers to a project and needing to assess the codebase's navigability.
  • During refactoring efforts to ensure improvements align with best practices for maintainability.
  • To proactively identify architectural bottlenecks or areas of technical debt before they impact development velocity.
  • After significant feature additions to evaluate if the architecture remains sound.
  • When experiencing difficulties in maintaining a codebase due to complex dependencies or unclear structure.

Key capabilities

  • Maps project directory structures and dependency graphs.
  • Identifies issues like circular dependencies, "god modules," leaky abstractions, and deep nesting.
  • Classifies identified issues by severity (critical, high, medium/low).
  • Proposes target architectures with incremental migration plans.
  • Provides references to analysis techniques, refactoring patterns, structural patterns, and dependency management strategies.

Example prompts

  • "Analyze the current project structure and identify any circular dependencies."
  • "Assess this codebase for maintainability issues and suggest improvements based on best practices."
  • "Can you map out the directory structure and highlight areas with high complexity?"

Tips & gotchas

  • The skill relies on a clear understanding of the existing project structure. Providing initial context or documentation can improve accuracy.
  • The suggested migration plans are intended as guidance; thorough testing is crucial after each incremental change.
  • The skill focuses on structural aspects and may not cover all potential architectural concerns (e.g., performance, security).