agentic-security:security-tutor

Explains security findings via Socratic Source-Sink-Sanitizer walkthroughs before remediation.

73|15|Updated May 6, 2026
One-click install
npx skills add https://github.com/Clear-Capabilities/agentic-security --skill agentic-security-security-tutor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-security:security-tutor
Source: https://github.com/Clear-Capabilities/agentic-security/tree/main/skills/security-tutor
Command: npx skills add https://github.com/Clear-Capabilities/agentic-security --skill agentic-security-security-tutor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users to understand and reason about security findings by applying a Socratic questioning approach, helping teams move beyond rote remediation to deeper comprehension.

Core Features & Use Cases

  • Socratic dialogue: prompts users to identify the Source, Sink, and Sanitizer in a finding and explains how they interact.
  • Contextual walkthrough: explains the risk narrative step-by-step rather than merely giving a fix.
  • Learning & onboarding: ideal for engineers, reviewers, and learners who want to build intuition about common vulnerability patterns.
  • Use Case: during code reviews, incident triage, or training sessions where users request explanations like “why is this dangerous?” or “what does finding-id ir-taint mean in context?”

Quick Start

Ask the assistant to explain a finding or reference its finding-id to start the Socratic walkthrough.

Frequently Asked Questions about agentic-security:security-tutor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I understand security findings during code review and triage?

Security findings during triage are best understood by identifying the Source, Sink, and Sanitizer. The Socratic dialogue method walks you through these interactions step-by-step, explaining the underlying risk context before addressing any remediation steps.

What is taint analysis and how do source, sink, and sanitizer interact?

Taint analysis tracks how untrusted data flows from a Source to a dangerous Sink, potentially mitigated by a Sanitizer. Understanding this interaction reveals why a finding is dangerous, building intuition about vulnerability patterns rather than just applying rote fixes.

How do I explain a security finding to engineering teams during onboarding?

To explain a security finding to engineering teams, use a structured Socratic walkthrough. This approach requires identifying the Source, Sink, and Sanitizer, and enforces a stepwise explanation of the risk narrative to build deeper comprehension.

Does this security learning approach provide direct remediation steps for vulnerabilities?

This security learning approach focuses on contextual risk explanation rather than immediate fixes. It enforces a stepwise walkthrough of the vulnerability's underlying mechanisms and requires full comprehension of the risk narrative before providing any remediation steps.

When do I need a Socratic walkthrough for vulnerability triage sessions?

You need a Socratic walkthrough for vulnerability triage when teams require deeper comprehension of findings. It is ideal for code reviews, incident triage, and training scenarios where engineers ask why a specific finding is dangerous or seek its contextual risk narrative.