Confidence Scorer Skill

Assign High, Medium, or Low confidence to correlated technology findings using weighted evidence and conflict penalties.

Updated May 27, 2026
One-click install
npx skills add https://github.com/hoanghn61/.agents --skill confidence-scorer-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Confidence Scorer Skill
Source: https://github.com/hoanghn61/.agents/tree/main/skills/techstack-identification/confidence_scorer
Command: npx skills add https://github.com/hoanghn61/.agents --skill confidence-scorer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves uncertainty in detected technology stacks by converting corroboration signals into consistent High, Medium, or Low confidence labels.

Core Features & Use Cases

It scores each correlated technology using weighted evidence signals such as source diversity, signal strength, cross-source agreement, evidence type preference (technical vs job postings), and conflict penalties. It also produces actionable outputs including a per-technology confidence result with detailed reasoning, an aggregate confidence summary across a report, and a list of confidence gaps that indicate where additional validation signals are needed. Typical use cases include technology stack identification from multi-source analysis where findings must be prioritized for follow-up verification.

Quick Start

Use the confidence_scorer operation to score each correlated technology from the correlated_technologies array and produce confidence-labeled results with explanations.

Frequently Asked Questions about Confidence Scorer Skill

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

FAQPage Schema
How do I assign confidence scores to technology stack findings from multiple sources?

Confidence scoring for technology stack identification works by weighting multi-source evidence such as source diversity, signal strength, and cross-source agreement. It then applies conflict penalties to assign High, Medium, or Low labels to each correlated technology finding.

Why does my detected technology stack have conflicting evidence from different sources?

When multi-source evidence disagrees during technology stack identification, this skill applies conflict penalties to penalize the agreement score, resulting in lowered confidence labels and flagging specific gaps where additional validation signals are needed.

What is the best way to resolve uncertainty in technology identification pipelines with incomplete corroboration?

The best way to resolve uncertainty from incomplete corroboration is to use confidence scoring to convert multi-source evidence signals into consistent High, Medium, or Low labels, producing a prioritized list of confidence gaps for follow-up verification.

What input format is required for confidence scoring of correlated technologies?

Confidence scoring requires a structured correlated_technologies input array containing sources, agreement_score, and corroborating_signals. An optional conflicts array can be included alongside this data to apply conflict penalties and threshold-based confidence mapping.

How do I identify confidence gaps in a multi-source technology stack analysis?

You identify confidence gaps in a technology stack analysis by processing weighted evidence and conflict impacts. The skill produces an actionable list of confidence gaps that indicates exactly where additional validation signals are needed across the report.