Skip to content
TrustedSkillsbeta
Back to all skills

Tech Stack Evaluator

Checked
matteocervelli·vlatest·other·MIT

This skill analyzes your project's codebase to assess its tech stack, highlighting potential improvements and suggesting modern alternatives for efficiency.

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 matteocervelli/llms --skill tech-stack-evaluator --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Commit
1e1f2089eb
Manifest
.archive/claude-v1/skills/tech-stack-evaluator/SKILL.md
Scanned
3 files, 1,165 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

The tech-stack-evaluator skill analyzes and evaluates technology stacks based on provided descriptions or lists. It can assess a stack's suitability for specific projects, identify potential weaknesses, and suggest alternative technologies. The tool aims to provide objective assessments by considering factors like scalability, security, and maintainability.

When to use it

  • Project Planning: Determine the best technology stack for a new software project based on requirements and constraints.
  • Technology Selection: Evaluate different options when choosing between multiple frameworks or libraries.
  • Stack Optimization: Identify potential bottlenecks or areas for improvement within an existing technology stack.
  • Due Diligence: Assess the technical feasibility and risks associated with adopting a particular tech stack.

Key capabilities

  • Analyzes provided technology stacks.
  • Evaluates suitability for projects.
  • Identifies weaknesses in a given stack.
  • Suggests alternative technologies.

Example prompts

  • "Evaluate this tech stack: React, Node.js, PostgreSQL, AWS."
  • "What are the potential drawbacks of using Angular and Spring Boot for a large e-commerce platform?"
  • "I need a scalable backend for a mobile game. Suggest alternatives to Python/Django."

Tips & gotchas

The quality of the evaluation depends heavily on the clarity and completeness of the technology stack description provided in the prompt. Be as specific as possible about the intended use case or project requirements for more accurate results.