Skip to content
Security
Skill

/example-skill

One or two sentences naming the SITUATION, INPUTS, and OUTCOME so Claude knows exactly when to fire this skill. This text is always in context — be specific but tight. Example: "Assess an API endpoint against the OWASP API Top 10 and produce a ranked findings table. Use when

From plugin
awesome-claude-security
7111 skills17 agents13 commands1 MCP
Install
$ npx -y skills add jassics/awesome-claude-security --skill example-skill --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/example-skill

Context preview

The summary Claude sees to decide when to auto-load this skill.

One or two sentences naming the SITUATION, INPUTS, and OUTCOME so Claude knows exactly when to fire this skill. This text is always in context — be specific but tight. Example: "Assess an API endpoint against the OWASP API Top 10 and produce a ranked findings table. Use when

SKILL.md

example-skill.SKILL.md
name: example-skill
description: >-
  One or two sentences naming the SITUATION, INPUTS, and OUTCOME so Claude knows
  exactly when to fire this skill. This text is always in context — be specific
  but tight. Example: "Assess an API endpoint against the OWASP API Top 10 and
  produce a ranked findings table. Use when reviewing a REST/GraphQL API for
  authz, rate-limiting, or schema-abuse issues."

Goal

State what "done" looks like in one line.

Prerequisites

  • Authorization to test/assess the target.
  • Any inputs the user must provide (URL, repo, scope, credentials channel).

Steps

1. Establish scope and gather inputs. 2. Work the methodology — reference the relevant framework by name (OWASP, MITRE ATT&CK, STRIDE, MASTG, CIS...). For long checklists, read `reference.md`. 3. Validate findings; remove false positives. 4. Rank by severity/risk.

Output

Produce a concrete artifact and say its format here, e.g. a findings table with columns: ID · Title · Severity · Evidence · Remediation. For reports or diagrams, defer to `security-reporting` / `security-diagramming`.

Notes

Keep framing defensive and authorized. Don't fabricate evidence.

Ships withawesome-claude-security

A Claude Code plugin marketplace for the full cybersecurity & GenAI-security lifecycle — from recon and threat modeling to detection engineering, GRC, and CISO-level strategy. A pentester knows which OWASP test bends a broken-access-control endpoint.

Get the whole plugin

Other skills on awesome-claude-security.