Explorar skills

코드를 비유 기반으로 설명하고 Mermaid 다이어그램을 생성합니다. 파일/기능/줌아웃 3가지 모드 지원. /explain @file.ts (상세 설명), /explain "로그인 기능" (기능 단위), /explain --zoom-out @file.ts (한 단계 위 맵).

This skill should be used when the user asks to "perform SMTP penetration testing", "enumerate email users", "test for open mail relays", "grab SMTP banners", "brute force email credentials", or "assess mail server security". It provides comprehensive techniques for testing SMTP server security.

Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.

Validates docked / generated protein-ligand poses using PoseBusters physical-validity tests, strain energy quantification, geometric checks (planarity, vdW overlap, bond/angle distortion), and pose-energy reasonableness. Filters AI-docking outputs (DiffDock, EquiBind, NeuralPLexer) where ~50% of poses fail physical-validity tests. Use when QC-ing docking results, comparing classical vs ML docking

Set up project infrastructure including TypeScript, database, state management, navigation, and testing. Use when initializing new features or configuring development environment.

Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA). Use when: (1) Enforcing security and compliance policies across infrastructure and applications, (2) Validating Kubernetes admission control policies, (3) Implementing policy-as-code for compliance frameworks (SOC2, PCI-DSS, GDPR, HIPAA), (4) Testing and evaluating OPA Rego policies, (5) Integrating policy checks i

Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

Domine dbt (data build tool) para engenharia de analytics com organização de modelos, testes, documentação e estratégias incrementais. Use ao construir transformações de dados, criar modelos de dados ou implementar as melhores práticas de engenharia de analytics.

Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.

Create the deliverable (code, documentation, tests, content) following the user's standards and best practices. Use after validation passes to actually build the work product.

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,

Staged build methodology for software projects: technical spike → design notes → build plan → stage-by-stage execution with professional-grade testing. Use when user says '/architect', 'new project', 'start a project', 'build this from scratch', wants to plan/build with structured methodology, or resumes an in-progress staged build. NOT for: quick scripts or one-off fixes.