Technology Stack Evaluator
Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/tech-stack-evaluator, including the files SKILL.md points to. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/engineering-team/skills/tech-stack-evaluator#main ~/.claude/skills/tech-stack-evaluatorFor one project only, change the path to .claude/skills/tech-stack-evaluator. This skill also uses Next.js, Angular.js, stack_comparator.py, tco_calculator.py, ecosystem_analyzer.py, security_assessor.py — copying SKILL.md alone won't be enough. See the folder on GitHub.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Technology Stack Evaluator
Show the full text185 lines
| name | description |
|---|---|
| tech-stack-evaluator | Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, evaluating technology stacks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability. |
Technology Stack Evaluator
Evaluate and compare technologies, frameworks, and cloud providers with data-driven analysis and actionable recommendations.
Table of Contents
Capabilities
| Capability | Description |
|---|---|
| Technology Comparison | Compare frameworks and libraries with weighted scoring |
| TCO Analysis | Calculate 5-year total cost including hidden costs |
| Ecosystem Health | Assess GitHub metrics, npm adoption, community strength |
| Security Assessment | Evaluate vulnerabilities and compliance readiness |
| Migration Analysis | Estimate effort, risks, and timeline for migrations |
| Cloud Comparison | Compare AWS, Azure, GCP for specific workloads |
Quick Start
Compare Two Technologies
Compare React vs Vue for a SaaS dashboard.
Priorities: developer productivity (40%), ecosystem (30%), performance (30%).
Calculate TCO
Calculate 5-year TCO for Next.js on Vercel.
Team: 8 developers. Hosting: $2500/month. Growth: 40%/year.
Assess Migration
Evaluate migrating from Angular.js to React.
Codebase: 50,000 lines, 200 components. Team: 6 developers.
Input Formats
The evaluator accepts three input formats:
Text - Natural language queries
Compare PostgreSQL vs MongoDB for our e-commerce platform.
YAML - Structured input for automation
comparison:
technologies: ["React", "Vue"]
use_case: "SaaS dashboard"
weights:
ecosystem: 30
performance: 25
developer_experience: 45
JSON - Programmatic integration
{
"technologies": ["React", "Vue"],
"use_case": "SaaS dashboard"
}
Analysis Types
Quick Comparison (200-300 tokens)
- Weighted scores and recommendation
- Top 3 decision factors
- Confidence level
Standard Analysis (500-800 tokens)
- Comparison matrix
- TCO overview
- Security summary
Full Report (1200-1500 tokens)
- All metrics and calculations
- Migration analysis
- Detailed recommendations
Scripts
stack_comparator.py
Compare technologies with customizable weighted criteria.
python scripts/stack_comparator.py --help
tco_calculator.py
Calculate total cost of ownership over multi-year projections.
python scripts/tco_calculator.py --input assets/sample_input_tco.json
ecosystem_analyzer.py
Analyze ecosystem health from GitHub, npm, and community metrics.
python scripts/ecosystem_analyzer.py --technology react
security_assessor.py
Evaluate security posture and compliance readiness.
python scripts/security_assessor.py --technology express --compliance soc2,gdpr
migration_analyzer.py
Estimate migration complexity, effort, and risks.
python scripts/migration_analyzer.py --from angular-1.x --to react
References
| Document | Content |
|---|---|
references/metrics.md |
Detailed scoring algorithms and calculation formulas |
references/examples.md |
Input/output examples for all analysis types |
references/workflows.md |
Step-by-step evaluation workflows |
Confidence Levels
| Level | Score | Interpretation |
|---|---|---|
| High | 80-100% | Clear winner, strong data |
| Medium | 50-79% | Trade-offs present, moderate uncertainty |
| Low | < 50% | Close call, limited data |
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)
| 1 | |
| 2 | name "tech-stack-evaluator" |
| 3 | description Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, evaluating technology stacks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability. |
| 4 | |
| 5 | |
| 6 | # Technology Stack Evaluator |
| 7 | |
| 8 | Evaluate and compare technologies, frameworks, and cloud providers with data-driven analysis and actionable recommendations. |
| 9 | |
| 10 | ## Table of Contents |
| 11 | |
| 12 | [Capabilities] |
| 13 | [Quick Start] |
| 14 | [Input Formats] |
| 15 | [Analysis Types] |
| 16 | [Scripts] |
| 17 | [References] |
| 18 | |
| 19 | |
| 20 | |
| 21 | ## Capabilities |
| 22 | |
| 23 | | Capability | Description | |
| 24 | |------------|-------------| |
| 25 | | Technology Comparison | Compare frameworks and libraries with weighted scoring | |
| 26 | | TCO Analysis | Calculate 5-year total cost including hidden costs | |
| 27 | | Ecosystem Health | Assess GitHub metrics, npm adoption, community strength | |
| 28 | | Security Assessment | Evaluate vulnerabilities and compliance readiness | |
| 29 | | Migration Analysis | Estimate effort, risks, and timeline for migrations | |
| 30 | | Cloud Comparison | Compare AWS, Azure, GCP for specific workloads | |
| 31 | |
| 32 | |
| 33 | |
| 34 | ## Quick Start |
| 35 | |
| 36 | ### Compare Two Technologies |
| 37 | |
| 38 | |
| 39 | Compare React vs Vue for a SaaS dashboard. |
| 40 | Priorities: developer productivity (40%), ecosystem (30%), performance (30%). |
| 41 | |
| 42 | |
| 43 | ### Calculate TCO |
| 44 | |
| 45 | |
| 46 | Calculate 5-year TCO for Next.js on Vercel. |
| 47 | Team: 8 developers. Hosting: $2500/month. Growth: 40%/year. |
| 48 | |
| 49 | |
| 50 | ### Assess Migration |
| 51 | |
| 52 | |
| 53 | Evaluate migrating from Angular.js to React. |
| 54 | Codebase: 50,000 lines, 200 components. Team: 6 developers. |
| 55 | |
| 56 | |
| 57 | |
| 58 | |
| 59 | ## Input Formats |
| 60 | |
| 61 | The evaluator accepts three input formats: |
| 62 | |
| 63 | **Text** - Natural language queries |
| 64 | |
| 65 | Compare PostgreSQL vs MongoDB for our e-commerce platform. |
| 66 | |
| 67 | |
| 68 | **YAML** - Structured input for automation |
| 69 | |
| 70 | comparison: |
| 71 | technologies: ["React", "Vue"] |
| 72 | use_case: "SaaS dashboard" |
| 73 | weights: |
| 74 | ecosystem: 30 |
| 75 | performance: 25 |
| 76 | developer_experience: 45 |
| 77 | |
| 78 | |
| 79 | **JSON** - Programmatic integration |
| 80 | |
| 81 | { |
| 82 | "technologies": ["React", "Vue"], |
| 83 | "use_case": "SaaS dashboard" |
| 84 | } |
| 85 | |
| 86 | |
| 87 | |
| 88 | |
| 89 | ## Analysis Types |
| 90 | |
| 91 | ### Quick Comparison (200-300 tokens) |
| 92 | Weighted scores and recommendation |
| 93 | Top 3 decision factors |
| 94 | Confidence level |
| 95 | |
| 96 | ### Standard Analysis (500-800 tokens) |
| 97 | Comparison matrix |
| 98 | TCO overview |
| 99 | Security summary |
| 100 | |
| 101 | ### Full Report (1200-1500 tokens) |
| 102 | All metrics and calculations |
| 103 | Migration analysis |
| 104 | Detailed recommendations |
| 105 | |
| 106 | |
| 107 | |
| 108 | ## Scripts |
| 109 | |
| 110 | ### stack_comparator.py |
| 111 | |
| 112 | Compare technologies with customizable weighted criteria. |
| 113 | |
| 114 | |
| 115 | python scripts/stack_comparator.py --help |
| 116 | |
| 117 | |
| 118 | ### tco_calculator.py |
| 119 | |
| 120 | Calculate total cost of ownership over multi-year projections. |
| 121 | |
| 122 | |
| 123 | python scripts/tco_calculator.py --input assets/sample_input_tco.json |
| 124 | |
| 125 | |
| 126 | ### ecosystem_analyzer.py |
| 127 | |
| 128 | Analyze ecosystem health from GitHub, npm, and community metrics. |
| 129 | |
| 130 | |
| 131 | python scripts/ecosystem_analyzer.py --technology react |
| 132 | |
| 133 | |
| 134 | ### security_assessor.py |
| 135 | |
| 136 | Evaluate security posture and compliance readiness. |
| 137 | |
| 138 | |
| 139 | python scripts/security_assessor.py --technology express --compliance soc2,gdpr |
| 140 | |
| 141 | |
| 142 | ### migration_analyzer.py |
| 143 | |
| 144 | Estimate migration complexity, effort, and risks. |
| 145 | |
| 146 | |
| 147 | python scripts/migration_analyzer.py --from angular-1.x --to react |
| 148 | |
| 149 | |
| 150 | |
| 151 | |
| 152 | ## References |
| 153 | |
| 154 | | Document | Content | |
| 155 | |----------|---------| |
| 156 | | `references/metrics.md` | Detailed scoring algorithms and calculation formulas | |
| 157 | | `references/examples.md` | Input/output examples for all analysis types | |
| 158 | | `references/workflows.md` | Step-by-step evaluation workflows | |
| 159 | |
| 160 | |
| 161 | |
| 162 | ## Confidence Levels |
| 163 | |
| 164 | | Level | Score | Interpretation | |
| 165 | |-------|-------|----------------| |
| 166 | | High | 80-100% | Clear winner, strong data | |
| 167 | | Medium | 50-79% | Trade-offs present, moderate uncertainty | |
| 168 | | Low | < 50% | Close call, limited data | |
| 169 | |
| 170 | |
| 171 | |
| 172 | ## When to Use |
| 173 | |
| 174 | Comparing frontend/backend frameworks for new projects |
| 175 | Evaluating cloud providers for specific workloads |
| 176 | Planning technology migrations with risk assessment |
| 177 | Calculating build vs. buy decisions with TCO |
| 178 | Assessing open-source library viability |
| 179 | |
| 180 | ## When NOT to Use |
| 181 | |
| 182 | Trivial decisions between similar tools (use team preference) |
| 183 | Mandated technology choices (decision already made) |
| 184 | Emergency production issues (use monitoring tools) |
| 185 |
Discussion
Browse more free Claude skills.