stock-data-verifier

Verify stock and ETF numeric data across multiple web sources with quoted evidence.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yjang-git/HoneyPot --skill stock-data-verifier-yjang-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stock-data-verifier
Source: https://github.com/yjang-git/HoneyPot/tree/main/plugins/stock-consultation/skills/stock-data-verifier
Command: npx skills add https://github.com/yjang-git/HoneyPot --skill stock-data-verifier-yjang-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents hallucinated or fabricated numeric data when collecting stock and ETF metrics by enforcing a strict cross-verification protocol and source quoting requirements.

Core Features & Use Cases

  • Three-source cross-checks: Enforce at least two independent sources plus one primary official source for financial metrics.
  • Original-text quoting: Require agents to include the exact quoted sentence containing the number (original_text), source URL, and date for traceability.
  • Failure handling and rules: Define clear tolerance bands (±5%), variance handling, and standardized error codes for automated workflows.
  • Use Case: An automated portfolio analyzer collects KRW prices, PER, and dividend yield for a Korean stock, verifies values across Naver Finance and KRX, includes original_text and URLs, and returns verified JSON or a FAIL code.

Quick Start

Use stock-data-verifier by instructing an agent to verify Samsung Electronics price and PER using the mcp_exa_web_search_exa and mcp_websearch_web_search_exa tools and return verified results with original_text and source URLs.

Frequently Asked Questions about stock-data-verifier

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

FAQPage Schema
How do I prevent hallucinated stock data when extracting financial metrics with agents?

Preventing hallucinated stock data requires enforcing a cross-verification protocol where agents must extract original_text quotes, source URLs, and dates from multiple web searches, matching financial metrics within a ±5% tolerance to prevent fabricated figures.

How do I cross-verify ETF and stock prices across multiple web sources?

Cross-verify ETF and stock prices by instructing agents to query at least two independent sources plus one primary official source, comparing extracted numeric data within a ±5% tolerance band and returning a standardized FAIL code if variance exceeds the limit.

Can I verify Korean equity data using Naver Finance and KRX sources?

Yes, you can verify Korean equity data using Naver Finance and KRX as independent sources. The verification process requires extracting original_text quotes and source URLs to cross-check KRW prices, PER, and dividend yields within the ±5% tolerance.

What is the best way to validate NAV and expense ratios for portfolio analysis?

The best way to validate NAV and expense ratios is enforcing a three-source cross-check protocol during data collection, requiring at least two independent sources plus one primary official source, and demanding exact original_text quotes for traceability.

Does financial data verification work with automated portfolio analyzer workflows?

Yes, financial data verification integrates with automated workflows by outputting verified JSON containing matched metrics, original_text, and source URLs, or returning a standardized FAIL code when cross-source variance exceeds the ±5% tolerance band.

Why does my stock data verification return a FAIL code during cross-source matching?

Stock data verification returns a FAIL code when the variance between extracted financial metrics from multiple web sources exceeds the strict ±5% tolerance band, indicating incompatible data points that cannot be confidently confirmed as accurate.