[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F2ADMERCVNTY37Z8ZMAXP0":3,"skill-same:01M6F2ADMERCVNTY37Z8ZMAXP0":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6F2ADMERCVNTY37Z8ZMAXP0","tech-stack-evaluator",null,"Comprehensive technology stack evaluation and comparison tool with TCO analysis, security assessment, and intelligent recommendations for engineering teams","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Ftech-stack-evaluator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"stack","tech stack evaluator","evaluator","tech","security","assessment","teams","engineering","Evaluation","analysis","tool","security assessment","technology","recommendations","comparison","with","2026-11-10 10:12:30",false,"---\nname: tech-stack-evaluator\ndescription: Comprehensive technology stack evaluation and comparison tool with TCO analysis, security assessment, and intelligent recommendations for engineering teams\n---\n\n# Technology Stack Evaluator\n\nA comprehensive evaluation framework for comparing technologies, frameworks, cloud providers, and complete technology stacks. Provides data-driven recommendations with TCO analysis, security assessment, ecosystem health scoring, and migration path analysis.\n\n## Capabilities\n\nThis skill provides eight comprehensive evaluation capabilities:\n\n- **Technology Comparison**: Head-to-head comparisons of frameworks, languages, and tools (React vs Vue, PostgreSQL vs MongoDB, Node.js vs Python)\n- **Stack Evaluation**: Assess complete technology stacks for specific use cases (real-time collaboration, API-heavy SaaS, data-intensive platforms)\n- **Maturity & Ecosystem Analysis**: Evaluate community health, maintenance status, long-term viability, and ecosystem strength\n- **Total Cost of Ownership (TCO)**: Calculate comprehensive costs including licensing, hosting, developer productivity, and scaling\n- **Security & Compliance**: Analyze vulnerabilities, compliance readiness (GDPR, SOC2, HIPAA), and security posture\n- **Migration Path Analysis**: Assess migration complexity, risks, timelines, and strategies from legacy to modern stacks\n- **Cloud Provider Comparison**: Compare AWS vs Azure vs GCP for specific workloads with cost and feature analysis\n- **Decision Reports**: Generate comprehensive decision matrices with pros\u002Fcons, confidence scores, and actionable recommendations\n\n## Input Requirements\n\n### Flexible Input Formats (Automatic Detection)\n\nThe skill automatically detects and processes multiple input formats:\n\n**Text\u002FConversational**:\n```\n\"Compare React vs Vue for building a SaaS dashboard\"\n\"Evaluate technology stack for real-time collaboration platform\"\n\"Should we migrate from MongoDB to PostgreSQL?\"\n```\n\n**Structured (YAML)**:\n```yaml\ncomparison:\n  technologies:\n    - name: \"React\"\n    - name: \"Vue\"\n  use_case: \"SaaS dashboard\"\n  priorities:\n    - \"Developer productivity\"\n    - \"Ecosystem maturity\"\n    - \"Performance\"\n```\n\n**Structured (JSON)**:\n```json\n{\n  \"comparison\": {\n    \"technologies\": [\"React\", \"Vue\"],\n    \"use_case\": \"SaaS dashboard\",\n    \"priorities\": [\"Developer productivity\", \"Ecosystem maturity\"]\n  }\n}\n```\n\n**URLs for Ecosystem Analysis**:\n- GitHub repository URLs (for health scoring)\n- npm package URLs (for download statistics)\n- Technology documentation URLs (for feature extraction)\n\n### Analysis Scope Selection\n\nUsers can select which analyses to run:\n- **Quick Comparison**: Basic scoring and comparison (200-300 tokens)\n- **Standard Analysis**: Scoring + TCO + Security (500-800 tokens)\n- **Comprehensive Report**: All analyses including migration paths (1200-1500 tokens)\n- **Custom**: User selects specific sections (modular)\n\n## Output Formats\n\n### Context-Aware Output\n\nThe skill automatically adapts output based on environment:\n\n**Claude Desktop (Rich Markdown)**:\n- Formatted tables with color indicators\n- Expandable sections for detailed analysis\n- Visual decision matrices\n- Charts and graphs (when appropriate)\n\n**CLI\u002FTerminal (Terminal-Friendly)**:\n- Plain text tables with ASCII borders\n- Compact formatting\n- Clear section headers\n- Copy-paste friendly code blocks\n\n### Progressive Disclosure Structure\n\n**Executive Summary (200-300 tokens)**:\n- Recommendation summary\n- Top 3 pros and cons\n- Confidence level (High\u002FMedium\u002FLow)\n- Key decision factors\n\n**Detailed Breakdown (on-demand)**:\n- Complete scoring matrices\n- Detailed TCO calculations\n- Full security analysis\n- Migration complexity assessment\n- All supporting data and calculations\n\n### Report Sections (User-Selectable)\n\nUsers choose which sections to include:\n\n1. **Scoring & Comparison Matrix**\n   - Weighted decision scores\n   - Head-to-head comparison tables\n   - Strengths and weaknesses\n\n2. **Financial Analysis**\n   - TCO breakdown (5-year projection)\n   - ROI analysis\n   - Cost per user\u002Frequest metrics\n   - Hidden cost identification\n\n3. **Ecosystem Health**\n   - Community size and activity\n   - GitHub stars, npm downloads\n   - Release frequency and maintenance\n   - Issue response times\n   - Viability assessment\n\n4. **Security & Compliance**\n   - Vulnerability count (CVE database)\n   - Security patch frequency\n   - Compliance readiness (GDPR, SOC2, HIPAA)\n   - Security scoring\n\n5. **Migration Analysis** (when applicable)\n   - Migration complexity scoring\n   - Code change estimates\n   - Data migration requirements\n   - Downtime assessment\n   - Risk mitigation strategies\n\n6. **Performance Benchmarks**\n   - Throughput\u002Flatency comparisons\n   - Resource usage analysis\n   - Scalability characteristics\n\n## How to Use\n\n### Basic Invocations\n\n**Quick Comparison**:\n```\n\"Compare React vs Vue for our SaaS dashboard project\"\n\"PostgreSQL vs MongoDB for our application\"\n```\n\n**Stack Evaluation**:\n```\n\"Evaluate technology stack for real-time collaboration platform:\nNode.js, WebSockets, Redis, PostgreSQL\"\n```\n\n**TCO Analysis**:\n```\n\"Calculate total cost of ownership for AWS vs Azure for our workload:\n- 50 EC2\u002FVM instances\n- 10TB storage\n- High bandwidth requirements\"\n```\n\n**Security Assessment**:\n```\n\"Analyze security posture of our current stack:\nExpress.js, MongoDB, JWT authentication.\nNeed SOC2 compliance.\"\n```\n\n**Migration Path**:\n```\n\"Assess migration from Angular.js (1.x) to React.\nApplication has 50,000 lines of code, 200 components.\"\n```\n\n### Advanced Invocations\n\n**Custom Analysis Sections**:\n```\n\"Compare Next.js vs Nuxt.js.\nInclude: Ecosystem health, TCO, and performance benchmarks.\nSkip: Migration analysis, compliance.\"\n```\n\n**Weighted Decision Criteria**:\n```\n\"Compare cloud providers for ML workloads.\nPriorities (weighted):\n- GPU availability (40%)\n- Cost (30%)\n- Ecosystem (20%)\n- Support (10%)\"\n```\n\n**Multi-Technology Comparison**:\n```\n\"Compare: React, Vue, Svelte, Angular for enterprise SaaS.\nUse case: Large team (20+ developers), complex state management.\nGenerate comprehensive decision matrix.\"\n```\n\n## Scripts\n\n### Core Modules\n\n- **`stack_comparator.py`**: Main comparison engine with weighted scoring algorithms\n- **`tco_calculator.py`**: Total Cost of Ownership calculations (licensing, hosting, developer productivity, scaling)\n- **`ecosystem_analyzer.py`**: Community health scoring, GitHub\u002Fnpm metrics, viability assessment\n- **`security_assessor.py`**: Vulnerability analysis, compliance readiness, security scoring\n- **`migration_analyzer.py`**: Migration complexity scoring, risk assessment, effort estimation\n- **`format_detector.py`**: Automatic input format detection (text, YAML, JSON, URLs)\n- **`report_generator.py`**: Context-aware report generation with progressive disclosure\n\n### Utility Modules\n\n- **`data_fetcher.py`**: Fetch real-time data from GitHub, npm, CVE databases\n- **`benchmark_processor.py`**: Process and normalize performance benchmark data\n- **`confidence_scorer.py`**: Calculate confidence levels for recommendations\n\n## Metrics and Calculations\n\n### 1. Scoring & Comparison Metrics\n\n**Technology Comparison Matrix**:\n- Feature completeness (0-100 scale)\n- Learning curve assessment (Easy\u002FMedium\u002FHard)\n- Developer experience scoring\n- Documentation quality (0-10 scale)\n- Weighted total scores\n\n**Decision Scoring Algorithm**:\n- User-defined weights for criteria\n- Normalized scoring (0-100)\n- Confidence intervals\n- Sensitivity analysis\n\n### 2. Financial Calculations\n\n**TCO Components**:\n- **Initial Costs**: Licensing, training, migration\n- **Operational Costs**: Hosting, support, maintenance (monthly\u002Fyearly)\n- **Scaling Costs**: Per-user costs, infrastructure scaling projections\n- **Developer Productivity**: Time-to-market impact, development speed multipliers\n- **Hidden Costs**: Technical debt, vendor lock-in risks\n\n**ROI Calculations**:\n- Cost savings projections (3-year, 5-year)\n- Productivity gains (developer hours saved)\n- Break-even analysis\n- Risk-adjusted returns\n\n**Cost Per Metric**:\n- Cost per user (monthly\u002Fyearly)\n- Cost per API request\n- Cost per GB stored\u002Ftransferred\n- Cost per compute hour\n\n### 3. Maturity & Ecosystem Metrics\n\n**Health Scoring (0-100 scale)**:\n- **GitHub Metrics**: Stars, forks, contributors, commit frequency\n- **npm Metrics**: Weekly downloads, version stability, dependency count\n- **Release Cadence**: Regular releases, semantic versioning adherence\n- **Issue Management**: Response time, resolution rate, open vs closed issues\n\n**Community Metrics**:\n- Active maintainers count\n- Contributor growth rate\n- Stack Overflow question volume\n- Job market demand (job postings analysis)\n\n**Viability Assessment**:\n- Corporate backing strength\n- Community sustainability\n- Alternative availability\n- Long-term risk scoring\n\n### 4. Security & Compliance Metrics\n\n**Security Scoring**:\n- **CVE Count**: Known vulnerabilities (last 12 months, last 3 years)\n- **Severity Distribution**: Critical\u002FHigh\u002FMedium\u002FLow vulnerability counts\n- **Patch Frequency**: Average time to patch (days)\n- **Security Track Record**: Historical security posture\n\n**Compliance Readiness**:\n- **GDPR**: Data privacy features, consent management, data portability\n- **SOC2**: Access controls, encryption, audit logging\n- **HIPAA**: PHI handling, encryption standards, access controls\n- **PCI-DSS**: Payment data security (if applicable)\n\n**Compliance Scoring (per standard)**:\n- Ready: 90-100% compliant\n- Mostly Ready: 70-89% (minor gaps)\n- Partial: 50-69% (significant work needed)\n- Not Ready: \u003C50% (major gaps)\n\n### 5. Migration Analysis Metrics\n\n**Complexity Scoring (1-10 scale)**:\n- **Code Changes**: Estimated lines of code affected\n- **Architecture Impact**: Breaking changes, API compatibility\n- **Data Migration**: Schema changes, data transformation complexity\n- **Downtime Requirements**: Zero-downtime possible vs planned outage\n\n**Effort Estimation**:\n- Development hours (by component)\n- Testing hours\n- Training hours\n- Total person-months\n\n**Risk Assessment**:\n- **Technical Risks**: API incompatibilities, performance regressions\n- **Business Risks**: Downtime impact, feature parity gaps\n- **Team Risks**: Learning curve, skill gaps\n- **Mitigation Strategies**: Risk-specific recommendations\n\n**Migration Phases**:\n- Phase 1: Planning and prototyping (timeline, effort)\n- Phase 2: Core migration (timeline, effort)\n- Phase 3: Testing and validation (timeline, effort)\n- Phase 4: Deployment and monitoring (timeline, effort)\n\n### 6. Performance Benchmark Metrics\n\n**Throughput\u002FLatency**:\n- Requests per second (RPS)\n- Average response time (ms)\n- P95\u002FP99 latency percentiles\n- Concurrent user capacity\n\n**Resource Usage**:\n- Memory consumption (MB\u002FGB)\n- CPU utilization (%)\n- Storage requirements\n- Network bandwidth\n\n**Scalability Characteristics**:\n- Horizontal scaling efficiency\n- Vertical scaling limits\n- Cost per performance unit\n- Scaling inflection points\n\n## Best Practices\n\n### For Accurate Evaluations\n\n1. **Define Clear Use Case**: Specify exact requirements, constraints, and priorities\n2. **Provide Complete Context**: Team size, existing stack, timeline, budget constraints\n3. **Set Realistic Priorities**: Use weighted criteria (total = 100%) for multi-factor decisions\n4. **Consider Team Skills**: Factor in learning curve and existing expertise\n5. **Think Long-Term**: Evaluate 3-5 year outlook, not just immediate needs\n\n### For TCO Analysis\n\n1. **Include All Cost Components**: Don't forget training, migration, technical debt\n2. **Use Realistic Scaling Projections**: Base on actual growth metrics, not wishful thinking\n3. **Account for Developer Productivity**: Time-to-market and development speed are critical costs\n4. **Consider Hidden Costs**: Vendor lock-in, exit costs, technical debt accumulation\n5. **Validate Assumptions**: Document all TCO assumptions for review\n\n### For Migration Decisions\n\n1. **Start with Risk Assessment**: Identify showstoppers early\n2. **Plan Incremental Migration**: Avoid big-bang rewrites when possible\n3. **Prototype Critical Paths**: Test complex migration scenarios before committing\n4. **Build Rollback Plans**: Always have a fallback strategy\n5. **Measure Baseline Performance**: Establish current metrics before migration\n\n### For Security Evaluation\n\n1. **Check Recent Vulnerabilities**: Focus on last 12 months for current security posture\n2. **Review Patch Response Time**: Fast patching is more important than zero vulnerabilities\n3. **Validate Compliance Claims**: Vendor claims ≠ actual compliance readiness\n4. **Consider Supply Chain**: Evaluate security of all dependencies\n5. **Test Security Features**: Don't assume features work as documented\n\n## Limitations\n\n### Data Accuracy\n\n- **Ecosystem metrics** are point-in-time snapshots (GitHub stars, npm downloads change rapidly)\n- **TCO calculations** are estimates based on provided assumptions and market rates\n- **Benchmark data** may not reflect your specific use case or configuration\n- **Security vulnerability counts** depend on public CVE database completeness\n\n### Scope Boundaries\n\n- **Industry-Specific Requirements**: Some specialized industries may have unique constraints not covered by standard analysis\n- **Emerging Technologies**: Very new technologies (\u003C1 year old) may lack sufficient data for accurate assessment\n- **Custom\u002FProprietary Solutions**: Cannot evaluate closed-source or internal tools without data\n- **Political\u002FOrganizational Factors**: Cannot account for company politics, vendor relationships, or legacy commitments\n\n### Contextual Limitations\n\n- **Team Skill Assessment**: Cannot directly evaluate your team's specific skills and learning capacity\n- **Existing Architecture**: Recommendations assume greenfield unless migration context provided\n- **Budget Constraints**: TCO analysis provides costs but cannot make budget decisions for you\n- **Timeline Pressure**: Cannot account for business deadlines and time-to-market urgency\n\n### When NOT to Use This Skill\n\n- **Trivial Decisions**: Choosing between nearly-identical tools (use team preference)\n- **Mandated Solutions**: When technology choice is already decided by management\u002Fpolicy\n- **Insufficient Context**: When you don't know your requirements, priorities, or constraints\n- **Real-Time Production Decisions**: Use for planning, not emergency production issues\n- **Non-Technical Decisions**: Business strategy, hiring, organizational issues\n\n## Confidence Levels\n\nThe skill provides confidence scores with all recommendations:\n\n- **High Confidence (80-100%)**: Strong data, clear winner, low risk\n- **Medium Confidence (50-79%)**: Good data, trade-offs present, moderate risk\n- **Low Confidence (\u003C50%)**: Limited data, close call, high uncertainty\n- **Insufficient Data**: Cannot make recommendation without more information\n\nConfidence is based on:\n- Data completeness and recency\n- Consensus across multiple metrics\n- Clarity of use case requirements\n- Industry maturity and standards\n\n","# Technology Stack Evaluator\n\nA comprehensive evaluation framework for comparing technologies, frameworks, cloud providers, and complete technology stacks. Provides data-driven recommendations with TCO analysis, security assessment, ecosystem health scoring, and migration path analysis.\n\n## Capabilities\n\nThis skill provides eight comprehensive evaluation capabilities:\n\n- **Technology Comparison**: Head-to-head comparisons of frameworks, languages, and tools (React vs Vue, PostgreSQL vs MongoDB, Node.js vs Python)\n- **Stack Evaluation**: Assess complete technology stacks for specific use cases (real-time collaboration, API-heavy SaaS, data-intensive platforms)\n- **Maturity & Ecosystem Analysis**: Evaluate community health, maintenance status, long-term viability, and ecosystem strength\n- **Total Cost of Ownership (TCO)**: Calculate comprehensive costs including licensing, hosting, developer productivity, and scaling\n- **Security & Compliance**: Analyze vulnerabilities, compliance readiness (GDPR, SOC2, HIPAA), and security posture\n- **Migration Path Analysis**: Assess migration complexity, risks, timelines, and strategies from legacy to modern stacks\n- **Cloud Provider Comparison**: Compare AWS vs Azure vs GCP for specific workloads with cost and feature analysis\n- **Decision Reports**: Generate comprehensive decision matrices with pros\u002Fcons, confidence scores, and actionable recommendations\n\n## Input Requirements\n\n### Flexible Input Formats (Automatic Detection)\n\nThe skill automatically detects and processes multiple input formats:\n\n**Text\u002FConversational**:\n```\n\"Compare React vs Vue for building a SaaS dashboard\"\n\"Evaluate technology stack for real-time collaboration platform\"\n\"Should we migrate from MongoDB to PostgreSQL?\"\n```\n\n**Structured (YAML)**:\n```yaml\ncomparison:\n  technologies:\n    - name: \"React\"\n    - name: \"Vue\"\n  use_case: \"SaaS dashboard\"\n  priorities:\n    - \"Developer productivity\"\n    - \"Ecosystem maturity\"\n    - \"Performance\"\n```\n\n**Structured (JSON)**:\n```json\n{\n  \"comparison\": {\n    \"technologies\": [\"React\", \"Vue\"],\n    \"use_case\": \"SaaS dashboard\",\n    \"priorities\": [\"Developer productivity\", \"Ecosystem maturity\"]\n  }\n}\n```\n\n**URLs for Ecosystem Analysis**:\n- GitHub repository URLs (for health scoring)\n- npm package URLs (for download statistics)\n- Technology documentation URLs (for feature extraction)\n\n### Analysis Scope Selection\n\nUsers can select which analyses to run:\n- **Quick Comparison**: Basic scoring and comparison (200-300 tokens)\n- **Standard Analysis**: Scoring + TCO + Security (500-800 tokens)\n- **Comprehensive Report**: All analyses including migration paths (1200-1500 tokens)\n- **Custom**: User selects specific sections (modular)\n\n## Output Formats\n\n### Context-Aware Output\n\nThe skill automatically adapts output based on environment:\n\n**Claude Desktop (Rich Markdown)**:\n- Formatted tables with color indicators\n- Expandable sections for detailed analysis\n- Visual decision matrices\n- Charts and graphs (when appropriate)\n\n**CLI\u002FTerminal (Terminal-Friendly)**:\n- Plain text tables with ASCII borders\n- Compact formatting\n- Clear section headers\n- Copy-paste friendly code blocks\n\n### Progressive Disclosure Structure\n\n**Executive Summary (200-300 tokens)**:\n- Recommendation summary\n- Top 3 pros and cons\n- Confidence level (High\u002FMedium\u002FLow)\n- Key decision factors\n\n**Detailed Breakdown (on-demand)**:\n- Complete scoring matrices\n- Detailed TCO calculations\n- Full security analysis\n- Migration complexity assessment\n- All supporting data and calculations\n\n### Report Sections (User-Selectable)\n\nUsers choose which sections to include:\n\n1. **Scoring & Comparison Matrix**\n   - Weighted decision scores\n   - Head-to-head comparison tables\n   - Strengths and weaknesses\n\n2. **Financial Analysis**\n   - TCO breakdown (5-year projection)\n   - ROI analysis\n   - Cost per user\u002Frequest metrics\n   - Hidden cost identification\n\n3. **Ecosystem Health**\n   - Community size and activity\n   - GitHub stars, npm downloads\n   - Release frequency and maintenance\n   - Issue response times\n   - Viability assessment\n\n4. **Security & Compliance**\n   - Vulnerability count (CVE database)\n   - Security patch frequency\n   - Compliance readiness (GDPR, SOC2, HIPAA)\n   - Security scoring\n\n5. **Migration Analysis** (when applicable)\n   - Migration complexity scoring\n   - Code change estimates\n   - Data migration requirements\n   - Downtime assessment\n   - Risk mitigation strategies\n\n6. **Performance Benchmarks**\n   - Throughput\u002Flatency comparisons\n   - Resource usage analysis\n   - Scalability characteristics\n\n## How to Use\n\n### Basic Invocations\n\n**Quick Comparison**:\n```\n\"Compare React vs Vue for our SaaS dashboard project\"\n\"PostgreSQL vs MongoDB for our application\"\n```\n\n**Stack Evaluation**:\n```\n\"Evaluate technology stack for real-time collaboration platform:\nNode.js, WebSockets, Redis, PostgreSQL\"\n```\n\n**TCO Analysis**:\n```\n\"Calculate total cost of ownership for AWS vs Azure for our workload:\n- 50 EC2\u002FVM instances\n- 10TB storage\n- High bandwidth requirements\"\n```\n\n**Security Assessment**:\n```\n\"Analyze security posture of our current stack:\nExpress.js, MongoDB, JWT authentication.\nNeed SOC2 compliance.\"\n```\n\n**Migration Path**:\n```\n\"Assess migration from Angular.js (1.x) to React.\nApplication has 50,000 lines of code, 200 components.\"\n```\n\n### Advanced Invocations\n\n**Custom Analysis Sections**:\n```\n\"Compare Next.js vs Nuxt.js.\nInclude: Ecosystem health, TCO, and performance benchmarks.\nSkip: Migration analysis, compliance.\"\n```\n\n**Weighted Decision Criteria**:\n```\n\"Compare cloud providers for ML workloads.\nPriorities (weighted):\n- GPU availability (40%)\n- Cost (30%)\n- Ecosystem (20%)\n- Support (10%)\"\n```\n\n**Multi-Technology Comparison**:\n```\n\"Compare: React, Vue, Svelte, Angular for enterprise SaaS.\nUse case: Large team (20+ developers), complex state management.\nGenerate comprehensive decision matrix.\"\n```\n\n## Scripts\n\n### Core Modules\n\n- **`stack_comparator.py`**: Main comparison engine with weighted scoring algorithms\n- **`tco_calculator.py`**: Total Cost of Ownership calculations (licensing, hosting, developer productivity, scaling)\n- **`ecosystem_analyzer.py`**: Community health scoring, GitHub\u002Fnpm metrics, viability assessment\n- **`security_assessor.py`**: Vulnerability analysis, compliance readiness, security scoring\n- **`migration_analyzer.py`**: Migration complexity scoring, risk assessment, effort estimation\n- **`format_detector.py`**: Automatic input format detection (text, YAML, JSON, URLs)\n- **`report_generator.py`**: Context-aware report generation with progressive disclosure\n\n### Utility Modules\n\n- **`data_fetcher.py`**: Fetch real-time data from GitHub, npm, CVE databases\n- **`benchmark_processor.py`**: Process and normalize performance benchmark data\n- **`confidence_scorer.py`**: Calculate confidence levels for recommendations\n\n## Metrics and Calculations\n\n### 1. Scoring & Comparison Metrics\n\n**Technology Comparison Matrix**:\n- Feature completeness (0-100 scale)\n- Learning curve assessment (Easy\u002FMedium\u002FHard)\n- Developer experience scoring\n- Documentation quality (0-10 scale)\n- Weighted total scores\n\n**Decision Scoring Algorithm**:\n- User-defined weights for criteria\n- Normalized scoring (0-100)\n- Confidence intervals\n- Sensitivity analysis\n\n### 2. Financial Calculations\n\n**TCO Components**:\n- **Initial Costs**: Licensing, training, migration\n- **Operational Costs**: Hosting, support, maintenance (monthly\u002Fyearly)\n- **Scaling Costs**: Per-user costs, infrastructure scaling projections\n- **Developer Productivity**: Time-to-market impact, development speed multipliers\n- **Hidden Costs**: Technical debt, vendor lock-in risks\n\n**ROI Calculations**:\n- Cost savings projections (3-year, 5-year)\n- Productivity gains (developer hours saved)\n- Break-even analysis\n- Risk-adjusted returns\n\n**Cost Per Metric**:\n- Cost per user (monthly\u002Fyearly)\n- Cost per API request\n- Cost per GB stored\u002Ftransferred\n- Cost per compute hour\n\n### 3. Maturity & Ecosystem Metrics\n\n**Health Scoring (0-100 scale)**:\n- **GitHub Metrics**: Stars, forks, contributors, commit frequency\n- **npm Metrics**: Weekly downloads, version stability, dependency count\n- **Release Cadence**: Regular releases, semantic versioning adherence\n- **Issue Management**: Response time, resolution rate, open vs closed issues\n\n**Community Metrics**:\n- Active maintainers count\n- Contributor growth rate\n- Stack Overflow question volume\n- Job market demand (job postings analysis)\n\n**Viability Assessment**:\n- Corporate backing strength\n- Community sustainability\n- Alternative availability\n- Long-term risk scoring\n\n### 4. Security & Compliance Metrics\n\n**Security Scoring**:\n- **CVE Count**: Known vulnerabilities (last 12 months, last 3 years)\n- **Severity Distribution**: Critical\u002FHigh\u002FMedium\u002FLow vulnerability counts\n- **Patch Frequency**: Average time to patch (days)\n- **Security Track Record**: Historical security posture\n\n**Compliance Readiness**:\n- **GDPR**: Data privacy features, consent management, data portability\n- **SOC2**: Access controls, encryption, audit logging\n- **HIPAA**: PHI handling, encryption standards, access controls\n- **PCI-DSS**: Payment data security (if applicable)\n\n**Compliance Scoring (per standard)**:\n- Ready: 90-100% compliant\n- Mostly Ready: 70-89% (minor gaps)\n- Partial: 50-69% (significant work needed)\n- Not Ready: \u003C50% (major gaps)\n\n### 5. Migration Analysis Metrics\n\n**Complexity Scoring (1-10 scale)**:\n- **Code Changes**: Estimated lines of code affected\n- **Architecture Impact**: Breaking changes, API compatibility\n- **Data Migration**: Schema changes, data transformation complexity\n- **Downtime Requirements**: Zero-downtime possible vs planned outage\n\n**Effort Estimation**:\n- Development hours (by component)\n- Testing hours\n- Training hours\n- Total person-months\n\n**Risk Assessment**:\n- **Technical Risks**: API incompatibilities, performance regressions\n- **Business Risks**: Downtime impact, feature parity gaps\n- **Team Risks**: Learning curve, skill gaps\n- **Mitigation Strategies**: Risk-specific recommendations\n\n**Migration Phases**:\n- Phase 1: Planning and prototyping (timeline, effort)\n- Phase 2: Core migration (timeline, effort)\n- Phase 3: Testing and validation (timeline, effort)\n- Phase 4: Deployment and monitoring (timeline, effort)\n\n### 6. Performance Benchmark Metrics\n\n**Throughput\u002FLatency**:\n- Requests per second (RPS)\n- Average response time (ms)\n- P95\u002FP99 latency percentiles\n- Concurrent user capacity\n\n**Resource Usage**:\n- Memory consumption (MB\u002FGB)\n- CPU utilization (%)\n- Storage requirements\n- Network bandwidth\n\n**Scalability Characteristics**:\n- Horizontal scaling efficiency\n- Vertical scaling limits\n- Cost per performance unit\n- Scaling inflection points\n\n## Best Practices\n\n### For Accurate Evaluations\n\n1. **Define Clear Use Case**: Specify exact requirements, constraints, and priorities\n2. **Provide Complete Context**: Team size, existing stack, timeline, budget constraints\n3. **Set Realistic Priorities**: Use weighted criteria (total = 100%) for multi-factor decisions\n4. **Consider Team Skills**: Factor in learning curve and existing expertise\n5. **Think Long-Term**: Evaluate 3-5 year outlook, not just immediate needs\n\n### For TCO Analysis\n\n1. **Include All Cost Components**: Don't forget training, migration, technical debt\n2. **Use Realistic Scaling Projections**: Base on actual growth metrics, not wishful thinking\n3. **Account for Developer Productivity**: Time-to-market and development speed are critical costs\n4. **Consider Hidden Costs**: Vendor lock-in, exit costs, technical debt accumulation\n5. **Validate Assumptions**: Document all TCO assumptions for review\n\n### For Migration Decisions\n\n1. **Start with Risk Assessment**: Identify showstoppers early\n2. **Plan Incremental Migration**: Avoid big-bang rewrites when possible\n3. **Prototype Critical Paths**: Test complex migration scenarios before committing\n4. **Build Rollback Plans**: Always have a fallback strategy\n5. **Measure Baseline Performance**: Establish current metrics before migration\n\n### For Security Evaluation\n\n1. **Check Recent Vulnerabilities**: Focus on last 12 months for current security posture\n2. **Review Patch Response Time**: Fast patching is more important than zero vulnerabilities\n3. **Validate Compliance Claims**: Vendor claims ≠ actual compliance readiness\n4. **Consider Supply Chain**: Evaluate security of all dependencies\n5. **Test Security Features**: Don't assume features work as documented\n\n## Limitations\n\n### Data Accuracy\n\n- **Ecosystem metrics** are point-in-time snapshots (GitHub stars, npm downloads change rapidly)\n- **TCO calculations** are estimates based on provided assumptions and market rates\n- **Benchmark data** may not reflect your specific use case or configuration\n- **Security vulnerability counts** depend on public CVE database completeness\n\n### Scope Boundaries\n\n- **Industry-Specific Requirements**: Some specialized industries may have unique constraints not covered by standard analysis\n- **Emerging Technologies**: Very new technologies (\u003C1 year old) may lack sufficient data for accurate assessment\n- **Custom\u002FProprietary Solutions**: Cannot evaluate closed-source or internal tools without data\n- **Political\u002FOrganizational Factors**: Cannot account for company politics, vendor relationships, or legacy commitments\n\n### Contextual Limitations\n\n- **Team Skill Assessment**: Cannot directly evaluate your team's specific skills and learning capacity\n- **Existing Architecture**: Recommendations assume greenfield unless migration context provided\n- **Budget Constraints**: TCO analysis provides costs but cannot make budget decisions for you\n- **Timeline Pressure**: Cannot account for business deadlines and time-to-market urgency\n\n### When NOT to Use This Skill\n\n- **Trivial Decisions**: Choosing between nearly-identical tools (use team preference)\n- **Mandated Solutions**: When technology choice is already decided by management\u002Fpolicy\n- **Insufficient Context**: When you don't know your requirements, priorities, or constraints\n- **Real-Time Production Decisions**: Use for planning, not emergency production issues\n- **Non-Technical Decisions**: Business strategy, hiring, organizational issues\n\n## Confidence Levels\n\nThe skill provides confidence scores with all recommendations:\n\n- **High Confidence (80-100%)**: Strong data, clear winner, low risk\n- **Medium Confidence (50-79%)**: Good data, trade-offs present, moderate risk\n- **Low Confidence (\u003C50%)**: Limited data, close call, high uncertainty\n- **Insufficient Data**: Cannot make recommendation without more information\n\nConfidence is based on:\n- Data completeness and recency\n- Consensus across multiple metrics\n- Clarity of use case requirements\n- Industry maturity and standards\n\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Ftech-stack-evaluator",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill tech-stack-evaluator",{"tool":55,"command":56},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill tech-stack-evaluator",{"tool":58,"command":59},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill tech-stack-evaluator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Ftech-stack-evaluator\u002FSKILL.md",true,[],[64,78,88,97,103,110],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":74,"publishedAt":35},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[75,76,77],"model","model hierarchy","model hierarchy skill",{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":84,"publishedAt":35},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[83],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[85,86,87],"MCP","zoom","zoom mcp",{"skillNo":89,"name":90,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":35},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[94,95,96,86],"sdk","zoom apps sdk","apps",{"skillNo":98,"name":99,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":35},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[99],{"skillNo":104,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":35},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[108],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[105],{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":35},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[112]]