本文へ移動
cccskills
無料GitHub で公開

source-assessment

Use when rating a source with the NATO Admiralty Scale, the user asks "is this reliable?" / "rate this source", or the tradecraft pipeline calls for source assessment before publishing. Reliability A-F, credibility 1-6.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md7.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Source & Information Assessment — NATO Admiralty Scale

Every piece of intelligence entering this platform MUST be assessed using the Admiralty Scale. This is non-negotiable. Tag every item with a two-character code (e.g., B2). Claims from documents are the exception: they carry the evidence grade instead, see below.

How this differs from the evidence grade

The pack uses two instruments. They are not the same and neither is converted into the other.

  • Admiralty reliability is the source's track record: how often it has been right before. The evidence grade's access level is how the source knows the particular thing claimed.
  • Admiralty is a letter and a number (B2). The evidence grade is two words, access level then claim support ("direct, firm").
  • Documents, articles and reports are graded per claim by /quality-of-information-check with the evidence grade. Lookup results and single items are rated here, on the Admiralty scale.

Scope of This Skill

This skill is the reference for the Admiralty scale itself: what the letters and digits mean and how to apply them to a single item, such as a lookup result, a feed entry or a tip.

Documents, articles and reports are graded per claim by /quality-of-information-check, using its fixed rubric (references/grading-rubric.md in that skill). That grade is the evidence grade, not an Admiralty rating. It resolves the article to its originating source first, then grades each claim on the chain it arrived through. One report usually contains claims of different standing, so one grade for the whole report is wrong.

The pack does not store reliability opinions about named organisations. Where the guides and examples below name a vendor or agency, they illustrate a kind of access and track record. They are not standing grades for that organisation. In one report the same organisation can publish an observation that /quality-of-information-check grades "direct, firm" and an attribution it grades "direct, tentative".

Source Reliability

How trustworthy is the source based on its track record?

CodeRatingCriteria
ACompletely reliableNo doubt about the source's authenticity, trustworthiness, or competency. History of complete reliability.
BUsually reliableMinor doubt. Source has been reliable in most instances.
CFairly reliableDoubt about reliability. Source has provided valid information in the past but not consistently.
DNot usually reliableSignificant doubt. Source has been unreliable in the past.
EUnreliableSource has a track record of being unreliable, or the information is obtained under duress/deception.
FReliability cannot be judgedNo basis for evaluating the source's reliability. New or unknown source.

Source Reliability Decision Guide

Judge the source on how it knows and how it has performed, not on its name.

  • A: Direct access to what it reports (own telemetry, an incident response engagement, forensic evidence from your own systems, a victim's own regulatory disclosure) and no known retractions on this kind of claim
  • B: Established source reporting from indirect access, such as sample analysis or partner data; well-known researcher with a history of published work; vetted sharing community relaying member reporting
  • C: Access not disclosed; reporting that mixes own findings with aggregation; community feeds and open-source tools with mixed accuracy; advisory that aggregates others' reporting without adding evidence
  • D: No originating source can be located; unverified forum posts and anonymous tips; source that has been wrong before
  • E: Documented history of inaccurate, inflated or fabricated claims
  • F: No basis to judge: first-time sources, automated feeds without historical accuracy data, newly discovered paste sites, a threat actor's own statements

Information Credibility

How likely is the information itself to be accurate, regardless of source?

CodeRatingCriteria
1ConfirmedConfirmed by other independent sources. Logical, consistent with other information on the subject.
2Probably trueNot confirmed, but logical and consistent with other information.
3Possibly trueNot confirmed. Reasonably logical but not fully consistent with other information.
4DoubtfulNot confirmed. Possible but not logical. No other information on the subject.
5ImprobableNot confirmed. Not logical. Contradicted by other information on the subject.
6Truth cannot be judgedNo basis for evaluating the information's veracity.

Information Credibility Decision Guide

  • 1: Corroborated by 2+ independent sources; matches observed technical evidence; confirmed by forensic analysis
  • 2: From a reliable source; logically consistent with known threat landscape; partially corroborated
  • 3: Plausible but from a single source; consistent with general trends but not specifically corroborated
  • 4: Unconfirmed claim; contradicts some known information; possible but requires further investigation
  • 5: Contradicts well-established intelligence; logically inconsistent; likely disinformation
  • 6: Cannot evaluate — insufficient context, entirely new domain, or conflicting assessment criteria

Combined Rating Examples

These illustrate the reasoning. They are not standing grades for the organisations named.

RatingExample
A1Microsoft publishes CVE details with MSRC forensic analysis, confirmed by CISA KEV listing
B2CrowdStrike reports new APT campaign TTPs; consistent with own telemetry but not independently confirmed
C3Security blogger reports new malware variant with partial technical analysis; plausible but unverified
D4Anonymous Telegram channel claims zero-day in popular software; no technical details provided
F6First-time automated feed delivers IOCs with no historical accuracy baseline

How to Apply

  1. At collection time: Tag every piece of incoming intelligence with its Admiralty rating
  2. In analysis: Weight evidence by reliability — A1 evidence outweighs D4 evidence
  3. In products: Include the rating in the Sources & References section
  4. When ratings change: If new information changes the credibility assessment, update and log the change

Common Mistakes

  • Confusing source reliability with information credibility (a reliable source can relay inaccurate information)
  • Rating all vendor reports as A1 (vendors can have biases and errors)
  • Giving an article one Admiralty rating for the outlet that published it (articles and reports go to /quality-of-information-check, which grades each claim on the primary's access and wording, plus how faithfully the outlet transmitted it; five outlets covering one report are one source)
  • Not reassessing ratings when new corroborating or contradicting information emerges
  • Omitting the rating entirely because "it's obvious" — always be explicit

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

AbuseIPDB API reference. IP reputation and abuse report lookups.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

ach

無料

Analysis of Competing Hypotheses — structured technique for evaluating multiple explanations against evidence. Use when facing ambiguous attribution or multiple plausible scenarios. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Runs on ungraded evidence when asked, labelled as such, unweighted, and capped at Moderate confidence.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Use when documenting a named campaign across time and victims, the user asks to start or update a campaign record, or another skill identified a multi-incident cluster that warrants formal tracking. Provides the template (timeline, attribution, victimology, attack chain, Diamond Model mapping, IOC clusters) and the lifecycle from active to historical.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Use when the user asks about carding, BIN attacks, payment-card breach markets, fullz/CVV2 trade, autoshops (BidenCash, Brian's Club, Russianmarket, B1ack's Stash), or financial-fraud TTPs. Self-updating knowledge cell.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Censys API v2 reference. Host reconnaissance and certificate data.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Use when the user asks about Chinese state-sponsored cyber operations or specific PRC-aligned actors (APT41, Volt Typhoon, Mustang Panda, APT10, APT31, Salt Typhoon, etc.), MSS/PLA-attributed campaigns, or PRC sector targeting. Self-updating knowledge cell.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Liberty91LTD のスキルをすべて見る

このスキルの問題を報告する