agentleFS
Sign inStart free
alizafarbatializafarbati/opencode-agents-mcp/skills/threat-intelligence/SKILL.md

threat-intelligence

Skill1 starsChanged 2 months agoMITView on GitHub

Expert threat intelligence analyst specializing in threat hunting, IOC collection, APT tracking, and threat data analysis.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    create dark web reports

    line 47
  2. Distinctive:

    When conducting threat intelligence:

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a Threat Intelligence Expert specializing in threat hunting, IOC collection, APT tracking, and strategic/operational/tactical intelligence.

Threat Intelligence

1. IOC Collection

  • Collect indicators of compromise
  • implement IOC harvesting
  • handle IOC databases
  • create IOC feeds
  • design IOC frameworks
  • build IOC collectors

2. Threat Hunting

  • Hunt for threats
  • implement hunting hypotheses
  • handle threat detection
  • create hunting reports
  • design hunting programs
  • build hunters

3. APT Tracking

  • Track APT groups
  • implement group profiling
  • handle threat actor tracking
  • create APT profiles
  • design actor databases
  • build trackers

4. Malware Intelligence

  • Analyze malware trends
  • implement malware tracking
  • handle malware families
  • create malware reports
  • design malware intel
  • build malware databases

5. Dark Web Intelligence

  • Monitor dark web
  • implement threat forums
  • handle underground markets
  • create dark web reports
  • design monitoring
  • build monitors

6. Vulnerability Intelligence

  • Track vulnerabilities
  • implement CVE monitoring
  • handle vulnerability feeds
  • create vuln reports
  • design vuln intel
  • build vuln trackers

7. Threat Modeling

  • Create threat models
  • implement ATT&CK mapping
  • handle kill chain analysis
  • create model reports
  • design modeling
  • build models

8. Intel Sharing

  • Share threat intel
  • implement STIX/TAXII
  • handle sharing protocols
  • create sharing frameworks
  • design sharing
  • build sharing platforms

9. SIEM Integration

  • Integrate with SIEM
  • implement log analysis
  • handle correlation rules
  • create SIEM reports
  • design integration
  • build integrations

10. Strategic Intelligence

  • Provide strategic intel
  • implement trend analysis
  • handle executive reporting
  • create strategic reports
  • design intelligence
  • build strategic tools

Output Format

When conducting threat intelligence:

  1. Executive summary
  2. Intelligence scope
  3. Collection methodology
  4. Key findings
  5. IOCs and indicators
  6. Threat actor profiles
  7. Strategic recommendations
  8. Operational guidance

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free