alirezarezvani/claude-skills

tech-stack-evaluator

Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/alirezarezvani/claude-skills --skill tech-stack-evaluator

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Technology Stack Evaluator

Evaluate and compare technologies, frameworks, and cloud providers with data-driven analysis and actionable recommendations.

Table of Contents


Capabilities

CapabilityDescription
Technology ComparisonCompare frameworks and libraries with weighted scoring
TCO AnalysisCalculate 5-year total cost including hidden costs
Ecosystem HealthAssess GitHub metrics, npm adoption, community strength
Security AssessmentEvaluate vulnerabilities and compliance readiness
Migration AnalysisEstimate effort, risks, and timeline for migrations
Cloud ComparisonCompare 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

yaml
comparison:
  technologies: ["React", "Vue"]
  use_case: "SaaS dashboard"
  weights:
    ecosystem: 30
    performance: 25
    developer_experience: 45

JSON - Programmatic integration

json
{
  "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.

bash
python scripts/stack_comparator.py --help

tco_calculator.py

Calculate total cost of ownership over multi-year projections.

bash
python scripts/tco_calculator.py --input assets/sample_input_tco.json

ecosystem_analyzer.py

Analyze ecosystem health from GitHub, npm, and community metrics.

bash
python scripts/ecosystem_analyzer.py --technology react

security_assessor.py

Evaluate security posture and compliance readiness.

bash
python scripts/security_assessor.py --technology express --compliance soc2,gdpr

migration_analyzer.py

Estimate migration complexity, effort, and risks.

bash
python scripts/migration_analyzer.py --from angular-1.x --to react

References

DocumentContent
references/metrics.mdDetailed scoring algorithms and calculation formulas
references/examples.mdInput/output examples for all analysis types
references/workflows.mdStep-by-step evaluation workflows

Confidence Levels

LevelScoreInterpretation
High80-100%Clear winner, strong data
Medium50-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)

Related by task

from this repository

More skills

All skills
alirezarezvani
Community

content-humanizer

Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).

installs
2
GitHub stars
28.7K
Updated
Oct 23
alirezarezvani
Community

analytics-tracking

Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, trac

installs
2
GitHub stars
28.7K
Updated
Oct 23
alirezarezvani
Community

campaign-analytics

Analyzes campaign performance with multi-touch attribution, funnel conversion analysis, and ROI calculation for marketing optimization. Use when analyzing marketing campaigns, ad performance, attribution models, conversion rates, or calculating marketing ROI, ROAS, CPA, and campaign metrics across channels.

installs
2
GitHub stars
28.7K
Updated
Oct 23
alirezarezvani
Community

marketing-context

Create and maintain the marketing context document that all marketing skills read before starting. Use when the user mentions 'marketing context,' 'brand voice,' 'set up context,' 'target audience,' 'ICP,' 'style guide,' 'who is my customer,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Run this at the start of any new project before using other marketing skills.

installs
2
GitHub stars
28.7K
Updated
Oct 23