Individual skill

social-eng-methodology

Plan and run an AUTHORIZED social-engineering assessment safely — the load-first guardrails for any human-factor test. Load before any phishing, vishing, pretext, or physical work. Signals: "social engineering", "phishing assessment", "test our employees", "security awareness", a human-factor objective in a pentest SoW. Establishes authorization, safety, tracking, and the awareness-focused report.

skills/social-eng/social-eng-methodology/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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

# Social-engineering engagement methodology

## When this governs
Load this **first**, before any phishing/vishing/pretext/physical skill. Social engineering targets
*people*, so it carries authorization and duty-of-care requirements beyond a normal technical test.
This is `pentest`-only: it is never run against a bug-bounty target, and never against individuals
or organizations that have not authorized it in writing.

## Authorization — stricter than technical scope
On top of `tradecraft-scope-roe`, an SE engagement requires, in writing, before anything:
- **Explicit sign-off from someone empowered to consent for the employees being tested** (not just
  IT) — SE tests real staff, so leadership/HR/legal must have approved the human-factor testing.
- **The pretext boundaries**: which themes are allowed and which are off-limits (no fake layoffs,
  bonuses, medical/family emergencies, or anything that causes real distress or coerces protected
Back to top