Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

cross-validation交叉验证

Agent Skill

cross-validation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

267

周安装

11

GitHub Stars

4

下载量

87
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cross-validation(交叉验证)
来源仓库:https://github.com/tradeinsight-info/investment-analysis-skills
仓库路径:skills/cross-validation
安装命令:
npx skills add https://github.com/tradeinsight-info/investment-analysis-skills --skill cross-validation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/tradeinsight-info/investment-analysis-skills --skill cross-validation

简介

cross-validation 通过比对多个独立数据源验证关键财务指标的真实性与一致性。

  • 适用于投资分析、财报解读等对数据准确性要求高的场景,帮助识别潜在误差或矛盾点。
  • 自动标记单源覆盖数据与重大差异项,生成结构化验证报告供人工复核决策。
  • 使用前需熟悉内置数据源清单与阈值设定规则,确保验证逻辑符合业务需求。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Cross-Validation

Purpose

Verify key financial data points by cross-referencing values across two or more independent data sources. Detect discrepancies that may arise from differences in reporting periods, accounting adjustments, rounding conventions, or outright data errors. Produce a validation report that flags confirmed data, discrepancies above a defined threshold, and metrics with only single-source coverage, so downstream analysis rests on trustworthy inputs.

Data Fetching Process

Consult ${CLAUDE_PLUGIN_ROOT}/skills/_shared/references/data-sources.md for full source details and fallback behavior.

Source Selection Rules

  1. Determine the primary source of the data being validated. Identify which source originally provided the data points under review:

- If the original data came from SEC EDGAR, validate against Stock Analysis as the cross-check source. - If the original data came from Stock Analysis, validate against SEC EDGAR or Gurufocus as the cross-check source. - If the original data came from Gurufocus, validate against SEC EDGAR as the cross-check source. - If the original source is unknown or the user simply requests validation, fetch from both SEC EDGAR and Stock Analysis independently and compare.

  1. Resolve the ticker. Fetch https://www.sec.gov/files/company_tickers.json using the sec-fetch skill (see data-sources.md), locate the company's CIK, and pad it to 10 digits. Cache the CIK and official company name.

Fetching Source A — SEC EDGAR XBRL API

  1. Fetch structured financial data from EDGAR. Request: https://data.sec.gov/api/xbrl/companyfacts/CIK{10-digit-CIK}.json Extract the following XBRL concepts for the most recent fiscal year (filter for fp == "FY", sort by end date descending): Metric XBRL Concept(s) Unit Revenue Revenues, RevenueFromContractWithCustomerExcludingAssessedTax USD Net Income NetIncomeLoss USD Diluted EPS EarningsPerShareDiluted USD/shares Total Assets Assets USD Total Debt LongTermDebt, LongTermDebtAndCapitalLeaseObligations USD Stockholders' Equity StockholdersEquity USD Shares Outstanding CommonStockSharesOutstanding shares Record the end date for each data point to ensure period alignment during comparison.

Fetching Source B — Stock Analysis

  1. Fetch financial data from Stock Analysis. Retrieve: Parse the HTML tables to extract the matching fiscal year's figures. Ensure the fiscal year end date aligns with the EDGAR data. Note any labeling differences (e.g., Stock Analysis may label "Total Debt" differently than EDGAR's LongTermDebt).

- https://stockanalysis.com/stocks/{ticker}/financials/ — revenue, net income, EPS - https://stockanalysis.com/stocks/{ticker}/financials/balance-sheet/ — total assets, total debt, equity - https://stockanalysis.com/stocks/{ticker}/financials/ratios/ — P/E, EV/EBITDA, market cap

Fetching Source C — Gurufocus (When Needed)

  1. Fetch supplementary data from Gurufocus when a third source is required for tiebreaking or when one of the primary sources is unavailable: https://www.gurufocus.com/term/{metric}/{ticker} Common metric slugs: revenue, net-income, eps-diluted, total-assets, long-term-debt, pe-ratio, ev-to-ebitda.

Market-Derived Metrics

  1. Validate market-derived metrics separately. Market cap, P/E, and EV/EBITDA change with share price and may differ between sources due to timing:

- Fetch current market cap from Stock Analysis main page: https://stockanalysis.com/stocks/{ticker}/ - Compute P/E as market cap divided by TTM net income, or share price divided by TTM diluted EPS. - Compare computed P/E with the reported P/E from Stock Analysis ratios page and Gurufocus. - Accept wider discrepancy thresholds for market-derived metrics (up to 10%) since share price fluctuates intraday.

Analysis Steps

Key Metrics to Validate

Validate the following core metrics. These represent the most commonly referenced data points in fundamental analysis and are the highest-priority items for accuracy:

PriorityMetricWhy It Matters
CriticalRevenueFoundation of all growth and margin calculations
CriticalNet IncomeDrives EPS, P/E, and profitability metrics
CriticalDiluted EPSMost widely quoted earnings figure
HighTotal AssetsDenominator for ROA and leverage ratios
HighTotal DebtKey input for D/E, interest coverage, solvency
HighMarket CapBasis for all valuation multiples
MediumP/E RatioMost common valuation shorthand
MediumEV/EBITDAEnterprise-level valuation multiple

Discrepancy Detection

For each metric, compute the percentage discrepancy between sources:

Discrepancy % = |Value_A - Value_B| / ((Value_A + Value_B) / 2) * 100

Apply the following thresholds:

Metric TypeThresholdRationale
Reported financials (revenue, net income, EPS, assets, debt)5%These come from audited filings; differences above 5% likely indicate a data error, period mismatch, or definitional difference
Market-derived metrics (market cap, P/E, EV/EBITDA)10%Share price changes cause natural divergence between sources with different data refresh cycles
Computed ratios (ROE, ROIC, margins)8%Slight differences in denominators or averaging methods can produce meaningful ratio differences

Discrepancy Investigation

When a discrepancy exceeds the threshold:

  1. Check period alignment. Verify that both sources reference the same fiscal year end date. A common cause of discrepancy is one source reporting calendar-year data while the other reports the company's fiscal year (e.g., Apple's fiscal year ends in September, not December).
  2. Check definitional differences. Revenue may differ if one source includes or excludes excise taxes. Debt may differ if one source includes capital lease obligations while the other reports only long-term debt. EPS may differ between basic and diluted. Document the specific definitional cause.
  3. Check currency and unit scaling. Ensure both values use the same currency and scale (millions vs. billions vs. raw numbers). A factor-of-1000 discrepancy almost always indicates a unit mismatch rather than a data error.
  4. Check restatements. If the company restated financials, one source may reflect the restated figures while the other retains the originally reported values. Note which value is the restated figure.
  5. Tiebreak with a third source. If the cause of discrepancy cannot be determined, fetch the same metric from Gurufocus or WebSearch for an SEC filing excerpt. Align with whichever two of three sources agree.

Single-Source Coverage

Note any metrics where only one source provides data. Common situations include:

  • Gurufocus-only metrics: quality scores, predictability rank, DCF intrinsic value
  • EDGAR-only metrics: specific XBRL concepts not mapped by aggregator sites
  • Stock Analysis-only metrics: pre-computed TTM figures, analyst estimate composites

Flag single-source metrics explicitly so the user understands these data points have not been independently verified.

Depth Handling

Consult ${CLAUDE_PLUGIN_ROOT}/skills/_shared/references/output-format.md for standard formatting rules.

  • Summary depth (default). Present the validation table with status indicators for the eight core metrics. Include a one-sentence note for any flagged discrepancy explaining the likely cause. Omit detailed investigation steps. Total output should be a single table plus two to three sentences of commentary.
  • Detailed depth. Expand to include all validated metrics (core plus any additional metrics the user or calling agent requested). Provide a full investigation narrative for each discrepancy, including the raw values from all sources consulted, the computed discrepancy percentage, the identified root cause, and the recommended value to use. Include a separate section listing single-source metrics with an assessment of reliability.

Output

Follow the output structure defined in ${CLAUDE_PLUGIN_ROOT}/skills/_shared/references/output-format.md. Begin with the standard header using "Data Cross-Validation" as the analysis type. Present findings in the following validation table format:

MetricSource A (EDGAR)Source B (Stock Analysis)DiscrepancyStatus
Revenue ($B)394.3394.30.0%Confirmed
Net Income ($B)97.096.80.2%Confirmed
Diluted EPS6.426.420.0%Confirmed
Total Debt ($B)108.0111.12.8%Confirmed
P/E Ratio32.133.54.3%Confirmed
EV/EBITDA25.428.110.1%Discrepancy

Use "Confirmed" when the discrepancy is within threshold and "Discrepancy" when it exceeds the threshold. For discrepancies, add a footnote row or inline note explaining the likely cause and the recommended value.

After the table, include a summary line:

Validation result: X of Y metrics confirmed, Z discrepancies flagged.

Note any metrics with single-source coverage in a separate row or footnote. Include source URLs for both sources consulted. Close with the standard disclaimer.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.22%
按下载量换算31

Claude

28.71%
按下载量换算25

Cursor

17.92%
按下载量换算16

Gemini CLI

8.66%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills