本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(17)

  • SKILL.md6.2 KB
  • assets/expected_output_comparison.json1.9 KB
  • assets/sample_input_structured.json1.1 KB
  • assets/sample_input_tco.json1.1 KB
  • assets/sample_input_text.json237 B
  • references/examples.md10.3 KB
  • references/metrics.md6.5 KB
  • references/tool-reference.md15.4 KB
  • references/usage-and-criteria.md4.4 KB
  • references/workflows.md8.0 KB
  • scripts/ecosystem_analyzer.py16.1 KB
  • scripts/format_detector.py12.3 KB
  • scripts/migration_analyzer.py20.1 KB
  • scripts/report_generator.py15.5 KB
  • scripts/security_assessor.py17.3 KB
  • scripts/stack_comparator.py12.1 KB
  • scripts/tco_calculator.py15.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

ToolPurposeEntry point
stack_comparator.pyWeighted comparison across 8 categoriesfrom stack_comparator import StackComparator
tco_calculator.pyMulti-year TCO incl. hidden costsfrom tco_calculator import TCOCalculator
ecosystem_analyzer.pyEcosystem health & viability scoringfrom ecosystem_analyzer import EcosystemAnalyzer
security_assessor.pySecurity posture & compliance readinessfrom security_assessor import SecurityAssessor
migration_analyzer.pyMigration complexity, effort, risksfrom migration_analyzer import MigrationAnalyzer
report_generator.pyContext-aware report renderingfrom report_generator import ReportGenerator
format_detector.pyDetect/parse JSON, YAML, URL, or text inputfrom format_detector import FormatDetector

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

Scope & Limitations

Covers:

  • Weighted multi-criteria comparison of frameworks, libraries, and cloud providers
  • Multi-year TCO projections including hidden costs (technical debt, vendor lock-in, turnover)
  • Ecosystem viability assessment using GitHub, npm, and community metrics
  • Security posture scoring and compliance readiness for GDPR, SOC2, HIPAA, PCI-DSS

Does NOT cover:

  • Live data fetching from GitHub API, npm registry, or vulnerability databases (all data must be provided as input dictionaries)
  • Performance benchmarking or load testing (use engineering/senior-qa for test execution)
  • Licensing legal review or contract negotiation (use ra-qm-team compliance skills for regulatory guidance)
  • Team hiring or organizational design decisions (use hr-operations/talent-acquisition for staffing analysis)

Integration Points

SkillIntegrationData Flow
engineering/senior-securityFeed security assessor output into deeper vulnerability analysisSecurityAssessor results → security review input
engineering/senior-devopsUse TCO hosting projections to inform infrastructure planningTCOCalculator hosting/scaling data → DevOps capacity models
engineering/senior-qaMigration test coverage scores inform QA test planningMigrationAnalyzer testing_requirements → QA test strategy
ra-qm-team/compliance-auditorCompliance readiness gaps feed into formal audit preparationSecurityAssessor.assess_compliance() missing features → audit checklist
c-level-advisor/cto-advisorExecutive summaries and TCO reports support CTO decision-makingReportGenerator executive summary → strategic technology decisions
product-team/product-managerEcosystem viability and migration timelines inform product roadmapsEcosystemAnalyzer + MigrationAnalyzer → roadmap planning

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills8932026年10月7日 更新

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills8932026年10月7日 更新

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills8932026年10月7日 更新

Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills8932026年10月7日 更新

Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills8932026年10月7日 更新

aeo

無料

Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills8932026年10月7日 更新

borghei のスキルをすべて見る

このスキルの問題を報告する