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

People Osint

ASecurity

Gather people- and organization-focused OSINT for an authorized social-engineering assessment — org structure, roles, contact patterns, and public footprint that inform realistic phishing/pretext scenarios. Use only within an authorized engagement; focus on assessing susceptibility and improving awareness.

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

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill people-osint --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of People Osint?

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

Security grade badge for People Osint
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jassics-people-osint/badge)](https://www.skillsdirectory.com/skills/jassics-people-osint)

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: people-osint
description: >-
  Gather people- and organization-focused OSINT for an authorized social-engineering
  assessment — org structure, roles, contact patterns, and public footprint that
  inform realistic phishing/pretext scenarios. Use only within an authorized
  engagement; focus on assessing susceptibility and improving awareness.
---

# Goal

Enough organizational and personnel context to design realistic social-engineering
test scenarios (and to inform defensive awareness) — without overcollecting or
crossing ethical/legal lines.

# Scope & ethics first

- Only within an **authorized** engagement with agreed rules of engagement.
- Collect from **public** sources; gather the **minimum** needed for the assessment.
- The objective is to **measure susceptibility and improve awareness/controls**, not
  to harm or harass individuals. Handle personal data with care; minimize and protect
  it; respect privacy law.

# What to gather (organization-centric)

1. **Structure & roles** — departments, reporting lines, key functions (finance, IT,
   HR — common phishing targets), and high-value roles.
2. **Contact patterns** — corporate email format, naming conventions, public contact
   info, out-of-office/role mailboxes.
3. **Public footprint** — professional profiles, conference talks, public posts that
   reveal tooling, processes, or pretext hooks (events, vendors, projects).
4. **Pretext material** — current initiatives, partners, and vendors that make a
   believable, testable scenario.

# Steps

1. Confirm authorization and RoE; define what's in scope and off-limits.
2. Collect organization-level context and the email/naming pattern.
3. Build realistic, role-appropriate scenarios (e.g. vendor/IT/HR themes) for the
   authorized phishing/vishing test.
4. Keep records minimal and protected.

# Output

An assessment-support pack: org/role map · email/naming pattern · candidate pretext
themes · suggested target roles (by function, not gratuitous personal detail). Use
`security-reporting`; results inform awareness training and email controls.

# Notes

Stay authorized, public-source, and minimal — this measures and improves resilience,
it is not a license to profile or harm people. Finance/IT/HR are common targets;
weak SPF/DMARC (see `exposure-discovery`) makes spoofing easier and is a key
defensive fix.

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 →