Menu

Individual skill

defense-threat-intel

0upvotes

Enrich IOCs, campaigns, impersonation, and scam narratives from public sources — bounded public X/Twitter collection via Xquik plus independent corroboration — and hand off a reviewable intelligence package. Load for "enrich this IOC", "is this domain in recent phishing disclosures", tracking threat-actor aliases or lookalike accounts, or prepping an intel package for threat hunting, malware triage, or IR. Signals: IOC lists (domain/IP/URL/hash/email/wallet), campaign names, phishing disclosures, impersonation reports, X/Twitter leads, Xquik.

skills/defense/defense-threat-intel/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Threat intelligence from public sources

## When it applies
A defensive task needs public-source enrichment: vetting IOCs (domains, IPs, URLs, hashes, emails,
wallet addresses), tracking publicly disclosed malicious campaigns, phishing activity,
impersonation accounts, or scam narratives — or turning public X/Twitter chatter into leads that
samples, network telemetry, or vendor sources must then verify. Confirm the collection is bounded
up front (see `tradecraft-scope-roe`): target entities, time window, and intended use of the
results. This skill does **not** cover brand marketing, engagement growth, automated posting, or
social analytics with no security purpose.

## Why it works
Public posts surface malicious infrastructure and campaigns early — often before vendor coverage —
but a post only proves that *a claim was published at a time*, never attribution, exploitability,
Back to top