メニュー
Short-path entry for the Sentinel security skill bundle — route to audit, pentest, CTF, CVE, report, frontend, workflow. Use when user @ this file or says sentinel / 安全审计 / 渗透报告.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Source code security audits, SAST, dependency review. When findings are listed or audit ends, MUST chain to sentinel-report — read skills/sentinel/sentinel-report/SKILL.md, ask save folder, Write .md + offline .html. Triggers on audit, vulnerability, security review, 审计.
Use for CTF (Capture The Flag) challenges — web exploitation, binary pwn, cryptography, reverse engineering, forensics, and misc. Invoke when user mentions "CTF", "flag{", "challenge", "HackTheBox", "TryHackMe", "PicoCTF", "pwn", or shares a challenge description asking how to solve it.
Use when user mentions CVE, CVSS, vulnerability lookup, exploit research, CVE database search, or asks about a specific vulnerability severity and mitigation. Invoke when user shares a CVE ID, asks how to assess vulnerability severity, or needs to find known exploits for a component.
Authorized pentest workflow. When engagement summary or findings are delivered, MUST chain to sentinel-report — read sentinel-report/SKILL.md, ask save folder, Write .md + offline .html.
MANDATORY after sentinel-audit, sentinel-pentest, sentinel-frontend completes. Default write sentinel-security-assessment.md + sentinel-security-assessment.html. MUST ask save folder. HTML has ECharts pie (online, CDN) + CSS-bar fallback (offline). Multi-project tabs show each project vuln count as proportion of total. Triggers on audit complete, report, 报告, HTML deliverable.
Use for engineering discipline around security work — systematic root-cause tracing, verification before claiming success, structured review of fixes, threat-focused design exploration, and coordinating parallel multi-target analysis. Standalone replacement for external workflow plugins. Works in Claude Code, Cursor, Codex, Trae, and similar agents; attach this SKILL.md explicitly when the host does not auto-load skills.
| name | sentinel |
| description | Short-path entry for the Sentinel security skill bundle — route to audit, pentest, CTF, CVE, report, frontend, workflow. Use when user @ this file or says sentinel / 安全审计 / 渗透报告. |
| argument-hint | [subcommand] [topic...] |
| metadata | {"author":"sentinel-skill","version":"1.0.0"} |
Bundle index: This file lives at skills/sentinel/SKILL.md (same folder as each sub-skill). Load here first for fast discovery (sentinel ≈ whole package).
$ARGUMENTS
@ mentions skills/sentinel/SKILL.md or sentinel alone| Subcommand / alias | Skill folder | Role |
|---|---|---|
using / (default) | using-sentinel/ | Main router — architecture detection, which skill to follow |
audit | sentinel-audit/ | Source audit, SAST, OWASP |
pentest | sentinel-pentest/ | Authorized live testing workflow |
ctf | sentinel-ctf/ | CTF challenges |
cve | sentinel-cve/ | CVE / CVSS lookup |
report | sentinel-report/ | Reports + HTML deliverable (ECharts CDN pie + offline CSS fallback) |
frontend | sentinel-frontend/ | Vue / React / Angular security |
workflow | sentinel-workflow/ | Root cause, verification, review, parallel work |
Logical ids (elsewhere in docs) look like sentinel:sentinel-audit — they map 1:1 to the folder names above.
skills/sentinel/)| Topic | File |
|---|---|
| Entry & routing detail | using-sentinel/SKILL.md |
| Audit patterns (PHP, etc.) | sentinel-audit/references/*.md |
| Frontend patterns | sentinel-frontend/references/*.md |
$ARGUMENTS — first word = subcommand (see table); if empty or unknown → using-sentinel/SKILL.md.SKILL.md under this directory (e.g. sentinel-audit/SKILL.md).Default: no subcommand ⇒ treat as using-sentinel.
sentinel-skill in prose; on disk the canonical tree is skills/sentinel/<name>/SKILL.md.sentinel-report must run per that skill’s handoff rules.