Security Engineering
CheckedDesigns, implements, and assesses secure systems & infrastructure to proactively mitigate vulnerabilities and threats.
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 89jobrien/steve --skill security-engineering -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
89jobrien
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 89jobrien/steve at c0ff044bf0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c0ff044bf0
- Scanned
- 1 file, 224 lines
About this skill
What it does
This skill provides expertise in security engineering principles and practices. It can assist with identifying potential vulnerabilities, recommending mitigation strategies, and generating documentation related to secure system design. The skill aims to improve the overall security posture of systems by applying established industry best practices.
When to use it
- Threat Modeling: When you need help identifying potential threats and attack vectors for a new application or system.
- Security Audits: To assist in reviewing existing infrastructure and codebases for common vulnerabilities.
- Secure Code Review: For guidance on writing secure code and identifying security flaws during development.
- Compliance Documentation: To help generate documentation required for meeting specific security compliance standards.
Key capabilities
- Vulnerability identification
- Mitigation strategy recommendations
- Secure system design principles
- Security audit assistance
- Documentation generation
Example prompts
- "Perform a threat model on our new e-commerce platform."
- "What are the common vulnerabilities in Node.js applications?"
- "Generate documentation outlining security controls for PCI DSS compliance."
- "Review this code snippet and identify any potential security risks: [code]"
Tips & gotchas
The skill's effectiveness is dependent on providing clear context about the system or application being analyzed. It’s a support tool, not a replacement for human security expertise; always validate its recommendations.