본문으로 건너뛰기
cccskills
무료GitHub에 공개

likelihood-language

Use when phrasing a forward-looking statement, the user asks "how likely is X?" / "what's the likelihood?", or the tradecraft pipeline applies a probability yardstick to a finished product. Standardised likelihood language across all products.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Likelihood Language — Probability Yardstick

Every forward-looking assessment (prediction, forecast, risk statement) MUST use standardised likelihood language. Never use vague terms like "could", "might", or "may" without mapping them to a probability band.

The Yardstick

TermProbability RangeUsage
Almost certain>95%Use sparingly. Reserved for near-inevitable outcomes with overwhelming evidence.
Highly likely75-95%Strong evidence supporting the assessment. Limited plausible alternatives.
Likely50-75%The weight of evidence supports this outcome, but meaningful alternatives exist.
Realistic possibility25-50%Plausible outcome that cannot be discounted. Evidence is mixed or limited.
Unlikely15-25%Possible but not supported by the weight of evidence.
Highly unlikely5-15%Very limited evidence suggests this outcome. Most evidence points elsewhere.
Remote<5%Theoretically possible but requires multiple unlikely conditions to align.

How to Use

Correct usage

"It is highly likely (75-95%) that the threat actor will shift targeting to the financial sector in Q3, based on observed reconnaissance activity and historical pattern of seasonal targeting shifts."

"There is a realistic possibility (25-50%) that the exploit will be weaponised within 30 days, given the availability of a proof-of-concept but no evidence of active exploitation."

Incorrect usage

"The threat actor might target financial services." ❌ (No probability band) "It could happen in Q3." ❌ (Vague, unquantified) "We think it's likely but also possible that..." ❌ (Contradictory — pick one band)

Combining with Confidence

Likelihood and confidence are independent dimensions:

"We assess with moderate confidence that it is likely (50-75%) that Group X will conduct destructive operations against energy sector targets in the next 6 months."

  • Moderate confidence: We have some evidence but key assumptions are not fully validated
  • Likely: Based on available evidence, the probability falls in the 50-75% range

A low-confidence assessment CAN have a high likelihood term — it means "if our assessment is correct, the probability is high, but we're not fully sure our assessment is correct."

When NOT to Use Likelihood Language

  • Statements of fact: "APT28 used Fancy Bear malware in this campaign" — this is a factual claim, not a prediction. Use confidence levels instead.
  • Historical analysis: "The campaign began in January 2025" — past events don't need likelihood language.
  • Definitions and descriptions: "SIGMA rules are detection rules written in YAML" — informational, not predictive.

Mapping Informal Language

If you catch yourself writing informal probabilistic language, map it:

InformalMap to
"could", "may", "might"Determine which band and use proper term
"probably"Likely (50-75%) or Highly likely (75-95%)
"possibly"Realistic possibility (25-50%)
"unlikely"Already a valid term — check it maps to 15-25%
"almost certainly"Almost certain (>95%)
"there's a chance"Determine probability and use proper term
"can't rule out"Realistic possibility (25-50%) or Unlikely (15-25%)

Common Mistakes

  • Using multiple likelihood terms in one assessment ("likely or highly likely") — commit to one
  • Hedging with "possible" instead of making a judgment — if evidence is weak, say "unlikely" with rationale
  • Forgetting to include the percentage range in parentheses — always include for clarity
  • Confusing likelihood with confidence (see confidence-levels skill)
  • Using "almost certain" casually — this is >95% and should be rare

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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의 스킬 모두 보기

이 스킬의 문제 신고