Agent skill · data analytics · borghei
tech-stack-evaluator
Evaluate and compare technology stacks with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability.
Why this skill is useful
Adds 7 executable Python modules for technology evaluation, including TCO analysis and security assessment that are not commonly found in public resources.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Technology Stack Evaluator Evaluate and compare technologies, frameworks, and cloud providers with data-driven, weighted analysis and actionable recommendations. Core Capabilities Technology comparison — weighted multi-criteria scoring of frameworks and libraries across 8 categories. TCO analysis — 5-year total cost of ownership including hidden costs (technical debt, vendor lock-in, turnover). Ecosystem health — viability scoring from GitHub, npm, community, and corporate-backing metrics. Security assessment — vulnerability/patch scoring and compliance readiness for GDPR, SOC2, HIPAA, PCI-DSS. Migration analysis — complexity, effort, risk, and recommended approach (direct/phased/strangler). Cloud comparison — compare AWS, Azure, GCP for specific workloads. When to Use Comparing frontend/backend frameworks for new projects Evaluating cloud providers for specific workloads Planning technology migrations with risk assessment Calculating build vs. buy decisions with TCO Assessing open-source library viability When NOT to use: trivial decisions between similar tools (use team preference), mandated technology choices (decision already made), emergency production issues (use monitoring tools). Clarify First Before the evaluation, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Candidates — the specific frameworks / libraries / cloud providers to compare (the subject of the analysis) [ ] Analysis type — comparison / TCO / ecosystem health / security / migration (selects which module runs) [ ] Decision criteria & weights — which of the 8 categories matter most for this context (drives the weighted scoring and recommendation) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Tools All scripts are Python library modules — import the class and call its methods. See references/tool-reference.md for full parameters and outputs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/tech-stack-evaluator