What problem does it solve?
Adding external security material (blogs, tools, docs, screenshots) to a structured pentest knowledge base often leads to duplicated content, fabricated tool parameters, misplaced files, and accidental overwrites of contributor work. This Skill provides a seven-phase SOP that governs how external security knowledge is analyzed, verified, placed, and merged into the AboutSecurity repository.
Core Features & Use Cases
- Gap Analysis Before Writing: Decomposes source material into covered, new, skippable, and to-verify buckets, then produces a placement checklist mapping each piece of content to a target SKILL.md or references file.
- Truthfulness Verification: Requires every high-risk fact (tool parameters, API endpoints, default permissions, attack effects) to be confirmed against source material, official docs, or --help output before being written as fact.
- Contributor Protection: Checks git status, remote commits, and recent PRs before editing, and requires explicit justification before deleting or compressing recently contributed content.
- Use Case: A user provides a new cloud security blog with AWS CloudTrail bypass commands and asks to update the aws-post-exploit skill. The Skill first checks git state, extracts verifiable methods, validates AWS CLI parameters, splits content between SKILL.md and references/, and reports what was changed, verified, or skipped.
Quick Start
Absorb the attached security article into the AboutSecurity repository, following the contribution rules and verifying all tool parameters before writing.
