Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Threat Actor Profiling

ASecurity

Profile a threat actor or campaign — their TTPs (mapped to MITRE ATT&CK), targeting, tooling, infrastructure, and likely intent — to support threat-informed defense. Use to understand who might target you and how, and to prioritize defenses.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgosecurity

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill threat-actor-profiling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Threat Actor Profiling?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Threat Actor Profiling
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jassics-threat-actor-profiling/badge)](https://www.skillsdirectory.com/skills/jassics-threat-actor-profiling)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: threat-actor-profiling
description: >-
  Profile a threat actor or campaign — their TTPs (mapped to MITRE ATT&CK),
  targeting, tooling, infrastructure, and likely intent — to support threat-informed
  defense. Use to understand who might target you and how, and to prioritize defenses.
---

# Goal

An actor/campaign profile that informs defense: what they do (TTPs), who they target,
how they operate, and what that means for your detection and control priorities.

# What to capture

1. **Identity & aliases** — actor/group names across vendors (naming differs);
   suspected motivation (espionage, financial, hacktivism) and sponsorship if assessed.
2. **Targeting** — sectors, geographies, and victimology; whether your org fits the
   pattern (relevance to *you* is the point).
3. **TTPs** — map observed behaviors to **MITRE ATT&CK** across the lifecycle (initial
   access → impact); note signature techniques and tooling/malware families.
4. **Infrastructure** — typical C2, hosting, domains/certs patterns (link via
   `ioc-enrichment`).
5. **Framing** — use the Diamond Model (adversary–capability–infrastructure–victim)
   and Kill Chain to structure the picture; note confidence and gaps.

# Steps

1. Aggregate reporting and your own telemetry/incidents (`dfir`); reconcile aliases.
2. Build the ATT&CK technique set and tooling profile; assess confidence per claim.
3. Assess relevance to your environment and which of their TTPs you can/can't detect.
4. Translate to action: detection priorities (`detection-engineering:detection-coverage-review`)
   and control/hardening recommendations.

# Output

An actor profile: aliases · motivation · targeting · ATT&CK TTP set · tooling/
infrastructure · relevance-to-us · confidence/gaps · recommended detections &
controls. Use `security-reporting`; visualize the ATT&CK profile with
`security-diagramming`.

# Notes

The deliverable isn't a biography — it's *what their TTPs mean for your defenses*.
Reconcile vendor aliases (the same group has many names) and be explicit about
confidence and intelligence gaps. Prioritize defending the techniques they actually
use and that you currently can't detect.

Attribution

jassicsjassics
View sourceSee grades on GitHubMore from jassics →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

696561 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes
View all in ai-agents →