secure-defaults

Enforce secret management, input validation, and authentication controls at data ingress and egress.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/lgili/skillex --skill secure-defaults-lgili
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secure-defaults
Source: https://github.com/lgili/skillex/tree/main/skills/secure-defaults
Command: npx skills add https://github.com/lgili/skillex --skill secure-defaults-lgili

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill ensures security controls are baked into code from the start, reducing the risk of vulnerabilities due to unsafe defaults.

Core Features & Use Cases

  • Secret management and environment variable discipline to avoid hard-coded credentials.
  • Input validation, secure defaults, and least-privilege patterns across languages.
  • Guidance for auditing dependencies and secure deployment practices.

Quick Start

Run skillex to apply secure-defaults guidelines to your project and generate a starter secure configuration.

Frequently Asked Questions about secure-defaults

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

FAQPage Schema
How do I enforce secure defaults for input validation and secret management in code generation?

You enforce secure defaults by identifying trust boundaries and applying secret management, input validation, and authentication controls at every data ingress and egress. This bakes security controls into code generation from the start.

What is the best way to avoid hard-coded credentials and manage environment variables?

The best way to avoid hard-coded credentials is enforcing environment variable discipline through secret management patterns. Applying least-privilege patterns ensures credentials are securely handled during code generation and infrastructure automation.

Can I apply security-first defaults to API development across any programming language?

Yes, you can apply security-first defaults to API development across any language or framework. The approach enforces input validation, dependency hygiene, and authentication controls at trust boundaries during code generation and infrastructure automation.

How do I audit dependencies and implement safe runtime hardening for infrastructure automation?

You audit dependencies and implement safe runtime hardening by applying explicit checks and actionable guidance during infrastructure automation. This satisfies dependency hygiene requirements and enforces authentication controls across data ingress and egress.

When do I need to identify trust boundaries for secure code generation?

You need to identify trust boundaries whenever performing code generation, API development, or infrastructure automation. This identifies where to enforce secret management, input validation, and authentication controls to prevent vulnerabilities from unsafe defaults.