Total 50,504 skills, Security & Compliance has 1972 skills
Showing 12 of 1972 skills
Use when academic research involves human subjects, public web data, platform scraping, sensitive domains, privacy risk, dataset sharing, consent, IRB, licenses, or data retention.
Detect and analyze fraudulent software distribution repositories masquerading as legitimate security products
Interactive pentest report generator with vulnerability tracking, real-time risk statistics, and PDF export in multiple languages
AI-powered autonomous penetration testing framework with multi-agent system, real security tool execution, and compliance reporting
Identify and analyze potentially malicious software distribution repositories disguised as legitimate security software
Security audits, vulnerability management, GDPR/SOC2/ISO27001 compliance and incident response skill suite for AI coding agents
AI-driven autonomous penetration testing with Kali Linux tools, multi-phase attack planning, and human approval gates for high-risk actions
Warning system for identifying potentially malicious software distribution repositories
Automated penetration testing toolkit for security assessment, vulnerability scanning, and automated security reporting
Analyze and understand Avast antivirus security mechanisms, behavior shields, and protection components for security research
Query Alibaba Cloud WAF block reasons via SLS logs and WAF CLI. Analyzes detailed information about blocked requests. Optionally supports disabling WAF rules (ModifyDefenseRuleStatus) and managing log service settings (ModifyUserWafLogStatus, ModifyResourceLogStatus). Use when users report being blocked by WAF, encounter 405/block error pages, or need to investigate and remediate WAF security rules. Trigger words: "WAF block query", "blocked by WAF", "405 troubleshooting", "request blocked", "checkresponse", "intercept query", "disable WAF rule", "enable WAF log"
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Use when the user asks to threat model a codebase or path, enumerate threats or abuse paths, or perform AppSec threat modeling. Do NOT use for general architecture summaries, code review, security best practices (use security-best-practices), or non-security design work.