Skip to content
TrustedSkillsbeta
Back to all skills

Security Engineer

Checked
daffy0208·vlatest·security·MIT

Automates vulnerability scanning, remediation planning, and configuration hardening based on industry best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it Security Engineer, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add daffy0208/ai-dev-standards --skill "Security Engineer" -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

daffy0208

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 daffy0208/ai-dev-standards at 32c3241e48.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
32c3241e48
Manifest
skills/security-engineer/SKILL.md
Scanned
3 files, 1,021 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Security Engineer skill automates aspects of application security, focusing on authentication and authorization, input validation, and sanitization. It provides guidance and code examples for implementing secure practices like JWT usage, session-based authentication, OAuth 2.0/OIDC integration, Role-Based Access Control (RBAC), and Attribute-Based Access Control (ABAC). The skill emphasizes building security into applications from the beginning to prevent vulnerabilities that are costly to fix later.

When to use it

  • When implementing user authentication for APIs or mobile apps using JWTs.
  • For traditional web applications requiring session management.
  • Integrating social login functionality with OAuth 2.0 / OIDC.
  • Defining and enforcing access control policies using RBAC or ABAC.
  • Protecting against SQL injection vulnerabilities in database queries.

Key capabilities

  • Authentication Strategies: Guidance on JWT, Session-Based Authentication, and OAuth 2.0/OIDC implementation.
  • Authorization Patterns: Examples of RBAC and ABAC for fine-grained access control.
  • Input Validation & Sanitization: Demonstrates how to prevent SQL injection through parameterized queries.
  • Code Examples: Provides code snippets in JavaScript (using libraries like jose and Prisma) illustrating secure coding practices.

Example prompts

  • "Show me an example of creating a JWT token with a 15-minute expiry time."
  • "How can I implement RBAC to restrict access to the /api/users/:id endpoint?"
  • "Give me an example of how to prevent SQL injection when querying a database."

Tips & gotchas

  • The skill focuses on code examples in JavaScript. Adapt these examples to your specific technology stack.
  • Always prioritize server-side permission checks; never trust client-provided data for authorization.
  • When using JWTs, use RS256 instead of HS256 for enhanced security.