Menu

Individual skill

social-engineering-defense

0upvotes

Defend against social engineering — recognize manipulation tactics, build verification culture, and run awareness programs that work.

skills/social-engineering-defense/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 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)
56
Repository last updated
Oct 10, 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

## Overview

Social engineering bypasses technology by manipulating people: phishing, pretexting, baiting, tailgating. It remains the top initial-access vector because it attacks trust, urgency, and authority — human traits, not software bugs. Defense is therefore cultural and procedural as much as technical: verification habits, clear escalation paths, and controls that make a single human mistake non-fatal.

This skill is purely defensive: recognizing tactics, building organizational resilience, and designing awareness programs. It contains no instructions for conducting social engineering.

Humans are not the weakest link — they are the most attacked link, which is a design problem, not a people problem. The organizations that resist social engineering build systems where a moment of inattention does not equal a breach: verification procedures, technical guardrails, and a culture where pausing to check is praised, not mocked for slowing things down.

## When to use

- After a phishing incident or near-miss — turning it into systemic improvement.
- Designing security awareness training that changes behavior, not just completion rates.
- Writing verification procedures for high-risk actions (wire transfers, credential resets, access grants).
- Assessing human-risk: which roles are targeted and what would a compromise cost.
Back to top