Security Incident Reporting
CheckedAutomatically generates clear, concise incident reports from logs and alerts, streamlining investigations and response.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add dirnbauer/webconsulting-skills --skill security-incident-reporting -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
dirnbauer
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned dirnbauer/webconsulting-skills at 98b562d70f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 98b562d70f
- Scanned
- 2 files, 823 lines
About this skill
What it does
This skill allows AI agents to generate security incident reports based on provided information. It structures the report with key details such as incident summary, affected systems, and recommended actions. The generated reports are designed for clear communication and documentation of security events.
When to use it
- A security analyst needs a quick draft of an incident report after initial investigation.
- An automated system detects suspicious activity and requires a preliminary report to be created.
- During a tabletop exercise, generate sample incident reports for training purposes.
- To standardize the format and content of incident reporting across different teams or departments.
Key capabilities
- Incident Summary Generation
- Affected Systems Identification
- Recommended Actions Suggestion
- Report Structuring
Example prompts
- "Generate a security incident report for a phishing attack targeting employee credentials."
- "Create an incident report detailing unauthorized access to a database server, including the compromised IP address and timestamps."
- “Draft a report about a denial-of-service attack impacting our web application.”
Tips & gotchas
The quality of the generated report depends heavily on the accuracy and completeness of the information provided. Ensure you supply relevant details for optimal results.