Security audit
Security checks for vulnerabilities and agentic risk
This is a simple tutorial-writing skill with no executable code, persistence, credential access, or hidden authority.
Installers should understand that this skill may activate for many tutorial or guide-writing requests, but its behavior is limited to formatting and structuring instructional content.
The invocation guidance says to use the skill when the user asks to "create a tutorial, write a guide, explain how to use something, or document a process." Several of these phrases are broad, everyday requests that could match many unrelated conversations, and the file provides no exclusion conditions or narrower scope boundaries.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
- Use **bold** for key commands, file names, and important terms
- Use `code` for inline code, variables, and short commands
- Use blockquotes for warnings or notes:
> **Note:** This step requires sudo privileges.
- Use numbered lists for sequential steps
- Use bullet points for non-sequential items
No suspicious patterns detected.