skills.rest
aliciapls
aliciaplsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

security-patterns

Harden Kailash SDK code against OWASP security vulnerabilities.

Updated Apr 2, 2026
Search Tags:#authorization#security#authentication#input validation#owasp#secrets#injection prevention
One-click install
npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill security-patterns-aliciapls
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-patterns
Source: https://github.com/aliciapls/ML-Week-2---Healthcare/tree/main/.claude/skills/18-security-patterns
Command: npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill security-patterns-aliciapls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers prevent common security mistakes in Kailash SDK applications, including exposed secrets, unsafe inputs, weak authentication, and injection risks.

Core Features & Use Cases

  • Secret Management: Keep credentials out of code and use environment variables or secure stores instead.
  • Input and Injection Safety: Validate external data and avoid unsafe execution or query construction.
  • Authentication and Authorization: Apply secure access controls and fail closed when security dependencies are unavailable.
  • Use Case: Review a service that handles API keys, user input, and external API calls to make sure it follows secure coding and OWASP-aligned practices.

Quick Start

Use the security-patterns skill to review this codebase for hardcoded secrets, insecure input handling, and weak authentication logic.

Frequently Asked Questions about security-patterns

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

FAQPage Schema
Are there limitations to using environment variables for secret management?▼

Environment variables for secret management require secure stores to prevent exposure. Limitations include potential access control issues if not properly configured, but they keep credentials out of code.

How do I run a security review on my Kailash SDK codebase?▼

Run a security review on your Kailash SDK codebase by scanning for hardcoded secrets, validating external inputs, and checking authentication logic. Ensure fail-closed authorization and parameterized data access are enforced.

Does this approach work with Kailash SDK workflows that handle external API calls?▼

This approach works with Kailash SDK workflows handling external API calls by enforcing HTTPS usage and input validation. It ensures secure credential management and compliance with documented attack chains.

What is the best way to secure Kailash SDK workflows against common vulnerabilities?▼

The best way to secure Kailash SDK workflows is to enforce environment-variable credential management, parameterized data access, and fail-closed authentication. This prevents injection risks and aligns with OWASP security practices.

Why does my SDK authentication logic fail when dependencies are missing?▼

SDK authentication logic fails when dependencies are missing due to fail-closed security requirements. This prevents unauthorized access by denying operations until all security controls are verified and active.

Related Skills

Explore More Software Engineering Skills→
myeohVmzrka92myeohVmzrka92

security-patterns

Review Kailash SDK code for security vulnerabilities and OWASP compliance.

Community
Advanced
sumik5sumik5
2

AUTH-SECRETS

Enforce secure coding practices for authentication, authorization, and secrets management.

Community
Advanced
ssssssssassssssssssssssassssss

security-patterns

Enforces secure coding patterns for Kailash SDK development.

Community
Advanced
jorgealvesjorgealves
2

python-security-scanner

Detect SQL injections, unsafe deserialization, and hardcoded secrets in Python codebases.

Community
Intermediate