Technology choices often hide tradeoffs across performance, cost, reliability, operations, and team readiness. This skill compares candidates, recommends an option, and defines proof-of-concept checks.
Review the Skillstore skill "arch-tech-evaluation" from https://skillstore.io/skills/zl2023github-arch-tech-evaluation.md and its manifest at https://skillstore.io/api/skills/zl2023github-arch-tech-evaluation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
「arch-tech-evaluation」を使用しています。 Compare Kafka and RabbitMQ for order events at 100,000 messages per second.
期待される結果:
**Recommendation: Kafka.** It better matches sustained throughput and retention needs. Validate p99 latency, broker recovery, consumer rebalancing, and operational capacity in a proof of concept.
「arch-tech-evaluation」を使用しています。 Choose between two web frameworks for a small team maintaining a business application.
期待される結果:
**Recommendation: Framework A.** Its team familiarity and simpler operations outweigh Framework B's performance advantage. Reassess when traffic or real-time requirements increase.
「arch-tech-evaluation」を使用しています。 Create a proof-of-concept plan and ADR for selecting a distributed database.
期待される結果:
The plan measures latency, failover, consistency, recovery, and cost under representative workloads. The ADR records weighted scores, unresolved risks, and the approval criteria.
All four static findings are false positives. The command alerts identify Markdown fences, while the entropy alerts identify readable Chinese Markdown rather than encoded payloads. No prompt injection, data exfiltration, or executable behavior was found.
zl2023github. (2026). arch-tech-evaluation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-arch-tech-evaluation/audits/4
BibTeX形式の引用
@techreport{zl2023github-zl2023github-arch-tech-evaluation-2026,
author = {zl2023github},
title = {arch-tech-evaluation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-arch-tech-evaluation/audits/4},
note = {Author version unspecified}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "arch-tech-evaluation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/zl2023github-arch-tech-evaluation/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-arch-tech-evaluation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由証拠の信頼度: 中
41
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
Select Messaging Infrastructure
Compare message brokers against throughput, latency, durability, recovery, ecosystem, and operating requirements.
Choose an Application Framework
Evaluate frameworks against delivery needs, team experience, maintenance effort, security, and total cost.
Plan a Defensible Decision
Define proof-of-concept tests and record the final choice, evidence, risks, and rejected alternatives.
これらのプロンプトを試す
Compare Two Options
Compare [option A] and [option B] for [use case]. Focus on functionality, performance, cost, operations, and learning curve. Recommend one option.
Evaluate Against Constraints
Evaluate [candidates] for [system]. Use these constraints: [scale], [latency], [availability], [consistency], [budget], and [team experience]. Create a weighted comparison and identify missing information.
Design a Proof of Concept
Design a proof of concept for choosing among [candidates]. Define hypotheses, workloads, metrics, pass criteria, failure tests, effort, and decision rules.
Produce an Architecture Decision
Assess [candidates] for [architecture]. Build a weighted scorecard, sensitivity analysis, risk register, migration plan, and final recommendation. Draft an ADR that records rejected alternatives and evidence gaps.
ベストプラクティス
Provide measurable workload, latency, availability, consistency, retention, budget, and compliance constraints.
Adjust dimension weights with stakeholders before scoring candidates.
Validate decisive assumptions with benchmarks, documentation, and a time-boxed proof of concept.
回避
Do not select a technology from popularity or star counts alone.
Do not treat default scores as universal facts across teams and workloads.
Do not finalize a recommendation while critical requirements or evidence remain unknown.
よくある質問
What information should I provide?
Provide the use case, candidate technologies, scale, reliability targets, budget, timeline, team experience, existing stack, and compliance constraints.
Can it evaluate any technology category?
Yes. The general workflow applies broadly, but evaluation dimensions and weights should match the specific technology category.
Does it perform live benchmarks?
No. It designs benchmark and proof-of-concept plans, but users must run the tests and supply measured results.
How are recommendations calculated?
Candidates are compared across weighted dimensions. The final recommendation also considers tradeoffs, risks, missing evidence, and organizational constraints.
Can it create an architecture decision record?
Yes. It can format the selected option, decision context, evidence, consequences, risks, and rejected alternatives as an ADR.
How should I handle outdated facts?
Verify product versions, pricing, licenses, security history, and community activity with current primary sources before approving the decision.