patch-recon
/patch-recon
Audit existing vulnerability management — find SLA gaps, missing tiers, and process failures. Use when asked to "audit our vulnerability management", "find patch SLA gaps", or "are we patching fast enough".
- Author
- tonone-ai ↗
- Repository
- tonone ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Audit existing vulnerability management — find SLA gaps, missing tiers, and process failures. Use when asked to "audit our vulnerability management", "find patch SLA gaps", or "are we patching fast enough".
Triggers from the description
Original author description
Audit existing vulnerability management — find SLA gaps, missing tiers, and process failures. Use when asked to "audit our vulnerability management", "find patch SLA gaps", or "are we patching fast enough".
How it works
- Steps
- Key Rules
- Delivery
SKILL.md preview
--- name: patch-recon description: Audit existing vulnerability management — find SLA gaps, missing tiers, and process failures. Use when asked to "audit our vulnerability management", "find patch SLA gaps", or "are we patching fast enough". allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion version: 1.5.0 author: tonone-ai <hello@tonone.ai> license: MIT compatibility: Designed for Claude Code tags: [security, vulnerability-management, recon] --- # Patch Recon You are Patch — Vulnerability Management Engineer on the Security Operations Team. ## Steps ### Step 0: Confirm Context Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed. ### Step 1: Gather Context Read existing vuln management policies, SLA definitions, and any scan reports. Grep for CVSS, SLA, patching in docs. ### Step 2: Produce Output Report: SLA coverage gaps, missing asset tiers, process failures (no verification step, no exceptions process), and recommended improvements. ### Step 3: Summary Output a brief summary: - What was produced - Key risks or open questions - Recommended next steps ## Key Rules - Follow the output format defined in docs/output-kit.md - Always flag when outside security expertise is required (legal counsel, law enforcement, regulatory) - Pair every risk finding with a business impact statement ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Versions
The database has no other skills named patch-recon.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 858bf7f34262 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90patch-plan
Design a vulnerability management program — SLAs, asset tiers, escalation, and metrics. Use when asked to "design a patching program", "set vulnerability SLAs", or "define our patch cadence". - 90drift-recon
Audit existing ML monitoring — find gaps in drift coverage and missing alerts. Use when asked to "audit our ML monitoring", "are our models monitored", or "find drift coverage gaps". - 100implementing-vulnerability-remediation-sla
Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation KPIs/trending metrics. Use when defining mandatory patching timeframes by severity and asset… - 100vulnerability-management
Enforce vulnerability management and patching for AI software dependencies. Use when planning, implementing, or reviewing vulnerability response processes for MCP servers, inference engines, or AI system components. - 90vulnerability-management
Subdomain routing agent for Vulnerability Management and Attack Surface Management. Covers VM programs, scanner operations, risk scoring (CVSS/EPSS/VPR), remediation workflows, SLA tracking, CNAPP platforms, and EASM tools. WHEN: \"vulnerability management\", \"vuln scan\",… - 100implementing-vulnerability-sla-breach-alerting
Build an automated SLA breach alerting system for vulnerability remediation, including a database schema for SLA tracking, breach detection logic, notification dispatch, a scheduled check runner, and a KPI/compliance metrics dashboard. Use when implementing severity-based SLA…