tech-assessment_skill

This skill helps assess technologies for strategic fit, feasibility, and risks to guide build vs.

3

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill zircote/sigint --skill tech-assessment

SKILL.md5.8 KB

Overview

This skill evaluates technologies for strategic fit, technical feasibility, and competitive advantage. It provides practical frameworks to score maturity, risk, economics, and fit within an existing stack. Use it to produce clear build-vs-buy recommendations, readiness assessments, and monitoring indicators.

How this skill works

The skill inspects technical maturity, strategic alignment, risk profile, and economic factors using structured matrices and readiness levels (TRL). It maps technologies to hype-cycle stages, applies three-valued trend logic (INC/DEC/CONST), and produces a weighted evaluation and a concise recommendation. Outputs include an evaluation matrix, build-vs-buy rationale, competitive position, primary risks with mitigations, and monitoring indicators.

When to use it

Selecting a new technology or vendor for a product initiative
Assessing technical feasibility during early-stage planning
Conducting technical due diligence for M&A or partnerships
Deciding whether to build or buy a capability
Creating a technology roadmap or migration plan

Best practices

Score technologies against real use cases and measurable criteria
Include non-technical stakeholders to validate strategic fit
Prototype critical components before a large investment
Document assumptions, update assessments regularly, and track indicators
Weight dimensions (maturity, risk, cost, talent) to reflect business priorities

Example use cases

Compare two machine learning platforms and recommend build vs. buy
Evaluate a vendor SaaS for integration and long-term TCO
Perform architecture and code quality review during due diligence
Map a legacy stack to cloud-native alternatives and produce a migration plan
Monitor adoption trends for an emerging open-source framework

FAQ

Set weights to reflect business priorities: emphasize performance, scalability, and security for mission-critical systems; emphasize cost and time-to-market for commodity features.

When is build favored over buy?

Favor build when the capability is a core differentiator, requirements are unique, long-term cost benefits exist, and internal expertise is available.