security-essentials

Protects Elixir/Phoenix apps with CSRF-safe authentication and logging.

149|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/j-morgan6/elixir-phoenix-guide --skill security-essentials-j-morgan6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-essentials
Source: https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/security-essentials
Command: npx skills add https://github.com/j-morgan6/elixir-phoenix-guide --skill security-essentials-j-morgan6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security-sensitive code requires strict patterns to avoid common vulnerabilities and misconfigurations.

Core Features & Use Cases

  • Enforces input validation, safe token handling, and secure logging across modules.
  • Defaults to CSRF protection, safe redirects, and dependency auditing to reduce risk.
  • Use Case: A Phoenix app validates user input, secures tokens, and logs safely across controllers, views, and contexts.

Quick Start

Apply the security-essentials skill before implementing authentication, token handling, redirects, or user input processing.

Frequently Asked Questions about security-essentials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure authentication flows and token handling in Phoenix?

You secure Phoenix authentication flows by enforcing safe input handling and using secure token comparisons across controllers and contexts to prevent injection flaws and data leaks.

What is the best way to prevent CSRF attacks in an Elixir application?

Preventing CSRF attacks in Elixir involves defaulting to built-in CSRF protection mechanisms and enforcing safe redirects within your Phoenix controllers to reduce security risks.

How do I implement safe logging in Elixir without leaking sensitive user data?

Safe logging in Elixir requires applying strict patterns across views and contexts to prevent sensitive user data from being exposed or leaked into application logs.

How do I audit dependencies for security vulnerabilities in a Phoenix project?

You audit dependencies for security vulnerabilities in a Phoenix project by running regular dependency auditing to identify compromised packages and reduce overall application risk.

Does this secure coding approach work for processing user input across views and contexts?

Yes, this secure coding approach applies directly to processing user input across Phoenix views and contexts by enforcing strict input validation and safe data handling.

Why do I need dependency auditing and safe redirects for secure Elixir apps?

Dependency auditing identifies vulnerable packages while safe redirects prevent open redirect attacks, both reducing risk and ensuring secure Elixir apps by default.