tech-evaluation

Evaluates libraries and file formats against cited evidence to produce one schema-validated recommendation.

Updated Apr 9, 2014
One-click install
npx skills add https://github.com/thoroc/thoroc.github.io --skill tech-evaluation-thoroc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-evaluation
Source: https://github.com/thoroc/thoroc.github.io/tree/main/.agents/skills/tech-evaluation
Command: npx skills add https://github.com/thoroc/thoroc.github.io --skill tech-evaluation-thoroc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Technology decisions often stall on unverified claims or end in hedged "it depends" answers with no citation trail. This Skill forces a structured investigation of a candidate library, dependency, or file format against a fixed question set, validates the result against a JSON schema, and produces exactly one actionable recommendation. ## Core Features & Use Cases - Structured research workflow: Dispatches a research subagent with a fixed question set (correctness, integration_fit, footprint, maturity, practical_fit) and requires cited evidence for every verdict. - Schema validation gate: Validates the subagent's YAML output with scripts/validate-tech-evaluation.sh before any finding is rendered, rejecting empty evidence, out-of-enum verdicts, or thin rationales. - Finding record generation: Renders validated results into a dated FINDING record via the context-file skill and regenerates the context index for discoverability. - Use Case: Choosing between mustache, micromustache, and a hand-rolled templating function for a Lambda-bundled project — the Skill verifies the actual Terraform bundling config rather than trusting assumptions, then delivers a single adopt/reject verdict with citations. ## Quick Start Ask the agent to properly evaluate a specific npm package or file format for your integration point, naming the alternatives already considered.

Frequently Asked Questions about tech-evaluation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate an npm package before adopting it?▼

Dispatch a structured evaluation covering correctness, integration fit, footprint, maturity, and practical fit, with cited evidence required for every verdict. The output is validated against a JSON schema and ends in exactly one recommendation: adopt, keep_current, reject, or needs_more_research.

How do I compare two libraries like mustache vs micromustache?▼

Provide both package identifiers and the alternatives already ruled out, then run the fixed question set against each with cited sources. The process forbids ending in a comparison table without a conclusion — it must produce a single non-hedging recommendation.

When should I not run a technology evaluation?▼

Skip it for one-line version lookups, purely subjective preference calls with no verifiable claim, and decisions already settled by an existing ADR. For ADR-settled choices, supersede the ADR instead of producing a duplicate evaluation finding.

What happens if the evaluation YAML fails schema validation?▼

Validation failures such as empty evidence arrays or too-short rationales block rendering entirely. The YAML is sent back to the research subagent for correction rather than being hand-patched, and the finding is only rendered after a fresh validation pass succeeds.

Can the default evaluation dimensions be changed?▼

Yes, the schema requires at least one question, not exactly five. You can substitute dimensions when the defaults don't fit, such as replacing integration_fit with tooling for a file-format choice or adding interoperability for a protocol decision.